On Wed, Nov 18, 2009 at 08:31:56PM +0100, Florian Engelhardt wrote: > On Wed, 18 Nov 2009 11:18:01 -0800 > "Luis R. Rodriguez" <mcgrof@xxxxxxxxx> wrote: > > > On Wed, Nov 18, 2009 at 11:09 AM, Florian Engelhardt <flo@xxxxxxxxxx> > > wrote: > > > On Tue, 17 Nov 2009 13:35:24 -0800, "Luis R. Rodriguez" > > > <mcgrof@xxxxxxxxx> wrote: > > > > > >> That's wild. What kernel are you using? > > > > > > # uname -a > > > Linux eka 2.6.31-ARCH #1 SMP PREEMPT Tue Nov 10 19:48:17 CET 2009 > > > i686 Intel(R) Atom(TM) CPU N270 @ 1.60GHz GenuineIntel GNU/Linux > > > > > >> Have you tried: > > >> http://wireless.kernel.org/en/users/Download/stable > > >> or > > >> http://wireless.kernel.org/en/users/Download > > > > > > Tried both, no change. > > > > > >> Can you provide the output of 'iw list', your dmesg, and your 'iw > > >> dev wlan0 scan'. > > > > > > See attached files. Despite that i can add one additional > > > information: I have a second Laptop with Intel WLAN Chip, and it > > > shows exactly the same behaviour, MA-WLAN two, sometimes three > > > times, with none of the addresses being correct. > > > > > > Somehow, i can not reproduce this kind of behaviour with my own > > > wlan. It shows up only one time, not multiple, but it did two days > > > ago on the ath5k chipset based netbook > > > > As Bob pointed out your scan shows two beacons received on different > > BSSes: > > > > 00:80:48:5c:86:5d > > 00:80:48:5c:86:48 > > > > The TSF on the second one seems odd though. Do you have access to the > > AP? Can you change the channel to see if you see the two beacons on a > > new channel? > > Can you try rebooting it? > > Sorry, no. I have no access to that AP, but i can ask the owner if he > may reboot it, or if he faces any problems with it. Yeah ask him for the actual MAC address of the BSS you are supposed to be connecting to. Did you tell him your cards are seeing two beacons from it? Might want to get a sniffer an capture two beacons to show this info. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
