[ath9k-devel] AuthSAE rekeying issues with ATH9K

Stam, Michel [FINT] <[email protected]> Thu, 14 Jul 2016 09:12:53 +0000
Newsgroups org.ath9k.lists.ath9k-devel
Message-ID <[email protected]>
Hi,

Periodically validating the keycache would work as far as I'm concerned, although I'm not sure that a patch for the ath9k would be accepted if that hits the mac80211/cfg80211 layers. This is why I did not look into this, figuring that this should be handled at ath9k level somehow. I did not check if it is possible to access the kernel keycache from within the ath9k driver, this might be an idea.

What I do see when calling iw dev mesh0 station dump is that there's an inactivity timer kept for all stations (=mesh nodes), so it should be possible.

As to TX/RX, I added a monitor interface on the receiving node, and using wireshark I could see packets arriving when the link was not working anymore. That, and the RX_DROP_MISC increasing seems to indicate an RX issue to me. But, if the transmitting end does not use the right key, this would yield the same result, as both ends need to agree on the same key for this to work.
Note that on both nodes I added some debugging to dump the contents of the registers, and that seems to be identical; what is written to it is read back after the write, as well.

Would you mind checking if the patch I sent (replumb_did_not_work.diff) is sound as far as the moment the replumb occurs? Because if that is the case, this would suggest a TX side problem, as this did not seem to fix the issue.

Cheers

Michel
-------------- next part --------------
An embedded message was scrubbed...
From: Adrian Chadd <[email protected]>
Subject: Re: [ath9k-devel] AuthSAE rekeying issues with ATH9K
Date: Wed, 13 Jul 2016 20:45:08 +0000
Size: 5488
Url: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20160714/c83f2e5a/attachment.eml