Message-ID: <41ACBAD7.9010301@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> <41A61AC6.1060300@clanganke.de> <200411252023.iAPKNZ9p032943@ns2.cruzio.com>
In-Reply-To: <200411252023.iAPKNZ9p032943@ns2.cruzio.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Date:  Tue, 30 Nov 2004 19:24:23 +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:

>>From what you say, I should now be able to ignore my scripts, and when I plug
>in my wireless card, it should just connect.
>
>OK, that is just what it does. That is cool. I needed to have properties:
>Radio: Activate radio on startup. Also I needed to have TCP/IP: LAN 1
>
Ok, so that far everything works

>
>But I still can't figure out how to switch from wireless back to wired. There
>are some things missing. But my scripts do not always work for this, either.
>Ideally, when the card is inserted, the computer activates LAN1 and deactivates
>LAN0, and when the card is ejected, the comptuer activates LAN0 and deactivates
>LAN1.
>
This would mean that a piece of software designed to run the Wireless 
LAN device and its IP interface should also take care for the wired 
interface. But thats not what the package is currently designed for. I 
once thought about a more global acting software, like a LAN management 
component, handling all lan interfaces, but for that an application 
would need to be able to register itself to get nofified if a cable is 
plugged into a NIC or umplugged from it.

>But I do now have it working without my scripts for the simplest case. Start
>the computer with a wire, it uses LAN0. Start the computer with nothing, and
>plug in the wireless card, then it uses LAN1.
>
Yes, I think that is the way to go. The fix release V1.11 should now 
even work once the DHCP request is fired off for the cabled interface.

thanx, 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)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=