Poštni seznam arhiviranih sporo?il

Od: "Lewis G Rosenthal" <os2-wireless_users@2rosenthals.com> Glava
Izvorno E-sporo?ilo
Zadeva: Re: [OS2Wireless] Re: Cannot get DHCP
Datum: Mon, 12 Oct 2009 22:52:39 -0400
Za: OS/2 Wireless Users Mailing List <os2-wireless_users@2rosenthals.com>

Hi, again. Let's see if we can suss out the details, here...

On 10/12/09 06:25 pm, Stuart Updike thus wrote :
Lewis G Rosenthal wrote:
Hi, Stu...

On 10/12/09 02:12 pm, Stuart Updike thus wrote :
Hello all,

I have just installed eCS 2.0rc7 on my ThinkPad T23. I have no
problem using the wired connection to my router, a Netgear MR814V2.
However, when I enable the wireless card, I cannot connect. At this
point, it is an open system. The DHCP Monitor reports the DHCP client
is not running. The XWlan widget is showing full green on connection
strength. I tried looking at the sample script, but it is Greek to me.

Any ideas?

Ensure that the DHCP monitor is indeed looking at the correct
interface (usually, lan1 vs lan0). Once you've done that, try getting
dhcp to start on the interface from a command line, in case there is
any valuable feedback:

dhcpmon -t
route -fh
arp -f
dhcpstrt -i lan1

(the default timeout of 60 seconds should give you an indication as to
whether or not we're even finding a DHCP server on the other end)

Make sure that you are seeing a MAC address for your Wi-Fi card (this
should be the case; it's only the newer Intels which have this
annoyance, AFAICR). I'm not very familiar with the Netgear MR812V2, so
I can't offer up any help as to what you might want to check on that
end, sorry.

Hi Lewis,

The wired connection to the router can get a lease very quickly, but the wireless never gets a lease. I do not know how to query the wireless card for its MAC address, but it is labeled on the bottom of the machine and it does show up in the router's list of connected devices.

netstat -n <Enter>

should yield you something along the lines of:

   Interface 0  Ethernet-Csmacd
   physical address    00016ccbf480      MTU 1500

(among other info; use | more to pause the display). This was taken with my wired interface active and my wireless turned off.
I ran your suggested CMD file.  The response is included below:

Well, actually those were just manual commands to enter at the prompt. :-)  Same difference, though...

[E:\TEMP]dhcpmon -t

[E:\TEMP]route -fh
default              192.168.0.1   done

[E:\TEMP]arp -f
192.168.0.1 (192.168.0.1) deleted.
192.168.0.255 (192.168.0.255) deleted.

[E:\TEMP]dhcpstrt -i lan1
DHCPSTRT: Waiting for DHCP client.(maximum wait = 60 seconds)


DHCPSTRT: DHCP client did not start.

----------------End of output-----------------------

Interesting. Is lan1 indeed the number of your wireless adapter?
I tried pinging the IP addresses of the wireless card (192.168.0.3) and the router (192.168.0.1 ). Results below:

If you don;t get DHCP info, then how do you have an address in your wireless interface?
PING 192.168.0.3: 56 data bytes
64 bytes from 192.168.0.3: icmp_seq=0. time=0. ms
64 bytes from 192.168.0.3: icmp_seq=1. time=0. ms
64 bytes from 192.168.0.3: icmp_seq=2. time=0. ms
64 bytes from 192.168.0.3: icmp_seq=3. time=0. ms
64 bytes from 192.168.0.3: icmp_seq=4. time=0. ms

----192.168.0.3 PING Statistics----
5 packets transmitted, 5 packets received, 0% packet loss
round-trip (ms)  min/avg/max = 0/0/0
---------------------End------------------------

Looks like it's working to me.
PING 192.168.0.1: 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0. time=0. ms
64 bytes from 192.168.0.1: icmp_seq=1. time=0. ms
64 bytes from 192.168.0.1: icmp_seq=2. time=0. ms

----192.168.0.1 PING Statistics----
3 packets transmitted, 3 packets received, 0% packet loss
round-trip (ms)  min/avg/max = 0/0/0

Looks like that's working, too.
--------------------------End-------------------------------
Just in case it might help, here's the download from Craig Hart's sniffer:

You've already told me that you can get a green indicator in XWLAN. If we couldn't recognize the hardware to initialize it, you wouldn't get that far, let alone be able to ping something...

<snip>

Thank you for your help!!

Surely. I'm just a bit confused as to what you've got going on.

Please post your PROTOCOL.INI when you get a chance.
Have a great day!

Thanks! You, too!

--
Lewis
-------------------------------------------------------------
Lewis G Rosenthal, CNA, CLP, CLE
Rosenthal & Rosenthal, LLC                www.2rosenthals.com
Need a managed Wi-Fi hotspot?                www.hautspot.com
Secure, stable, operating system          www.ecomstation.com
-------------------------------------------------------------


Naro?iti: Poro?ilo (Feed), Izvle?ek (Digest), Indeks.
Odjava
E-pošta za mojstra za sezname