Re: [RFC] mesh: allow processing authentication frames in blocked state

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Feb 18, 2019 at 01:04:42PM +0100, Felix Fietkau wrote:
> If authentication fails repeatedly e.g. because of a weak signal, the link
> can end up in blocked state. If one of the nodes tries to establish a link
> again before it is unblocked on the other side, it will block the link to
> that other side. The same happens on the other side when it unblocks the
> link. In that scenario, the link never recovers on its own.
> 
> To fix this, allow restarting authentication even if the link is in blocked
> state, but don't initiate the attempt until the blocked period is over.

I have not seen any comments on this so far. Was there any addition work
going on in this area?

PLINK_BLOCKED seems to be a implementation specific state, i.e., not
defined in IEEE Std 802.11-2016. The nl80211 part for it
(NL80211_PLINK_BLOCKED) is clearly defined to discard all frames ("all
frames transmitted from this mesh plink are discarded"), so this patch
would seem to be against that definition. As such, I'd like to see
nl80211.h in the kernel updated first if there is desire to change
behavior the plink blocked state.
 
-- 
Jouni Malinen                                            PGP id EFC895FA

_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap



[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux