On Wed, 2013-07-31 at 08:55 +0200, Arkadiusz Miskiewicz wrote: > It basically reports: > [79477.496067] eth1: AP 68:7f:74:06:b3:1b changed bandwidth, new config is 2422 MHz, width 1 (2422/0 MHz) > [79477.496072] eth1: AP 68:7f:74:06:b3:1b changed bandwidth in a way we can't support - disconnect > > (note I have two wrt160nl here and problem happens with both) > > Any hints on why "we can't support" configuration issued by this (common) AP? As far as I can tell, it seems to be an AP bug, but I had no idea this was so common. Testing with hostapd, I can switch bandwidth between 20 and 40 MHz just fine, and it only prints "new config is ..." and then carries on. Since you seem to be able to reproduce this easily, can you run tcpdump with the beacon info? sudo iw wlan0 interface add moni0 type monitor flags none sudo ip link set moni0 up sudo tcpdump -i moni0 -s0 -w /tmp/dump and then wait for the problem to occur and send me (privately) the dump file (best compressed)? There's also a bug here: https://bugzilla.redhat.com/show_bug.cgi?id=981445 johannes -- 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
