slack 9.1 -- PCMCIA wireless card + DHCP -- can't pull an IP

rfrenz20 · 02-03-2004, 11:10 PM

Hi,
I've found a lot of help on this site, so I'm hoping someone can help me with my new problem. I have a Belkin F5D6020 version 2 wireless pcmcia card in an IBM ThinkPad running Slack 9.1. This card uses the atmelwlan drivers from sourceforge. I have successfully used this card with Slack 9.0, Fedora Core 1, and Mandrake 9.1. I followed the same steps to set it up this time, and all seemed to go well. However, I cannot pull an IP address from my schools DHCP server using dhcpcd. I keep getting "Timed out waiting for valid response from DHCP server" in my dhcpcd log file. I'm not sure where to go now, because everything else looks as it should: I'm associated with the access point (correct info from 'iwconfig', updating everytime I call it), and all my script settings are the same as they were in Slack 9.0 (with slight changes). Does anyone have anything I should try next? Please let me know if more output is needed.

Thanks in advance,

Ryan

Misel · 02-04-2004, 07:44 AM

Maybe the timeout of the client is too short. I had trouble with a Zyxel router (wired though) and slackware at the beginning.

Astro · 02-04-2004, 08:36 AM

Check your essid and make sure if you need one to be on the schools network that it is set. In retrospect actually when I needed to get on our schools network sometimes I had to set the essid to off/any for it to work, not sure how that goes. I've been having a TON of trouble with a dwl650+, and ended up getting mad and completely taking the card apart... now I have a nice keychain. (The card was deffective btw, damn tigerdirect and their refurbs) anyways... the dwl650 (not +) that I bought is HORRIBLY unsupported in *nix supposedly using the Prism3 chip, but if you search the forum for it people had an awful time with it. I have since bought that, tried it and sold it already and ordered a Netgear MA401, thank goodness a card that will actually work. ... so that was way off topic but, try the essid thing, and make sure the access point you are associated with is in range... I find sometimes I had to jump channels to a closer one... once you try to get an ip and it doesn't grap one look at the dmesg output and see if it throws you any errors.