In-reply-to: <4171E1B8.5070306@2rosenthals.com>
Message-id: <417310BE.3010805@2rosenthals.com>
Organization: Rosenthal & Rosenthal
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8a4) Gecko/20040930
 MultiZilla/1.6.4.0b Mnenhy/0.6.0.104
References: <4171E1B8.5070306@2rosenthals.com>
Date:  Sun, 17 Oct 2004 20:39:26 -0400
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Reply-To: os2-wireless_users@2rosenthals.com
From:  Lewis G Rosenthal <os2-wireless_users@2rosenthals.com>
To:  os2-wireless_users@2rosenthals.com
Subject: [OS2Wireless] Wireless LAN Monitor vs wired/wireless cmd files

Some follow-up to this...

In order to properly route packets to the connected interface, it is 
still necessary to turn off the disconnected one. While XWLAN easily 
handles the WiFi NIC, I found that using a couple of Neil's scripts 
(slightly modified) to turn off and on the wired NIC came in handy.

For reference:

NICON.CMD:
==========================
/* turn on TCP the NIC
 * This command Activates the wired interface
*/
say "Activating the wired network interface"
'@ ifconfig lan1 down'
'@ ifconfig lan1 delete'
'@ dhcpmon -t'
'@ route -fh'
'@ arp -f'
'@ dhcpstrt -i lan0 -d 0'
say "TCP on wired interface enabled"
return

NICOFF.CMD:
==========================
/* turn off TCP the NIC
 * This command deactivates the wired interface
*/
say "Deactivating the wired network interface"
'@ ifconfig lan0 down'
'@ ifconfig lan0 delete'
'@ dhcpmon -t'
'@ route -fh'
'@ arp -f'
say "TCP on wired interface disabled"
return

Note that NICON.CMD is probably unmodified (IIRC). We delete LAN1, as 
XWLAN will recreate it. NICOFF.CMD, OTOH, does not attempt to bring up 
LAN1, as this is left to XWLAN.

Notes/oddities:

   1. Sometimes, it is necessary to run NICON.CMD a couple times in
      order to get the wired NIC to obtain an address. My suspicion here
      is that this will depend upon the DHCP server (in the case of my
      testing, just the LinkSys WRT54G; I haven't tried it against my
      NetWare server, which is my usual DHCP server), or it may be
      differences in NIC drivers and/or firmware (the ethernet interface
      in this T30 is an Intel Pro 10/100 mPCI, though I'm not sure of
      the firmware rev; I used the included driver with eCS 1.2 for my
      test setup).
   2. My Cisco card was stubborn when it was not inserted at bootup.
      That is, if I started the system wired, then later inserted the
      Cisco 350, XWLAN had to either disable/enable the card a few times
      in order for it to become associated or I had to close eCenter and
      restart it (I'm using the XWLAN widget in this setup). once
      associated the first time, however, switching on and off was
      fairly smooth.
   3. I've seen the same issue previously reported where XWLAN refused
      to switch to a second profile. I've promised a spare Cisco 350 to
      Christian for his testing, but I've been slow to get it shipped to
      him, due to other distractions. Hopefully, when he has one of
      these things to play with, he'll be able to get the kinks worked
      out for the next release of XWLAN (right now, I've been using 1.02).

-- 
Lewis
------------------------------------------------------------
Lewis G Rosenthal, CNA 
Rosenthal & Rosenthal 
Accountants / Network Consultants 
  New York / Northern Virginia           www.2rosenthals.com
Team OS/2  / NetWare Users International      www.novell.com
------------------------------------------------------------ 


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

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).

This list is hosted by Rosenthal & Rosenthal
P.O. Box 281, Deer Park, NY 11729-0281. Non-
electronic communications related to content
contained in these messages should be directed
to the above address. (CAN-SPAM Act of 2003)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=