[zd1211-devs] Re: cannot get on dhcp networks anymore
Status: Beta
Brought to you by:
mayne
From: John H. <mis...@gm...> - 2005-12-27 05:07:25
|
hmm, i went back to .38 and it worked. i wonder if that's part of the problem i was having w/wpa. On 12/26/05, John H. <mis...@gm...> wrote: > i don't know if this is with .48 or what, but if i do ifconfig wlan0 > up, it gets on a local open essid, but once i do dhclient wlan0, it is > no longer on that essid, and it never completes anymore, despite the > fact I can get on fine in windows. here is the output from just > trying it. why is it that it somehow sees that 192.168.3.1 is the > router, but cannot get the IP? > > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 > No DHCPOFFERS received. > Trying recorded lease 10.1.42.32 > PING 10.1.0.1 (10.1.0.1) from 10.1.42.32 wlan0: 56(84) bytes of data. > > --- 10.1.0.1 ping statistics --- > 3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2013= ms > , pipe 4 > Trying recorded lease 192.168.3.25 > PING 192.168.3.1 (192.168.3.1) from 192.168.3.25 wlan0: 56(84) bytes of d= ata. > > --- 192.168.3.1 ping statistics --- > 3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2013= ms > , pipe 4 > No working leases in persistent database - sleeping. > > > > 10.1.0.1 is another wireless network, and 192.168.3.1 is the correct > one. I have been using this successfully for some time, but since I > started trying to get wpa_supplicant working on a separate network, i > don't know if that caused it or what. dhcp over eth1, ethernet > network, works fine and i acquire an IP and can use network. > > help? > |