From: Johannes Berg <johannes@sipsolutions.net>
To: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>,
Andy Isaacson <adi@hexapodia.org>
Cc: linux-wireless@vger.kernel.org, ilw@linux.intel.com
Subject: Re: AP changed bandwidth, new config is ... changed bandwidth in a way we can't support - disconnect - why? (intel advanced-n 6250)
Date: Wed, 31 Jul 2013 10:50:32 +0200 [thread overview]
Message-ID: <1375260632.8289.10.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <201307310855.28080.a.miskiewicz@gmail.com> (sfid-20130731_085534_667847_F735B965)
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
next prev parent reply other threads:[~2013-07-31 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 6:55 AP changed bandwidth, new config is ... changed bandwidth in a way we can't support - disconnect - why? (intel advanced-n 6250) Arkadiusz Miskiewicz
2013-07-31 8:50 ` Johannes Berg [this message]
2013-07-31 9:28 ` Arkadiusz Miskiewicz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1375260632.8289.10.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=a.miskiewicz@gmail.com \
--cc=adi@hexapodia.org \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).