Mailing List os2-wireless_users@2rosenthals.com Archived Message #4709 previous message next message back to list

From: Christian Langanke <os2-wireless_users@2rosenthals.com> Full Headers
Undecoded message
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Subject: [OS2Wireless] Wireless LAN Monitor vs wired/wireless cmd files
Date: Mon, 18 Oct 2004 22:30:25 +0200
To: os2-wireless_users@2rosenthals.com

Lewis G Rosenthal wrote:

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.

As already stated out, this is only true if due to any reason two nics get IP addresses of the same IP subsegment. Otherwise there is no need to disable any IP interface. And the disablement of an IP interface can easily be done with some extensions to XWLAN, so there is no need to stick with scripts here.

I see the following example scenarios where XWLAN can disable one of two interfaces in a senseful way:

scenario 1:
-------------
cabled lan0: static addr 192.168.1.5, not plugged
wifi lan1: attempts to access public hotspot with DHCP request

hotspot returns: 192.168.1.83
XWLAN detects an IP range conflict and brings up a popup, asking wether lan0 should be disabled.


scenario 2:
-------------
cabled lan0: dhcp address received from my home network, cable plugged on startup, so lan0 receives 192.168.1.10
wifi lan1: pcmcia card not plugged (or radio disabled)

Now I decide to pull the cable, slide in the PCMCIA card and change room. As the wifi router is attached to the same network, the DHCP request sent over wifi returns an address of the same IP subsegment, lets say 192.168.1.12.
Again, XWLAN detects an IP range conflict and brings up a popup, asking wether lan0 should be disabled.

scenario 3:
-------------
cabled lan0: cable not plugged (so DHCP request on startup has failed)
wifi lan1: pcmcia card plugged, DHCP returned address 192.168.1.12 from my home network

Now I decide to turn of wifi (maybe in order to switch to the faster cable for a big data transfer). Herfore I plug the cable for lan0,  need to issue a DHCP request for lan0 (after stopping DHCP for lan1, like in your script). Herefore I could think of two features of XWLAN:

- give up DHCP lease for the wifi nic (so no need to launch the DHCP monitor for this)
- issue the DHCP request for any other IP interface of choice

does that make sense ? Any other ideas ?

bye, Christian

-------------------------------------------------

Christian Langanke
COS2E & CWSE
Team OS/2 Ruhr e.V.
cla@clanganke.de






=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

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)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Subscribe: Feed, Digest, Index.
Unsubscribe
Mail to ListMaster