Bug 1659 - The driver is unable to reassociate with different AP using the same SSID
: The driver is unable to reassociate with different AP using the same SSID
Status: VERIFIED WONTFIX
: iwlwifi
AP to AP roaming
: unspecified
: IBM __UNSPECIFIED__
: P2 enhancement
Assigned To:
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2008-04-23 16:35 by
Modified: 2009-01-08 01:35 (History)


Attachments
dmesg.log (122.25 KB, text/plain)
2008-04-23 16:35, Lukas Hejtmanek
Details


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2008-04-23 16:35:30
Created an attachment (id=1425) [details]
dmesg.log

As I'm moving around a hotel, there are many APs using SSID Internet2. However,
if I am out of range from an AP, the driver should switch to another one. It
does not happen. To switch the APs I must remove the iwl4965 module and load it
again.

For some strange reason, it partly worked while I was creating the attached
debug log. For the first time, I was assocated with 00:12:7f:3f:cc:80. I moved
to different one and lost signal with cc:80. I did ifconfig wlan0 down and up
and it gets associated with 00:12:7f:fa:7b:e0. Well, it should work without
ifdown/up. However, moving to another AP, it lost the signal again and againt
it did not associate with the new one. ifup/down returned association back to
cc:80 but it was still out of range. So I had to remove the driver module and
load it again to get associated with 00:12:80:03:61:40.

The box is Lenovo Thinkpad T61. Using 2.6.25-git3 kernel from kernel.org
without additional patches.

this is my config:
CONFIG_IWLCORE=m
CONFIG_IWLWIFI_LEDS=y
CONFIG_IWLWIFI_RFKILL=y
CONFIG_IWL4965=m
CONFIG_IWL4965_HT=y
CONFIG_IWL4965_SPECTRUM_MEASUREMENT=y
CONFIG_IWL4965_SENSITIVITY=y
CONFIG_IWLWIFI_DEBUG=y
------- Comment #1 From 2008-04-23 16:39:41 -------
I also found out that iwconfig wlan0 ap auto should invoke reassociation to the
strongest AP according to man page. It seems it does nothing.
------- Comment #2 From 2008-05-23 09:12:08 -------
I believe the driver doesn't support roaming, and instead it relays on user
space tool such as the network manager. Yi?
------- Comment #3 From 2008-07-08 00:43:36 -------
Roaming can be done by NetworkManager or directly running command
"wpa_supplicant". But once we connect with one AP by "wpa_supplicant", even
there's another station/AP nearby which has stronger signal quality, it won't
roam to a new station.
------- Comment #4 From 2009-01-07 19:34:04 -------
Driver will not support roaming. Instead user can use some user space tools 
(such as wpa_supplicant) for it.
------- Comment #5 From 2009-01-07 23:55:38 -------
(In reply to comment #4)
> Driver will not support roaming. Instead user can use some user space tools 
> (such as wpa_supplicant) for it.
> 

is this kind of a bad joke?
------- Comment #6 From 2009-01-08 01:02:57 -------
Well, maybe you can use user space tools such as wpa_supplicant, NetworkManager
to do th roaming?
------- Comment #7 From 2009-01-08 01:30:47 -------
(In reply to comment #6)
> Well, maybe you can use user space tools such as wpa_supplicant, NetworkManager
> to do th roaming?
> 

well, do not know whether wpa_supplicant can handle non-authenticated networks,
and craps like the NetworkManager I do not use. Why did this work just fine
with the older cards? (IWL2915)
------- Comment #8 From 2009-01-08 01:35:13 -------
Yes. You can use wpa_supplicant to assocate to these networks. For example, for
open authentication without WEP, you can use configure file similar to:

network={
        ssid="plaintext-test"
        key_mgmt=NONE
}