[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dbbc8c3e898ec499f30a6ac1f262666ced6905fb.camel@sipsolutions.net>
Date: Tue, 29 Oct 2019 10:03:02 +0100
From: Johannes Berg <johannes@...solutions.net>
To: Koen Vandeputte <koen.vandeputte@...ntric.com>,
Krzysztof HaĆasa <khalasa@...p.pl>
Cc: "David S. Miller" <davem@...emloft.net>,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] 802.11n IBSS: wlan0 stops receiving packets due to
aggregation after sender reboot
On Tue, 2019-10-29 at 09:41 +0100, Koen Vandeputte wrote:
> I can confirm the issue as I'm also seeing this sometimes in the field here.
>
> Sometimes when a devices goes out of range and then re-enters,
> the link refuses to "come up", as in rx looks to be "stuck" without any
> reports in system log or locking issues (lockdep enabled)
Right. I've recently debugged this due to issues in distributed
beaconing (rather than moving in/out of range), but I guess it would be
relatively simple to reproduce this with wmediumd, if that can be
controlled dynamically?
What kernel are you running? You could check if you have
95697f9907bf ("mac80211: accept deauth frames in IBSS mode")
4b08d1b6a994 ("mac80211: IBSS: send deauth when expiring inactive STAs")
which might help somewhat, but don't fully cover the case of moving out
of range.
johannes
Powered by blists - more mailing lists