On Wed, Nov 18, 2009 at 08:14:10PM +0100, Florian Engelhardt wrote: > On Tue, 17 Nov 2009 17:11:05 -0500, Bob Copeland <m...@bobcopeland.com> > wrote: > > > Hmm, the mac addresses are different and they have at least a valid > > OUI: > > > > 00:80:48:5C:86:5D > > 00:80:48:5C:86:43 > > Nope, this is not my AP, but i had the same behavior with my AP, but as [added Luis,list back to cc]
Ok, fair enough. We should try to figure out where the 0x5d and 0x43 come from. It could be memory corruption, for example, but 0x5d and 0x43 aren't poison values. You may try turning on slub/slab debugging just to be sure. Does this happen frequently enough that you'd be able to capture some packets before it happens? Something like: $ sudo su # iw dev wlan0 interface add monitor wlan0.mon # ifconfig wlan0.mon up # wireshark -i wlan0.mon & # iw dev wlan0 scan [wait for some quantity of beacons from the malfunctioning node, and save the packet trace] -- Bob Copeland %% www.bobcopeland.com _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
