[PATCH 11/12] mesh: Send peering open frame again if beacon from listen state peer is received

Bob Copeland me at bobcopeland.com
Fri Nov 7 07:21:55 EST 2014


On Thu, Nov 06, 2014 at 10:29:51AM +0000, Nishikawa, Kenzoh wrote:
> > 2014-11-05 22:09 GMT+09:00 Bob Copeland <me at bobcopeland.com>:
> >> I fixed a similar problem with authsae here:
> >> https://github.com/cozybit/authsae/commit/295164a83717ce59ca280468fc2f7edcea6b3cbf
> >
> > Great!
> >
> > I could fix this problem by adding one line based on your idea.
> > Thank you !
> 
> I found the problem for this solution.
> 
> NodeA registers NodeB by receiving the beacon and sends open frames.
> But NodeB ignore the open frames because NodeB has not registered NodeA.
> So NodeA goes to Holding state and forget NodeB by the solution.
> Then NodeB starts sending open frames after receiving the NodeA beacon
> and fails since NodeA doesn't remember NodeB anymore.
> And repeats this forever.
> 
> Nearly same problem happens when a peer is deleted since mesh_mpm_fsm_restart()
> is called with the reason code "WLAN_REASON_MESH_CLOSE_RCVD".

Ah, too bad.  I guess authsae must suffer from this same problem then
if SAE succeeds but plink establishment fails, as it doesn't delete
peers inside the ampe.c state machine.  Hmm.

-- 
Bob Copeland %% http://bobcopeland.com/


More information about the HostAP mailing list