Mailing List os2-wireless_users@2rosenthals.com Archived Message #3947 previous message next message back to list

From: Kris Steenhaut <os2-wireless_users@2rosenthals.com> Full Headers
Undecoded message
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Subject: [OS2Wireless] wlanstat question
Date: Thu, 06 Jan 2005 23:36:45 +0100
To: os2-wireless_users@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)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Subscribe: Feed, Digest, Index.
Unsubscribe
Mail to ListMaster