Message-ID: <3F2FCB58.7000800@rogers.com>
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.4) Gecko/20030624
MIME-Version: 1.0
References: <auto-000176369454@admin.nni.com> <3F2E9BBA.10200@rogers.com> <200308041225.000006WR@dsl3-63-249-70-32.cruzio.com> <3F2EBF5A.4090408@rogers.com> <3F2F2367.4040802@2rosenthals.com>
In-Reply-To: <3F2F2367.4040802@2rosenthals.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date: Tue, 5 Aug 2003 11:20:57 EST5EDT4,M4.1,M10.5
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Reply-To: os2-wireless_users@2rosenthals.com
From:  Orest Skrypuch <os2-wireless_users@2rosenthals.com>
To:  os2-wireless_users@2rosenthals.com
Subject: [OS2Wireless] How to: setup wireless AND wired interface on a laptop?

Lewis G Rosenthal wrote:

> Orest -
>
> Orest Skrypuch wrote:
>
>> Another question, now, how do you know that the wireless MAC is lan1? 
>> I guess it would be a reasonable assumption, but is this determined 
>> somewhere in the setup files? MPTS lists the tcp/ip protocol through 
>> the wireless card as "2", is lan0 the lowest number tcp/ip, lan1 the 
>> next highest (in this case 2), and so on? 
>
>
> The first card to which you bind TCP/IP is lan0. The second card, by 
> default, is lan1. You may change this number in LAPS to anything you 
> like. If you look at the bindings, you'll see that the first card 
> listed is not preceded by a comma; this denotes lan0. The second 
> binding follows the first comma, and is lan1, the third follows 
> another comma, and so forth.
>
> Example:
>
> [tcpip_nif]
>
>   DriverName = TCPIP$
>   Bindings = IBMFEEO2_nif
>
> IBMFEEO2 (IBM EtherJet NIC) is lan0.
>
> [tcpip_nif]
>
>   DriverName = TCPIP$
>   Bindings = IBMFEEO2_nif,CISCOPCM_nif
>
> Same as above, but the Cisco 340/350 card is lan1.
>
> One other point to note. Virtual switch does not work with Wi-Fi 
> adapters (there's a note on this earlier in the archives here, and was 
> explained to me by the guys at Innotek). However, it doesn't hurt to 
> leave it loaded; just remember that in order to route your traffic 
> through your 802.11x device you'll need to (temporarily) configure the 
> VPC for shared networking.


I don't need the VPC session with 11x access (at present anyway), so 
that is a project for another day.


Another question, is there a simple way to determine which lanx 
interface is active for TCPIP? I'd like to add that to the rexx scripts, 
so you don't in error run the setup Rexx script more than once.

BTW, this is a FABULOUS list!

* Orest

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

To unsubscribe from this list, send a message to
steward@2rosenthals.com with the command
"unsubscribe os2-wireless_users" in the body
(omit the quotes).

For help with other commands, send a message
to steward@2rosenthals.com with the command
"help" in the body (omit the quotes).

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=