Message-ID: <40E44C75.2050508@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: <auto-000323732728@admin.nni.com>
In-Reply-To: <auto-000323732728@admin.nni.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Date:  Thu, 01 Jul 2004 19:40:05 +0200
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] WiFi Wiget XLan Monitor ??

Stanley Sidlov wrote:

>New Question:
>
>If you are switching back and forth using a 'wired' and 'wireless' cmd files such as those that Neil wrote. How should 
>the new widget be configured for the card? 
>
>A. No radio and DHCP?
>B. Radio on and don't configure?
>C. Radio on and DHCP?
>D. Radio on  and Manually configure?
>
>
>'Cause,  I had it manually configured and the script didn't work. I changed it to 'Don't Configure' and the script 
>worked but the unit didn't get an IP address but did work when I changed it to DHCP AFTER running the script.....
>
That is because the WLAN monitor works around a problem with the DHCP 
client: it kills the DHCP client daemon before issuing another dhcp 
request. If you don't do this, the dhcp client just does nothing...

You may want to use my pgmcntrl utility (see sig for my homepage) to 
kill the client daemon within your script before issuing the dhcpstrt call.


BTW the only proper way to connect to the same machine (maybe your 
desktop system) both via a cabled _and_ a WLAN connection is to 
establish two different IP subnets (like 192.168.1.x and 192.168.2.x) 
and either (A) two nics in your target system or (B) usign another 
machine with two nics as a router or (C) using an alias TCP/IP address 
on the only nic of your target machine. AFAIK solution A is the only one 
if you want not only TCP/IP being the only network protocol used, but 
also NetBIOS...

In any way, using two subnets, you can use DHCP on both cabled and WLAN 
interface, but then you can't use the normal DHCP configuration withthe 
TCP/IP configuration notebook, as the IBM DHCP client can maintain only 
one interface simultaniously. In order to request DHCP configuration for 
more than one interface on a asystem, you need to serialize it, likely 
with a script performing the following steps (assume lan0 is cabled and 
lan1 is WLAN):

1 kill dhcpcd
2 call dhcpstrt lan0
3 wait for completion of configuration of lan0
4 kill dhcpcd
5 call dhcpstrt lan1

The problem is that there is no command line utility ready to use for 
step 3. For that a REXX script could pipe the output of "ifconfig lanx" 
to a temp file and parse, if the IP address is still 0.0.0.0 (incomplete 
configuration), and bails out of the loop, if it has been set.

Remember that both DHCP requests should return a default gateway, 
otherwise you will have none if the one returning a default gateway 
cannot be reached. The bad point on this is how to make sure that the 
faster subnet over the cable is preferred over the slower WLAN 
connection.I don't see a solution for this other than forgetting about 
DHCP automation and triggering DHCP configuration via two rpogram 
objects on the desktop, deactivation all DHCP configurarion within the 
TCP/IP configuration notebook as well as in the WLAN monitor.

>And what is the default netmask?    225.225.225.225 or 225.225.225.0 ? 
>  
>
I coded that according to my TCP/IP reference:
for class A adresses (first byte <=128) it is 255.0.0.0
for class B adresses (first byte <=192) it is 255.255.0.0
all other the code assumes class C addresses: 255.255.255.0

Unless somebody is using subnetting (ege. using subnet masks like 
255.255.255.240) , the default netmaks should be sufficient.

bye, Christian

-------------------------------------------------

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)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=