X-Account-Key: account1 X-UIDL: 41461 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 20050106173625-48072-7 ; Thu, 06 Jan 2005 17:36:25 -0500 (Hethmon Brothers Smtpd) id 20050106173623-7463-7 ; Thu, 06 Jan 2005 17:36:23 -0500 Received: from mx1.mailhop.org ([63.208.196.170]) by mxout2.mailhop.org with esmtp (Exim 4.43) id 1CmgEw-000EfT-6u for os2-wireless_users@2rosenthals.com; Thu, 06 Jan 2005 17:36:23 -0500 Received: from outmx004.isp.belgacom.be ([195.238.2.101]) by mx1.mailhop.org with esmtp (Exim 4.42) id 1CmgEw-0007SM-0q for os2-wireless_users@2rosenthals.com; Thu, 06 Jan 2005 17:36:22 -0500 Received: from outmx004.isp.belgacom.be (localhost [127.0.0.1]) by outmx004.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with ESMTP id j06MaHRC029240 for ; Thu, 6 Jan 2005 23:36:17 +0100 (envelope-from ) Received: from [192.168.2.100] (115.124-136-217.adsl.skynet.be [217.136.124.115]) by outmx004.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with ESMTP id j06Ma807029165; Thu, 6 Jan 2005 23:36:08 +0100 (envelope-from ) Message-ID: <41DDBD7D.2070504@hccnet.nl> Organization: CFM$-FC (Coalition for Micro$oft-Free Computing) User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; nl-NL; rv:1.7.5) Gecko/20041220 X-Accept-Language: nl-NL,nl-BE,nl MIME-Version: 1.0 References: <41DB0D2F.3070504@hccnet.nl> <41DCC86C.2070908@2rosenthals.com> <41DD00FA.3030000@hccnet.nl> <41DD65CA.3000105@2rosenthals.com> In-Reply-To: <41DD65CA.3000105@2rosenthals.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mail-Handler: MailHop by DynDNS.org X-Spam-Score: -2.6 (--) Date: Thu, 06 Jan 2005 23:36:45 +0100 Sender: os2-wireless_users-owner X-Listname: os2-wireless_users@2rosenthals.com Reply-To: os2-wireless_users@2rosenthals.com From: Kris Steenhaut To: os2-wireless_users@2rosenthals.com Subject: [OS2Wireless] wlanstat question X-List-Unsubscribe: Send email to mailusers-request@2rosenthals.com X-List-Owner: mailusers-owner@2rosenthals.com Lewis G Rosenthal schreef: >> too). >> > But at the client side running ifconfig lan1 you don't see an address > assigned, correct? What does netstat -n show for lan1 (try netstat -n > | more or netstat -n > netstat.txt)? > When when wlanstat is set to "manual" to 192.168.2.102 NETSTAT -R destination router netmask metric flags intrf default 192.168.2.1 0.0.0.0 1 UGSP lan1 127.0.0.1 127.0.0.1 255.255.255.255 0 UH lo 192.168.2 192.168.2.102 255.255.255.0 0 UC lan1 195.238.2.21 192.168.2.1 255.255.255.255 1 UGHW3 lan1 NETSTAT -N Interface 1 Ethernet-Csmacd physical address 00022d30d2fb MTU 1500 speed 11000000 bits/sec unicast packets received 125 broadcast packets received 0 total bytes received 8432 unicast packets sent 136 broadcast packets sent 191 total bytes sent 33739 packets discarded on transmission 0 packets discarded on reception 0 received packets in error 0 errors trying to send 0 packets received in unsupported protocols 0 Interface 9 Software Loopback physical address 000000000000 MTU 1536 speed 0 bits/sec unicast packets received 0 broadcast packets received 0 total bytes received 0 unicast packets sent 10 broadcast packets sent 0 total bytes sent 4780 packets discarded on transmission 0 packets discarded on reception 0 received packets in error 0 errors trying to send 0 packets received in unsupported protocols 0 and IMMEDIATELY AFTER (after having disabled and restarted tcpip interface of course): When when wlanstat is set to "DHCP" : NETSTAT -R destination router netmask metric flags intrf 127.0.0.1 127.0.0.1 255.255.255.255 0 UH lo NETSTAT -N Interface 1 Ethernet-Csmacd physical address 00022d30d2fb MTU 1500 speed 11000000 bits/sec unicast packets received 159 broadcast packets received 0 total bytes received 10818 unicast packets sent 173 broadcast packets sent 217 total bytes sent 40326 packets discarded on transmission 0 packets discarded on reception 0 received packets in error 0 errors trying to send 0 packets received in unsupported protocols 0 Interface 9 Software Loopback physical address 000000000000 MTU 1536 speed 0 bits/sec unicast packets received 0 broadcast packets received 0 total bytes received 0 unicast packets sent 15 broadcast packets sent 0 total bytes sent 6680 packets discarded on transmission 0 packets discarded on reception 0 received packets in error 0 errors trying to send 0 packets received in unsupported protocols 0 > So after clearing 192.168.2.101 at the router, the router still > assigns it again to the card Indeed. > but the card doesn't see the address? I'm not knowledgeable enough to sort that out. > Or.... you haven't actually cleared the DHCPTAB in the router (look > for something in the router to release or delete the client)? > Have already done everything a simple human being can think of: power off the router, reset the router, disable DHCP and enable again. >> - when in xwlan set to "manually" and ip address 192.168.2.102, then >> connection is established and working for 100 %. >> > If the router has truly assigned an address to the correct MAC of the > card, using a second address with the same MAC (on the same network) > should generate errors. While I am typing now, and while laptop and PC are truly connected to each other and both as well to the Internet (thus wlanstat set to use manually 192.168.2.102) , the DHCP log of the router shows: ip=192.168.2.100 mac=00-A0-24-7C-8D-33 (= main pc 3com card) ip=192.168.2.101 mac=00-02-2D-30-D2-FB (= mac address jacaranda card) > If it doesn;t we may be looking at the wrong side of the equation, and > the problem may lie in the router's firmware. > Hmm, may I remind you, before you bothering all, I already have done the obvious, that is: just the Artem driver in the config.sys just in setup.cmd: dhcpstrt -i lan0 and the loopback etc. Should have worked, shouldn't it? But the answer was "dhcp server didn't get parameters". The same exercise with the Genprism drivers do give exactly the same result ""dhcp server didn't get parameters". It is always like that when dhcp is set to a wireless lanx (jacaranda). OTOH, dhcp works as it should when set to a wired lanx (onboard intel nic). I have checked with Frank Vos, he has exactly the same card as I have, and at his Laptop, a T23 IIRC, DHCP is working with Artem drivers as well as with Genprism (remember, Artem drivers don't work here at all, except for the flashing lights). I still wonder whether the internal wireless nic (intel) of my T41 couldn't be in the game. After all, there is no option in the bios to disable the intel onboard nic. Meaning it is always powered on. A radiating device that is powered on, always radiates, doesn't it? -- Groeten uit Gent, Kris =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 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) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=