Bugzilla – Bug 414
ipw2200 0.14 issues with scan list
Last modified: 2005-10-04 13:21:37
You need to log in before you can comment on or make changes to this bug.
The bug is ported by OS ML from matt@matt-land.com 11/23 Subject: ipw2200 0.14 issues. When I loaded up my ipw2200 driver and ran iwlist wlan0 scanning I got the following: wlan0 Scan completed : Cell 01 - Address: 00:11:95:18:BF:6E ESSID:"<hidden>" Protocol:IEEE 802.11g Mode:Master Channel:6 Encryption key:on Bit Rate:54 Mb/s Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54 Extra: RSSI: -21 dBm Extra: Last beacon: 1224ms ago Cell 02 - Address: 00:11:95:18:BF:6E ESSID:"<hidden>" Protocol:IEEE 802.11g Mode:Master Channel:6 Encryption key:on Bit Rate:54 Mb/s Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54 Extra: RSSI: -23 dBm Extra: Last beacon: 702ms ago Cell 03 - Address: 00:11:95:18:BF:6E ESSID:"<hidden>" Protocol:IEEE 802.11g Mode:Master Channel:6 Encryption key:on Bit Rate:54 Mb/s Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54 Extra: RSSI: -21 dBm Extra: Last beacon: 180ms ago Cell 04 - Address: 00:11:95:18:BF:6E ESSID:"<hidden>" Protocol:IEEE 802.11g Mode:Master Channel:6 Encryption key:on Bit Rate:54 Mb/s Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54 Extra: RSSI: -21 dBm Extra: Last beacon: 6ms ago Except there were 18 the first time I did it. Notice all of the mac addresses are the same. I can still connect to the AP fine, but it did not list my ap multiple times like this before.
Comments from rhl@izzlazz.dk 11/23: I see this as well. My Linksys WAP54G with hidden ESSID is listed 18 times as well, as long as I'm unassociated. Once I set up the ESSID and WEP key and associate with the AP, the number of times my AP is listed is reduced to 1-3, sometimes including one entry with the real ESSID, with the rest of the entries having "<hidden>" ESSID.
Created an attachment (id=127) [details] patch posted on mailing list Dec 1st 2004. Attaching a test patch that was posted by James to the mailing list on the 1st of December. Can you apply to 0.15 and see if it helps.
*** Bug 419 has been marked as a duplicate of this bug. ***
Fixed in 0.16
*** Bug 434 has been marked as a duplicate of this bug. ***
verified in 0.16.