Hi, Fabrice I think that it may due to SAE part of authsae.
Node A whereby the tx power is reduced to 0 is able to receive the beacon generated from its peering node (Node B). So it generates the authentication commit message. If Node B received the commit message (sometime, it can be received by Node B even tx power of Node A is reduced to 0), Node B generates commit message followed by confirm message. Node A receives those messages and go into plink establishment. But Node B cannot receive the confirm message from Node A and thus deleting Node A in SAE exchange. Node A [plink state: LISTEN] --------- Commit -----------> Node B [plink state: ESTBA] Node A [plink state: LISTEN] <-------- Commit ----------- Node B [plink state: ESTBA] Node A [plink state: LISTEN] <-------- Confirm ----------- Node B [plink state: ESTBA] Node A [plink state: LISTEN] -------- Confirm ------XXX----> Node B [plink state: ESTBA] Node B's authsae output msg: recv'd COMMIT from 0a:0b:6b:7d:e3:b9 while in NOTHING assigning group 19 to peer, the size of the prime is 32 COMMIT received for unknown peer, committing and confirming in NOTHING, sending COMMIT (no token), len 128, group 19 in NOTHING, sending CONFIRM (sc=1), len 64 state of 0a:0b:6b:7d:e3:b9 is now (2) CONFIRMED timer 109 fired! retrans = 0, incrementing in CONFIRMED, sending CONFIRM (sc=2), len 64 timer 110 fired! retrans = 1, incrementing in CONFIRMED, sending CONFIRM (sc=3), len 64 timer 111 fired! retrans = 2, incrementing in CONFIRMED, sending CONFIRM (sc=4), len 64 timer 112 fired! retrans = 3, incrementing in CONFIRMED, sending CONFIRM (sc=5), len 64 timer 113 fired! retrans = 4, incrementing in CONFIRMED, sending CONFIRM (sc=6), len 64 timer 114 fired! retrans = 5, incrementing in CONFIRMED, sending CONFIRM (sc=7), len 64 timer 115 fired! retrans = 6, incrementing peer not listening! deleting peer at 0a:0b:6b:7d:e3:b9 in state CONFIRMED Another case is as follow: Node A [plink state: LISTEN] --------- Commit ---XXXX---> Node B [plink state: ESTBA] Node A's authsae output msg group 19 is configured, prime is 32 bytes group 26 is configured, prime is 28 bytes group 21 is configured, prime is 66 bytes group 25 is configured, prime is 24 bytes group 20 is configured, prime is 48 bytes nlerror, cmd 69, seq 1318004731: Transport endpoint is not connected received a beacon from 0a:0b:6b:b2:03:5d Initiate event assigning group 19 to peer, the size of the prime is 32 in NOTHING, sending COMMIT (no token), len 128, group 19 state of 0a:0b:6b:b2:03:5d is now (1) COMMITTED timer 1 fired! retrans = 0, incrementing in COMMITTED, sending COMMIT (no token), len 128, group 19 timer 2 fired! retrans = 1, incrementing in COMMITTED, sending COMMIT (no token), len 128, group 19 timer 3 fired! retrans = 2, incrementing in COMMITTED, sending COMMIT (no token), len 128, group 19 timer 4 fired! retrans = 3, incrementing in COMMITTED, sending COMMIT (no token), len 128, group 19 timer 5 fired! retrans = 4, incrementing in COMMITTED, sending COMMIT (no token), len 128, group 19 timer 6 fired! retrans = 5, incrementing in COMMITTED, sending COMMIT (no token), len 128, group 19 timer 7 fired! retrans = 6, incrementing peer not listening! 0a:0b:6b:b2:03:5d never responded, adding to blacklist deleting peer at 0a:0b:6b:b2:03:5d in state COMMITTED removing 0a:0b:6b:b2:03:5d from blacklist Regards, Chun-Yeow
_______________________________________________ Devel mailing list [email protected] http://open80211s.com/mailman/listinfo/devel
