Message-ID: <41A61AC6.1060300@clanganke.de>
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.4a) Gecko/20030401
MIME-Version: 1.0
References: <200411250633.iAP6XVoY093082@mail.cruzio.com> <41A5D1EB.10502@mindspring.com> 	<200411251534.iAPFYm66008286@mail.cruzio.com> <41A5FDDB.6050107@mindspring.com> <200411251652.iAPGqDhu043536@mail.cruzio.com>
In-Reply-To: <200411251652.iAPGqDhu043536@mail.cruzio.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date:  Thu, 25 Nov 2004 18:47:50 +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] Wireless LAN Monitor

Neil Waldhauer wrote:

>On Thu, 25 Nov 2004 09:44:27 -0600, Stuart Updike <stuupdike@mindspring.com>
>wrote:
>
>  
>
>>I would think you could still use your scripts to change to the wireless 
>>card, in which case you should set XWLAN to lan1.  That is essentially 
>>what I've been doing with my T21.
>>    
>>
>
>You are right. If I continue to use my scripts, then networking continues as
>normal. But I had hoped that my scripts functionality would have been included
>in the new XWLAN.
>
>XWLAN calls scripts on "disconnect" and "connect". Are these events when the
>card is inserted and ejected? Can I call my scripts from XWLAN?
>
>Neil
>  
>
Hmm, I do not remember what your scripts are doing, and I think you 
should not be require to use scripts to configure the lan interface of 
the TCP/IP interface of your Wireless LAN device (also not the script 
solution that XWLAN offers) - I think we discussed that once. If you 
have a cabled interface on your notebook as well, this should not 
disturb, unless you don't configure it. In any case it is highly 
recommended to notconfigure the TCP/IP interface within the TCP/IP 
configuration program.

In order to find out which TCP/IP lan interface is boud to your Wireless 
LAN device, just open MPTS and check the adapter number left to the 
entry "TCP/IP" protocol underneath the driver for your Wireless LAN 
device. When you then select this interface in the TCP/IP properties 
page, XWLAN should be able to configure this interface. But after having 
made that change, nothing happens, until you take further action.

Taken that you are in range of the hotspot that the selected access 
point would match to, you would reconfigure (in this case reissue the 
DHCP request) by selecting "TCP/IP interface - (re)configure..

Instead, in order to connect to any hotspot, select the menu item 
"Public hotspot". This will automatically launch a DHCP request. Only 
when this returns successfully, the IP interface is being configured 
(not by XWLAN, but rather by the DHCP client daemon),  and only after 
_that_ has succeded, XWLAN will call its script (once you have 
configured that) for the connect event. So the script events connect and 
disconnect are not to configure or unconfigure the LAN interface of the 
Wireless LAN device, instead they are called when the configuration has 
succeeded or the IP interface was unconfigured.

After having connected to a public hotspot, you then may want to create 
a dedicated connection profile out of the connection, just by selection 
the appropriate menu item within the hotspot menu.

Please let me know it it works.

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)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=