Re: Wireless association problem
- From: Bill Davidsen <davidsen@xxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 01 Feb 2006 22:00:04 GMT
Alan Adams wrote:
In message <I_rDf.4385$ur7.3797@xxxxxxxxxxxxxxxxxxxxxxxxxx> Bill Davidsen <davidsen@xxxxxxxxxxxxxxxxxxxxx> wrote:
I'm trying to get a laptop with ipw2200/Centrino modem working under Linux (FC4). The problem seems to be in getting the computer to associate with the AP, and I don't see a hint in any of the docs I found searching.
I can see the AP, actually a number of them in the building, and using iwlist the one to be used is showing its name (essid) and channel, and no encryption. Those are exactly the same parameters which work for Windows. But after I set the channel and essid, and verify with iwconfig that they are set, the connection doesn't associate. I have tried with the latest FC4 kernel and tools as of Jan 26, and with a kernel.org 2.6.15.1 kernel.
My experience with wireless networks is on Windows, but may be relevant.
The sequence is first associate, then sort out IP address (dhcp or static). You don't even HAVE TO use IP - potentially you could run other protocols - it's just a transport after all.
The situation described above strongly suggests to me that the encryption settings of the AP and NIC don't match. This happens sometimes on Windows when the vendors are different. Keys can be entered either as hex data, or ASCII equivalents. I find some interfaces will accept either, some only one or the other, and in one case, the hex has to be in uppercase.
The problem is that none of the AP use any encryption at all. Just the network name to tell them apart. Connecting with Windows works, without providing any type of access code.
I guess Linux wireless isn't quite there yet, I was hoping I was just missing a step.
It doesn't usually result in an error message - just a failure to associate.
I also found one case where I could change the ESSID or the encryption, and associate, but if I changed both it failed. This was fixed by a driver upgrade.
Good luck!
Thanks, I'm out of things to try, so the idea is going to have to scrubbed for the moment.
Has anyone a pointer to better doc or other idea? The docs I have indicate that I should see an association, and can then set the IP (ifconfig) or request one (dhcpcd or dhclient). It seems that there's some "now do it!" step so obvious that it isn't listed, or maybe it's one of those "here magic occurs" things which is supposed to just work.
Oh, I tried to set the IP and just use it (someone suggested that) but use doesn't force association, either.
-- bill davidsen SBC/Prodigy Yorktown Heights NY data center http://newsgroups.news.prodigy.com .
- Follow-Ups:
- Re: Wireless association problem
- From: Unruh
- Re: Wireless association problem
- Prev by Date: Re: yum update fedora 4 undefined symbol: krb5_prompter_pocix
- Next by Date: Re: Windows to Linux - HELP!
- Previous by thread: Re: yum update fedora 4 undefined symbol: krb5_prompter_pocix
- Next by thread: Re: Wireless association problem
- Index(es):
Relevant Pages
|
