X-Account-Key: account1 X-UIDL: 29581 X-Mozilla-Keys: Return-Path: os2-wireless_users-owner@2rosenthals.com Received: from 192.168.100.5 (hawking [192.168.100.5]) by 2rosenthals.com (Hethmon Brothers Smtpd) id 20041019230143-27377-7 ; Tue, 19 Oct 2004 23:01:43 -0400 (Hethmon Brothers Smtpd) id 20041019230141-52292-7 ; Tue, 19 Oct 2004 23:01:41 -0400 Received: from mx1.mailhop.org ([63.208.196.170]) by mxout3.mailhop.org with esmtp (Exim 4.42) id 1CK6j4-000LTR-VU for os2-wireless_users@2rosenthals.com; Tue, 19 Oct 2004 23:01:29 -0400 Received: from smtp.toast.net ([206.244.186.20] helo=MAIL03.eucnet.com) by mx1.mailhop.org with esmtp (Exim 4.42) id 1CK6iq-000OPH-6G for os2-wireless_users@2rosenthals.com; Tue, 19 Oct 2004 23:01:08 -0400 Received: from [192.168.1.5] (unverified [206.149.149.42]) by MAIL03.eucnet.com (Vircom SMTPRS 3.2.315.0) with ESMTP id for ; Tue, 19 Oct 2004 22:58:22 -0400 Message-ID: <4175D4F4.7020100@2rosenthals.com> Organization: Rosenthal & Rosenthal User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8a4) Gecko/20040930 MultiZilla/1.6.4.0b Mnenhy/0.6.0.104 X-Accept-Language: en-us, en MIME-Version: 1.0 References: <4171E1B8.5070306@2rosenthals.com> <417310BE.3010805@2rosenthals.com> <417427E1.5070807@clanganke.de> <200410182133.i9ILX2P5093412@mail.cruzio.com> <41759C5C.8020303@clanganke.de> In-Reply-To: <41759C5C.8020303@clanganke.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mail-Handler: MailHop by DynDNS.org X-Spam-Score: -4.8 (----) Date: Tue, 19 Oct 2004 23:01:08 -0400 Sender: os2-wireless_users-owner X-Listname: os2-wireless_users@2rosenthals.com Reply-To: os2-wireless_users@2rosenthals.com From: Lewis G Rosenthal To: os2-wireless_users@2rosenthals.com Subject: [OS2Wireless] Wireless LAN new features - please test X-List-Unsubscribe: Send email to mailusers-request@2rosenthals.com X-List-Owner: mailusers-owner@2rosenthals.com Thanks, Christian. A couple quick questions, below: On 10/19/2004 06:59 pm, Christian Langanke thus wrote : > > Hi *, > > I released a test version to > > http://www.clanganke.de/test/deb103_1004.zip > > This includes the standalone executable only. If you use it, make sure > that you stop any XCenter running the widget. > > New features: > new startup properties page for enable/disable radio > > new submenu for to (reconfigure) or disable the IP interface bound > to the wifi nic. This should help for scenario 3, when you want to > switch from wifi nic to wired nic, at least you can free up the DHCP > lease properly. I have no clue yet how a user can best issue a DHCP > request for the wired nic after having released the one from the wifi > nic - I am not sure if such a feature should be part of XWLAN and > where it could be integrated... OTOH we otherwise may have to come > back to the 2nd best solution: scripts... Perhaps a page in the profile properties for what to do when switching from the wireless connection, with options: * Do nothing * Activate wired interface * Ask me what to do Of course, when initially deactivating the wired interface, it would probably be necessary to record the IP configuration (static or dynamic) in order to bring it back up in the same state. > > conflict detection: whenever XWLAN configures the IP interface for > the wifi nic (either with a static address or by DHCP), XWLAN checks > if any other interface is configured for the same IP segment. If so, > a popup asks to either disable the conflicting (cabled) interface or > to take back the configuration for the wifi nic. Check the config of > both lan interfaces with ifconfig before and after you pressed either > buttons - it should have deleted either interface to resolve the > conflict. > > the code executing the DHCP config/unconfig now issues dhcpmon > calls only (no more kill of DHCPCD.EXE) > How are you doing this? Is there an API for DHCPMON? > whenever the configuration of the wifi nic IP has been completed, > XWLAN flushes the ARP cache (!!). I think this has not been noticed in > the previous discussions, but is very important, once the same router > needs to be reached over a different interface. If the arp cache is > not flushed, the arp entry will make the stack stick to the hardware > used last time, even when the IP interface has been > deleted.Interestingly, it is not even necessary to kick out obsolete > "duplicate" entries of net routes out of the routing table (see > ntetstat -r) after having switched the default route from lan0 to > lan1(or vice versa) - even if there are still net routes pointing to > the now unavailable interface (ssee rightost column of netstat -r), > the IP stack manages to find the correct route once the arp cache is > flushed. > Yes, this is a very good point, which we have discussed a few times on this list with regard to Neil's scripts. I thought, though, that it would still be necessary to flush the routing table. This is a good tip. I'll give this one a try with my test setup over the weekend (don't want to mess with things until after the WiFi classes). Besides my Cisco card, I have a spare IBM High Rate PC card with me, so if the problems noted with 1.03 persist (as I expect they will, as I have been so late in shipping that other Cisco card to you!), I should at least be able to test this with the IBM. -- Lewis ------------------------------------------------------------ Lewis G Rosenthal, CNA Rosenthal & Rosenthal Accountants / Network Consultants New York / Northern Virginia www.2rosenthals.com Team OS/2 / NetWare Users International www.novell.com ------------------------------------------------------------ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 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) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=