Re: dhclient and ralink wlan problem

On Tue, Aug 09, 2005 at 01:26:57PM +0300, Juho Vuori wrote:
> Hello,
> 
> The new dhclient is not able to assign an IP address for my computer on 
> one particular wlan-network (the public wlan of University of Helsinki). 
> Everywhere else it works fine, both on wireless and wired networks.
> 
> Here is a log of what happens:
> 
> # ifconfig ral0
> ral0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>        inet6 fe80::208:a1ff:fe8a:d7cb%ral0 prefixlen 64 scopeid 0x5
>        inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
>        ether 00:08:a1:8a:d7:cb
>        media: IEEE 802.11 Wireless Ethernet autoselect (DS/1Mbps)
>        status: no carrier
>        ssid ""
>        authmode OPEN privacy OFF txpowmax 100 bintval 100
> # dhclient ral0
> DHCPDISCOVER on ral0 to 255.255.255.255 port 67 interval 5
> DHCPDISCOVER on ral0 to 255.255.255.255 port 67 interval 14
> DHCPDISCOVER on ral0 to 255.255.255.255 port 67 interval 11
> DHCPDISCOVER on ral0 to 255.255.255.255 port 67 interval 19
> DHCPDISCOVER on ral0 to 255.255.255.255 port 67 interval 12
> No DHCPOFFERS received.
> No working leases in persistent database - sleeping.
> 
> # ifconfig ral0
> ral0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>        inet6 fe80::208:a1ff:fe8a:d7cb%ral0 prefixlen 64 scopeid 0x5
>        inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
>        ether 00:08:a1:8a:d7:cb
>        media: IEEE 802.11 Wireless Ethernet autoselect (DS/1Mbps)
>        status: no carrier
>        ssid "Univ Helsinki HUPnet" channel 1
>        authmode OPEN privacy OFF txpowmax 100 protmode CTS bintval 100
> #
> 
> 
> Note that the ssid got set up correctly, but still no DHCP offer was 
> received.
>
> I'm happy to help debugging this, but I'm not exactly sure how to go on 
> with this as I don't know how DHCP or WLAN work. tcpdump -i ral0 is 
> unable to capture any packets of any type, which is wierd; some sort of 
> packets definately were transported, as the computer got the ssid right.
>
> Also, after a lot of trials, dhclient starts complaining about full send 
> buffer, suggesting the problem is at least partly in the ral-driver, 
> which for some reason is unable to send DHCP-packets.
> 
> And also related to that, when I tried to detach the (PCMCIA) WLAN-card 
> in order to reset the driver and the send buffer, the machine  just 
> reset itself.

This looks like a ral issue.  The ssid seems to be being found, but you
aren't associating.  As such this doesn't appear to be dhclient issue.
Unfortunately, the author of that driver hasn't been very active lately.

-- Brooks

--
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4