Message-ID: <40E4665F.7000500@comcast.net>
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8a2) Gecko/20040621
MIME-Version: 1.0
References: <auto-000323732728@admin.nni.com> <40E2B816.1020806@comcast.net> <40E44F2D.9020609@clanganke.de>
In-Reply-To: <40E44F2D.9020609@clanganke.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date:  Thu, 01 Jul 2004 13:30:39 -0600
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Reply-To: os2-wireless_users@2rosenthals.com
From:  Andy Willis <os2-wireless_users@2rosenthals.com>
To:  os2-wireless_users@2rosenthals.com
Subject: [OS2Wireless] WiFi Wiget XLan Monitor ??

Christian Langanke wrote:

> Andy Willis wrote:
>
>> I am not saying this is the best method but it seems to work.  I have 
>> the vpc mac driver with tcpip on lan0.  My wired card is configured 
>> to use it.  I then have tcpip on lan7 set to my wireless card. I am 
>> using dhcp for both the wireless and the wired lans but as you can't 
>> have both set to dhcp in the tcpip settings I have not enabled 
>> lan7.   I then have the wlan widget set to put my wireless set to 
>> dhcp on lan0.  This has allowed me to use the wireless without having 
>> to reconfigure anything.  The only thing I do have to do is switch 
>> the lan to something other than lan0 and then back to lan0 (in the 
>> widget) in order for it to grab it.
>> Andy 
>
>
> So I assume that lan0 is your TCP/IP interface for the wireless lan 
> card ? If not, I get a bit confused... You should not set the WLAN 
> widget to lan0 to let it issue a DHCP request for the cabled interface...
>
> You should also not set the WLAN monitor to lan7 to prevent DHCP 
> configuration, instead you should modify a given connection profile to 
> not use DHCP.
>
> The reason for both cases is that forthcoming versions of the driver 
> and the WLAN monitor will determine automatically the IP interface 
> associated to the WLAN driver, and then you will not longer be able to 
> select another IP interface. As a result, any IP interface selected 
> and not being the correct IP interface for yourWLAN device, while any 
> of your connection profile is configured to use DHCP or manual 
> configuration, is a _misconfigurarion_. You can currently do so, but 
> it is kind of a misuse. The WLAN monitor is to configure the IP 
> interface of the WLAN device _only_.
>
> Just wanted to make that point clear, as this will definitely change 
> in the future.
>
> BTW, in the forthcoming version of WLAN monitor there will also be a 
> notice in the installatio section that once the WLAN monitor is used 
> for IP configuration of the WLAN device, this should not anylonger be 
> done in the TCP/IP configuration settings notebook as well.
>
> bye, Christian
>
Lan0 is my wired card in MPTS.  I connect with it the majority of the 
time and have it set up to use the vpc virtual switch.  It uses dhcp.  I 
installed the wlan card and in MPTS and it requires a protocol so I 
added tcpip and put it on Lan7.  I then originally set the wlan widget 
to enable Lan7 and configured using dhcp.  This didn't ever work.  So I 
switched it to lan0 in the wlan widget and it got an ip address (never 
changing MPTS).  The next boot with the wlan card I did not get an ip 
address, so I switched it to Lan1 and closed the wlan widget then 
reopened the wlan widget and switched it back to Lan0 and closed it and 
got an ip address.  Since then that is what I have been doing to get an 
IP address on my wireless.
Andy
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

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)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=