From: Wojciech Dubowik <Wojciech.Dubowik@neratec.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] mac80211: fix auth/assoc timeout handling
Date: Thu, 14 Feb 2013 12:01:30 +0100 [thread overview]
Message-ID: <511CC40A.6080104@neratec.com> (raw)
In-Reply-To: <1360839938.8210.0.camel@jlt4.sipsolutions.net>
On 02/14/2013 12:05 PM, Johannes Berg wrote:
> On Thu, 2013-02-14 at 11:50 +0100, Wojciech Dubowik wrote:
>> I am getting some disconnections becasue of failed
>> nullfunc in my ath9k ap+sta test setup. The auth/assoc
>> don't timeout but nullfunc does.
>>
>> I have checked in wireshark and all nullfunc were
>> properly acknowledged.
>> Attached syslog + iw event.
>>
>> Do you have any idea where it comes from or should
>> I start looking at it?
> No idea right now, off the top of my head, sorry.
>
> johannes
>
So I will start digging.
Wojtek
next prev parent reply other threads:[~2013-02-14 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 9:29 [PATCH v2] mac80211: fix auth/assoc timeout handling Johannes Berg
2013-02-14 10:50 ` Wojciech Dubowik
2013-02-14 11:05 ` Johannes Berg
2013-02-14 11:01 ` Wojciech Dubowik [this message]
2013-02-14 17:29 ` Johannes Berg
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=511CC40A.6080104@neratec.com \
--to=wojciech.dubowik@neratec.com \
--cc=johannes@sipsolutions.net \
--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