Re: Wireless association problem

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.

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!

>
> 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.
>

--
Alan Adams, from Northamptonshire
alan.adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx
http://www.nckc.org.uk/
.

Relevant Pages

  • Re: Wireless association problem
    ... 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 and channel, and no encryption. ... Those are exactly the same parameters which work for Windows. ... I have tried with the latest FC4 kernel and tools as of Jan 26, and with a kernel.org 2.6.15.1 kernel. ... I guess Linux wireless isn't quite there yet, I was hoping I was just ...
    (comp.os.linux.setup)
  • Re: Wireless association problem
    ... >>>Linux (FC4). ... >> The situation described above strongly suggests to me that the encryption ... This happens sometimes on Windows ...
    (comp.os.linux.setup)
  • Re: Wireless association problem
    ... 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, ... Linux wireless IS there and works. ...
    (comp.os.linux.setup)
  • Re: Fedora amazes yet again
    ... > on Windows and loading/playing some songs, I rebooted into FC4 and was ... > surprised to find an iPod icon on my gnome desktop. ... FC4 seems to treat ... But in Windows it takes ...
    (Fedora)
  • Re: Fedora Core 4 features and programs
    ... What features and programs are included in Fedora Core 4? ... Once you install FC4, you can then learn how to find the applications you want and need which don't come with FC4 directly. ... I can do more on my FC4 box than on the Windows XP box that I have to use from time to time. ... allows me to search for applications depending on my needs. ...
    (Fedora)