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.