From: poma <pomidorabelisima@gmail.com>
To: "Felix Fietkau" <nbd@openwrt.org>,
"Laurențiu Nicola" <lnicola@dend.ro>,
"Emmanuel Grumbach" <egrumbach@gmail.com>
Cc: Dan Williams <dcbw@redhat.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: iwlwifi: Reason 7 periodic disconnect
Date: Tue, 21 Oct 2014 13:00:57 +0200 [thread overview]
Message-ID: <54463CE9.3060400@gmail.com> (raw)
In-Reply-To: <54461AEF.7040304@openwrt.org>
On 21.10.2014 10:35, Felix Fietkau wrote:
> On 2014-10-21 10:23, Laurențiu Nicola wrote:
>> It's an ASUS RT-N66U running NEWD-2/K3X from r24160.
> This is a Broadcom based device, so it should behave in the same way as
> other APs/Routers running the Broadcom drivers.
> The driver should only send Reason 7 when receiving a PS-Poll, BlockAck,
> BlockAckReq or Action frame from a station that's not associated, so
> probably it has already kicked out your iwlwifi client earlier. Not sure
> why that doesn't show up in the log though.
>
Whether this might refer to the Station Control Block Timeout value
http://www.dd-wrt.com/wiki/index.php/Wl#scb_timeout
...
scb_timeout
AP only: inactivity timeout value for authenticated stas
poma
next prev parent reply other threads:[~2014-10-21 11:01 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 12:48 iwlwifi: Reason 7 periodic disconnect Laurențiu Nicola
2014-10-16 20:42 ` Emmanuel Grumbach
2014-10-17 1:53 ` Dan Williams
2014-10-19 20:48 ` Laurențiu Nicola
2014-10-20 4:52 ` Emmanuel Grumbach
2014-10-20 5:30 ` Laurențiu Nicola
2014-10-20 7:06 ` Emmanuel Grumbach
2014-10-20 7:12 ` Emmanuel Grumbach
2014-10-20 7:22 ` Laurențiu Nicola
2014-10-20 8:23 ` Emmanuel Grumbach
2014-10-20 19:29 ` Laurențiu Nicola
2014-10-21 5:02 ` Emmanuel Grumbach
2014-10-21 5:31 ` Emmanuel Grumbach
2014-10-21 6:36 ` Krishna Chaitanya
2014-10-21 6:37 ` Krishna Chaitanya
2014-10-21 7:04 ` Emmanuel Grumbach
2014-10-21 7:22 ` Krishna Chaitanya
2014-10-21 8:07 ` Laurențiu Nicola
2014-10-21 7:28 ` Laurențiu Nicola
2014-10-21 8:02 ` Emmanuel Grumbach
2014-10-21 8:20 ` Felix Fietkau
2014-10-21 8:23 ` Laurențiu Nicola
2014-10-21 8:35 ` Felix Fietkau
2014-10-21 8:37 ` Laurențiu Nicola
2014-10-21 8:44 ` Emmanuel Grumbach
2014-10-21 9:05 ` Krishna Chaitanya
2014-10-21 9:16 ` Emmanuel Grumbach
2014-10-21 9:57 ` Krishna Chaitanya
2014-10-21 11:00 ` poma [this message]
2014-10-21 19:56 ` Laurențiu Nicola
2014-10-22 9:10 ` Emmanuel Grumbach
2014-10-22 21:53 ` Laurențiu Nicola
2014-10-23 5:21 ` Emmanuel Grumbach
2014-10-23 7:30 ` Laurențiu Nicola
2014-10-23 8:07 ` Emmanuel Grumbach
2014-10-23 16:02 ` Laurențiu Nicola
2014-10-23 16:46 ` Emmanuel Grumbach
2014-10-23 17:38 ` Laurențiu Nicola
2014-10-23 19:28 ` Emmanuel Grumbach
2014-10-23 19:42 ` Laurențiu Nicola
2014-10-23 19:55 ` Emmanuel Grumbach
2014-10-23 20:07 ` Laurențiu Nicola
2014-10-23 20:16 ` Emmanuel Grumbach
2014-10-23 20:27 ` Laurențiu Nicola
2014-10-23 20:33 ` Emmanuel Grumbach
2014-10-24 5:32 ` Emmanuel Grumbach
2014-10-24 8:34 ` Laurențiu Nicola
2014-10-24 10:26 ` Emmanuel Grumbach
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=54463CE9.3060400@gmail.com \
--to=pomidorabelisima@gmail.com \
--cc=dcbw@redhat.com \
--cc=egrumbach@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lnicola@dend.ro \
--cc=nbd@openwrt.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).