Hi, Javier and Fabrice After debugging with Wireshark, let me clarify further:
Since Node 1 is pinging PC behind Node 2, after successfully ping and node 3 is brought up, if the ping is continue, PREQ broadcasting by Node 1 cannot be received or decrypted by Node 2. Thus, Node 1 assumes Node 2 is dead or out of range since no PREP from Node 2. Ping is route through Node 3. It seems that the problem is the broadcast PREQ frame generated by either Node 2 or Node 1 cannot be decoded by Node 1 or Node 2 respectively whenever Node 3 is up or reboot. Only node 3 can decode the broadcast PREQ frame from either Node 1 or Node 2. But after a period of time, it backs to normal. Regards, Chun-Yeow On Thu, Dec 8, 2011 at 1:40 PM, Yeoh Chun-Yeow <[email protected]>wrote: > Hi, Javier and Fabrice > > This is what I have observed for secured Mesh. > > In the initial stage, I have setup the following mesh topology. > > Node 1 ------> Node 2 [Root] -----> PC > > Ping from Node 1 to PC will go through Node 2 before reaching the PC. > > During the Ping process, Node 3 is brought up and the network topology is > immediately changed to following: > > Node 1 -----> Node 3 ------> Node 2 [Root] -----> PC > > Ping from Node 1 will go through Node 3 and then Node 2 before reaching > the PC. > > Look into the authsae source, there are 5 keys installed: > 1. key to encrypt/decrypt unicast data AND mgmt traffic to/from this peer > 2. key to protect integrity of multicast mgmt frames tx > 3. key to encrypt multicast data traffic > 4. key to decrypt multicast data traffic from this peer > 5. to check integrity of multicast mgmt frames from this peer > > When Node 3 is brought up or reboot, key 2 and key 3 are modified or > changed. This has caused the temporary breakdown between Node 1 and Node 2 > on broadcast/multicast frame. PREQ generated by Node 2 is not able decrypt > by Node 1. Node 1 assumes that Node 2 is dead and use the route towards > Node 3 to reach Node 2. > > Secured Mesh: > Dec 8 13:16:37 kern.debug kernel: ieee80211 phy0: Allocated STA > 0a:0b:6b:7d:e3:b9 > Dec 8 13:16:37 kern.debug kernel: ieee80211 phy0: Inserted STA > 0a:0b:6b:7d:e3:b9 > Dec 8 13:16:45 kern.debug kernel: Mesh HWMP (mesh0): received PREQ from > 0a:0b:6b:7d:e3:b9 > Dec 8 13:16:45 kern.debug kernel: Mesh HWMP (mesh0): forwarding the PREQ > from 0a:0b:6b:7d:e3:b9 > Dec 8 13:16:45 kern.debug kernel: Mesh HWMP (mesh0): sending PREQ to > 0a:0b:6b:b6:5c:3c > Dec 8 13:16:51 kern.debug kernel: Mesh HWMP (mesh0): received PREQ from > 0a:0b:6b:7d:e3:b9 > Dec 8 13:16:51 kern.debug kernel: Mesh HWMP (mesh0): forwarding the PREQ > from 0a:0b:6b:7d:e3:b9 > Dec 8 13:16:51 kern.debug kernel: Mesh HWMP (mesh0): sending PREQ to > 0a:0b:6b:b6:5c:3c > > Non-secured Mesh: > Dec 8 13:12:46 kern.debug kernel: Mesh plink: starting establishment > with 0a:0b:6b:7d:e3:b9 > Dec 8 13:12:46 kern.debug kernel: Mesh plink (peer, state, llid, plid, > event): 0a:0b:6b:7d:e3:b9 OPN-SNT 30058 0 6 > Dec 8 13:12:46 kern.debug kernel: Mesh plink (peer, state, llid, plid, > event): 0a:0b:6b:7d:e3:b9 OPN-SNT 30058 0 1 > Dec 8 13:12:46 kern.debug kernel: Mesh plink timer for 0a:0b:6b:7d:e3:b9 > fired on state 2 > Dec 8 13:12:46 kern.debug kernel: Mesh plink for 0a:0b:6b:7d:e3:b9 > (retry, timeout): 0 100 > Dec 8 13:12:46 kern.debug kernel: Mesh plink (peer, state, llid, plid, > event): 0a:0b:6b:7d:e3:b9 OPN-RCVD 30058 45600 4 > Dec 8 13:12:46 kern.debug kernel: Mesh plink with 0a:0b:6b:7d:e3:b9 > ESTABLISHED > *Dec 8 13:12:48 kern.debug kernel: Mesh HWMP (mesh0): received PREQ > from 0a:0b:6b:b6:5c:3c [Missing for Secured Mesh]* > *Dec 8 13:12:48 kern.debug kernel: Mesh HWMP (mesh0): forwarding the > PREQ from 0a:0b:6b:b6:5c:3c **[Missing for Secured Mesh]* > * Dec 8 13:12:48 kern.debug kernel: Mesh HWMP (mesh0): sending PREQ to > 0a:0b:6b:7d:e3:b9 **[Missing for Secured Mesh]* > Dec 8 13:12:52 kern.debug kernel: Mesh HWMP (mesh0): received PREQ from > 0a:0b:6b:7d:e3:b9 > Dec 8 13:12:52 kern.debug kernel: Mesh HWMP (mesh0): forwarding the PREQ > from 0a:0b:6b:7d:e3:b9 > Dec 8 13:12:52 kern.debug kernel: Mesh HWMP (mesh0): sending PREQ to > 0a:0b:6b:b6:5c:3c > Dec 8 13:12:58 kern.debug kernel: Mesh HWMP (mesh0): received PREQ from > 0a:0b:6b:7d:e3:b9 > Dec 8 13:12:58 kern.debug kernel: Mesh HWMP (mesh0): forwarding the PREQ > from 0a:0b:6b:7d:e3:b9 > Dec 8 13:12:58 kern.debug kernel: Mesh HWMP (mesh0): sending PREQ to > 0a:0b:6b:b6:5c:3c > Dec 8 13:13:08 kern.debug kernel: Mesh HWMP (mesh0): received PREQ from > 0a:0b:6b:7d:e3:b9 > Dec 8 13:13:08 kern.debug kernel: Mesh HWMP (mesh0): forwarding the PREQ > from 0a:0b:6b:7d:e3:b9 > Dec 8 13:13:08 kern.debug kernel: Mesh HWMP (mesh0): sending PREQ to > 0a:0b:6b:b6:5c:3c > Dec 8 13:13:12 kern.debug kernel: mesh0: running mesh housekeeping > Dec 8 13:13:18 kern.debug kernel: Mesh HWMP (mesh0): received PREQ from > 0a:0b:6b:7d:e3:b9 > Dec 8 13:13:18 kern.debug kernel: Mesh HWMP (mesh0): forwarding the PREQ > from 0a:0b:6b:7d:e3:b9 > Dec 8 13:13:18 kern.debug kernel: Mesh HWMP (mesh0): sending PREQ to > 0a:0b:6b:b6:5c:3c > Dec 8 13:13:28 kern.debug kernel: Mesh HWMP (mesh0): received PREQ from > 0a:0b:6b:7d:e3:b9 > Dec 8 13:13:28 kern.debug kernel: Mesh HWMP (mesh0): forwarding the PREQ > from 0a:0b:6b:7d:e3:b9 > Dec 8 13:13:28 kern.debug kernel: Mesh HWMP (mesh0): sending PREQ to > 0a:0b:6b:b6:5c:3c > Dec 8 13:13:33 kern.debug kernel: Mesh HWMP (mesh0): received PREQ from > 0a:0b:6b:7d:e3:b9 > Dec 8 13:13:33 kern.debug kernel: Mesh HWMP (mesh0): forwarding the PREQ > from 0a:0b:6b:7d:e3:b9 > Dec 8 13:13:33 kern.debug kernel: Mesh HWMP (mesh0): sending PREQ to > 0a:0b:6b:b6:5c:3c > Dec 8 13:13:38 kern.debug kernel: Mesh HWMP (mesh0): received PREQ from > 0a:0b:6b:b6:5c:3c > Dec 8 13:13:38 kern.debug kernel: Mesh HWMP (mesh0): PREQ is for us > Dec 8 13:13:38 kern.debug kernel: Mesh HWMP (mesh0): replying to the PREQ > Dec 8 13:13:38 kern.debug kernel: Mesh HWMP (mesh0): sending PREP to > 0a:0b:6b:b6:5c:3c > > Regards, > Chun-Yeow > >
_______________________________________________ Devel mailing list [email protected] http://open80211s.com/mailman/listinfo/devel
