Message-ID: <41ABB8EA.90305@clanganke.de>
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.4a) Gecko/20030401
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date:  Tue, 30 Nov 2004 01:03:54 +0100
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Reply-To: os2-wireless_users@2rosenthals.com
From:  Christian Langanke <os2-wireless_users@2rosenthals.com>
To:  os2-wireless_users@2rosenthals.com
Subject: [OS2Wireless] XWLAN Bugfix Release V1.11 for DHCP problems


Hi,

during Warpstock Europe event last weekend it turned out that XWLAN 
V1.10 had problems if any other interface than the one of the Wireless 
LAN device was dhcpstrt'ed before XWLAN was started. The code changes I 
added should now avoid the problem, I just shipped this to hobbes and my 
homepage (see sig)

I think this was the problem that Neil reported.  I would guess that his 
mptn\bin\setup.cmd contains a dhcpstrt command for the cabled interface 
(so was it here on two notebooks on Warpstock Europe).

I also extended the TCP/IP range conflict detection so that a conflict 
is checked for on every status update. As a result a conflict will also 
be detected if you would e.g. manually set the interface of the cabled 
device to the range that the interface of the Wireless LAN device is 
configured to.

Please be so kind and post back your experiences (especially Neil) as an 
answer to this mail (keep the subject please).

thanx, Christian

P.S.: @Neil: I reread the part on your scripts, deactivation lan0 or 
lan1 depending on what you are using. I just want to say that the TCP/IP 
interface of the Wireless LAN card is always activated or deactivated by 
XWLAN where appropriate, so your scripts will at least not have any 
impact on that interface when executed before connecting/disconnecting.

PP.S.:Concerning the wired interface, there has been a suggestion to let 
XWLAN as well configure that (by DHCP)  if XWLAN did not detect any 
wireless device (this would be a workaround for the fact that to my 
knowledge no piece of OS/2 software can currently detect or be notified 
if a network cable is plugged or unplugged, so XWLAN would make a 
guess). Does that make sense to everybody ? (I am not sure...)

-------------------------------------------------

Free utilities for OS/2 and eComStation at
-> http://www.clanganke.de/os2

Christian Langanke
COS2E & CWSE
Team OS/2 Ruhr e.V., Germany
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)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=