Mensaje archivado #2228 de la Lista os2-wireless_users@2rosenthals.com

De: Christian Langanke <os2-wireless_users@2rosenthals.com> Encabezados Completos
Mensaje no decodificado
Enviador: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Asunto: [OS2Wireless] XWLAN script for changing between wifi and wired LANs
Fecha: Tue, 29 Nov 2005 00:39:24 +0100
Para: os2-wireless_users@2rosenthals.com

Chris Clayton wrote:

After quite a bit of testing I have developed a xwlan script that
changes between a 'Home' profile wifi lan0 and a wired lan1.
Hi Chris,

great idea !Never thought about handling even NetBios stuff in such a way. Is there a specific reason why on "home connect" you don't restart the peer within the script ? Just thought about in which way this could be added.

I also read your comments about sticking to plain batch instead of using REXX. Just my two cents: the REXX script would read much better, because lots of comments would not be needed and no problems with batch labels would occurr. If the below things are done, and your script can get shorter, maybe it makes sense to try a REXX version - this may convince you. OTOH I could well think of enhancing XWLAN with some of the things your script does, just like starting/stopping peer. The bad part on this is that there is no way to safely determine if a NetBIOS compatible protocol stack is bound to the Wifi nic. In any way I would appreciate if we can proceed on that further, please send pm if you are interested in that.

But also plain batch will just do fine of course.  I only would suggest a slight change in order to make the whole script more configurable: specify the real important values as SET vars at the top:

SET WIFI_IF=lan1
SET CABLED_IF=lan0
SET IP=192.168.2.56
SET NETMASK=255.255.255.0
SET HOMEPRF=Home

and use it in the comands and batchlabel. It is much easier then for others to use it as well (I would do the very same for the REXX solution BTW)
And I just wondered of why you need a hopcount of 2 ...

About your comments

1)  When the radio is turned off the SSID does not appear to be passed
to the script (I get a NULL string).  So I used the profile name as a
test instead of the SSID as indicted in the sample script.

Will check that. The SSID should be empty only when (dis)connectiing from/to a hotspot.

2) I had to disable the TCP/IP setup in the 'Home' profile and do the
setup in the script because I got a popup error message about using
duplicate fixed IP addresses for both lan0 and lan1.  The 'Travel' DHCP
setup was ok, no configuration statements are needed in the script
except for ensuring that the wired LAN is deleted.

Just thought about to add a property to suppress this warning in favour either for the wireless or cabled interface. Think this should help you to make your script even shorter.

3) The wifi is sometimes stubborn about connecting to a profile, even
if the AP is only a few feet away.  I'm not sure if this is a xwlan
script problem or related to interference from local networks.  

May also be a driver issue... I sometimes even get a "no driver available", while the hardware _is_ available and was working before, and that both from genprism and genmac drivers (and the mini pci card csnnot be removed, right ?)

4) Sometimes the 'Home' profile connects but the connect event is not
sent to the script.  In this case, the infamous 'IP disabled' logo is
shown.  I correct this by manually issuing the appropriate wifi script
commands.

Ah, did not check for this until now, as I had not to rely on the script feature that much. Of course, if such a script does the whole config, one will notice it much earlier. Unfortunately I have no clue how I could check why some events are just not showing up.

---

I also found a bug that for "radio on" (or was it "radio off") no (dis)connect script event is generated. Will have to go after that...

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)

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




Suscribirse: Todos, Compendio, Indice.
Desuscribirse
Correo al dueño de la Lista