Javier, I'd successfully reach the stage where I can see 'mesh plink: ESTAB' when i enter iw IFACE station dump. This is after I run the authsae command with the -f option. I had assigned the channel of the interface with the configured channel. The problem may due to channel assignment as what you explained to me.
Afterward, I had assigned IP address to the mesh interface and tried to Ping to the peer. It was failed. The ping return 'Destination Host Unreachable'. Did you able to ping the peer on your previous test? I had the following part of the log: Received mgtk: hexdump cf ce 2d 8f 5f 77 4b 54 40 40 70 30 99 16 c0 e1 ---------- TODO: return available peer link slots Mesh plink (peer, state, llid, plid, event): 00:0e:8e:27:db:2e OPN-RCVD 61021 28566 4 ---------- mtk context: hexdump 49 c2 b0 a0 5c 44 40 b3 98 d3 49 a8 38 12 50 94 6d 02 a0 54 39 e0 3a 20 3e 4f f1 0b 50 1f 42 ad c2 c2 2e 73 fc db 69 1a 84 b1 64 e4 0a da ba d1 8f 14 12 9f 34 31 c9 fc 0d 5f a2 85 8e 22 db 16 96 6f 5d ee 00 0f ac 08 00 0e 8e 27 db 2e aa 0e 8e 27 db 2c ---------- ---------- mtk: hexdump 26 57 dc 85 8c 14 cf 67 60 c0 71 70 eb d4 26 37 ---------- estab with 00:0e:8e:27:db:2e set auth flag (seq num=1305095194) set plink state (seq num=1305095195) mesh plink with 00:0e:8e:27:db:2e established Mesh plink timer for 00:0e:8e:27:db:2e fired on state ESTAB Timeout for peer 00:0e:8e:27:db:2e in state 4 Is this a normal outcome? Thanks a lot. Ming > From: jav...@cozybit.com > Date: Tue, 10 May 2011 21:58:36 -0700 > Subject: Re: Problem on Release0.4.0 > To: devil_eddi...@hotmail.com > CC: devel@lists.open80211s.org > > Ming, > > On Tue, May 10, 2011 at 7:19 PM, MingANn Ng <devil_eddi...@hotmail.com> wrote: > > meshd: Staring mesh with mesh id = mesh > > Ignored event (20) <<<<<<<<<<<<<<<<<<<<<<< > > This corresponds to the kernel nl80211 event: NL80211_CMD_DEL_STATION. > That's probably happening when authsae brings down and up the mesh > interface during initial setup. I assume that you had stations > (visible with iw <iface> station dump) created before launching > authsae. Is that the case? This should not be a problem. I'll make > sure we supress that error message in authsae. > > > NL80211_CMD_NEW_STATION (1305078248.366798) > > Unexpected error -16 (expected -107) <<<<<<<<<<<<<<<< > > This is an EBUSY error. authsae may be trying to transmit on a > channel different than the one the interface is configured for. > With the -f option you can tell authsae what channel to use. The > default, if the option is not present, is 2412 (channel 1). > Can you try that? Also, given that you see no RX messages, you don't > seem to be receiving anything from the other peer. > > > The Log did not show any received mgtk or mtk hexdump. > > You'll only see those once the peering exchange completes successfully. > > Cheers, > > Javier > > > >> From: jav...@cozybit.com > >> Date: Tue, 10 May 2011 15:20:41 -0700 > >> Subject: Re: Problem on Release0.4.0 > >> To: devil_eddi...@hotmail.com > >> CC: devel@lists.open80211s.org > >> > >> Ming, > >> > >> On Mon, May 9, 2011 at 7:54 PM, MingANn Ng <devil_eddi...@hotmail.com> > >> wrote: > >> > I attached here wuth the dubugging message of the authsae: > >> > > >> > ---------- > >> > mgtk: hexdump > >> > 38 8c d1 84 f8 c7 62 a8 9b 52 09 09 c3 ed ed 1c > >> > ---------- > >> > > >> > ---------- > >> > Fixed Information Elements in this STA hexdump > >> > 01 08 02 03 04 05 06 09 0b 0c 32 0c 12 16 18 1b 24 2c 30 36 > >> > 42 48 60 6c > >> > ---------- > >> > > >> > meshd: Staring mesh with mesh id = mesh > >> > NL80211_CMD_NEW_PEER_CANDIDATE(1304992579.846996) > >> > new unauthed sta (seq num=1304992591) > >> > tx_frame(0x805d340, 0xbff855ac, 128) > >> > tx frame (seq num=1304992592) > >> > ---------- > >> > tx frame (seq num=%d) hexdump > >> > b0 00 00 00 00 0e 8e 27 db 2e 00 0e 8e 27 db 2c 00 0e 8e 27 > >> > db 2e 00 00 03 00 01 00 00 00 13 00 0e d0 50 a6 06 4d 3b 9c > >> > a6 ce a1 7f 72 2c 5c b8 58 f6 95 f5 a9 44 8d e8 99 af e6 d4 > >> > 9f 90 46 59 ae ca 76 64 29 4e 38 6d b0 82 44 8d 9e 3c e5 f0 > >> > 64 45 a7 3e 11 6f e4 85 e7 d9 da 59 76 e6 24 ae 49 aa 0b 27 > >> > c7 02 87 6b 47 79 04 a6 12 f6 fc 1c 61 69 02 5f 36 de cf 9f > >> > 4b 88 f7 b5 03 da 86 ca > >> > ---------- > >> > > >> > NL80211_CMD_NEW_STATION (1304992579.854079) > >> > tx_frame(0x805d340, 0xbff85b5c, 128) > >> > tx frame (seq num=0) > >> > ---------- > >> > tx frame (seq num=%d) hexdump > >> > b0 00 00 00 00 0e 8e 27 db 2e 00 0e 8e 27 db 2c 00 0e 8e 27 > >> > db 2e 00 00 03 00 01 00 00 00 13 00 0e d0 50 a6 06 4d 3b 9c > >> > a6 ce a1 7f 72 2c 5c b8 58 f6 95 f5 a9 44 8d e8 99 af e6 d4 > >> > 9f 90 46 59 ae ca 76 64 29 4e 38 6d b0 82 44 8d 9e 3c e5 f0 > >> > 64 45 a7 3e 11 6f e4 85 e7 d9 da 59 76 e6 24 ae 49 aa 0b 27 > >> > c7 02 87 6b 47 79 04 a6 12 f6 fc 1c 61 69 02 5f 36 de cf 9f > >> > 4b 88 f7 b5 03 da 86 ca > >> > ---------- > >> > > >> > tx_frame(0x805d340, 0xbff85b5c, 128) > >> > tx frame (seq num=0) > >> > ---------- > >> > tx frame (seq num=%d) hexdump > >> > b0 00 00 00 00 0e 8e 27 db 2e 00 0e 8e 27 db 2c 00 0e 8e 27 > >> > db 2e 00 00 03 00 01 00 00 00 13 00 0e d0 50 a6 06 4d 3b 9c > >> > a6 ce a1 7f 72 2c 5c b8 58 f6 95 f5 a9 44 8d e8 99 af e6 d4 > >> > 9f 90 46 59 ae ca 76 64 29 4e 38 6d b0 82 44 8d 9e 3c e5 f0 > >> > 64 45 a7 3e 11 6f e4 85 e7 d9 da 59 76 e6 24 ae 49 aa 0b 27 > >> > c7 02 87 6b 47 79 04 a6 12 f6 fc 1c 61 69 02 5f 36 de cf 9f > >> > 4b 88 f7 b5 03 da 86 ca > >> > ---------- > >> > > >> > tx_frame(0x805d340, 0xbff85b5c, 128) > >> > tx frame (seq num=0) > >> > ---------- > >> > tx frame (seq num=%d) hexdump > >> > b0 00 00 00 00 0e 8e 27 db 2e 00 0e 8e 27 db 2c 00 0e 8e 27 > >> > db 2e 00 00 03 00 01 00 00 00 13 00 0e d0 50 a6 06 4d 3b 9c > >> > a6 ce a1 7f 72 2c 5c b8 58 f6 95 f5 a9 44 8d e8 99 af e6 d4 > >> > 9f 90 46 59 ae ca 76 64 29 4e 38 6d b0 82 44 8d 9e 3c e5 f0 > >> > 64 45 a7 3e 11 6f e4 85 e7 d9 da 59 76 e6 24 ae 49 aa 0b 27 > >> > c7 02 87 6b 47 79 04 a6 12 f6 fc 1c 61 69 02 5f 36 de cf 9f > >> > 4b 88 f7 b5 03 da 86 ca > >> > ---------- > >> > > >> > tx_frame(0x805d340, 0xbff85b5c, 128) > >> > tx frame (seq num=0) > >> > ---------- > >> > tx frame (seq num=%d) hexdump > >> > b0 00 00 00 00 0e 8e 27 db 2e 00 0e 8e 27 db 2c 00 0e 8e 27 > >> > db 2e 00 00 03 00 01 00 00 00 13 00 0e d0 50 a6 06 4d 3b 9c > >> > a6 ce a1 7f 72 2c 5c b8 58 f6 95 f5 a9 44 8d e8 99 af e6 d4 > >> > 9f 90 46 59 ae ca 76 64 29 4e 38 6d b0 82 44 8d 9e 3c e5 f0 > >> > 64 45 a7 3e 11 6f e4 85 e7 d9 da 59 76 e6 24 ae 49 aa 0b 27 > >> > c7 02 87 6b 47 79 04 a6 12 f6 fc 1c 61 69 02 5f 36 de cf 9f > >> > 4b 88 f7 b5 03 da 86 ca > >> > ---------- > >> > > >> > tx_frame(0x805d340, 0xbff85b5c, 128) > >> > tx frame (seq num=0) > >> > ---------- > >> > tx frame (seq num=%d) hexdump > >> > b0 00 00 00 00 0e 8e 27 db 2e 00 0e 8e 27 db 2c 00 0e 8e 27 > >> > db 2e 00 00 03 00 01 00 00 00 13 00 0e d0 50 a6 06 4d 3b 9c > >> > a6 ce a1 7f 72 2c 5c b8 58 f6 95 f5 a9 44 8d e8 99 af e6 d4 > >> > 9f 90 46 59 ae ca 76 64 29 4e 38 6d b0 82 44 8d 9e 3c e5 f0 > >> > 64 45 a7 3e 11 6f e4 85 e7 d9 da 59 76 e6 24 ae 49 aa 0b 27 > >> > c7 02 87 6b 47 79 04 a6 12 f6 fc 1c 61 69 02 5f 36 de cf 9f > >> > 4b 88 f7 b5 03 da 86 ca > >> > ---------- > >> > > >> > tx_frame(0x805d340, 0xbff85b5c, 128) > >> > tx frame (seq num=0) > >> > ---------- > >> > tx frame (seq num=%d) hexdump > >> > b0 00 00 00 00 0e 8e 27 db 2e 00 0e 8e 27 db 2c 00 0e 8e 27 > >> > db 2e 00 00 03 00 01 00 00 00 13 00 0e d0 50 a6 06 4d 3b 9c > >> > a6 ce a1 7f 72 2c 5c b8 58 f6 95 f5 a9 44 8d e8 99 af e6 d4 > >> > 9f 90 46 59 ae ca 76 64 29 4e 38 6d b0 82 44 8d 9e 3c e5 f0 > >> > 64 45 a7 3e 11 6f e4 85 e7 d9 da 59 76 e6 24 ae 49 aa 0b 27 > >> > c7 02 87 6b 47 79 04 a6 12 f6 fc 1c 61 69 02 5f 36 de cf 9f > >> > 4b 88 f7 b5 03 da 86 ca > >> > ---------- > >> > > >> > fin: 16, key len:0 me:00:0e:8e:27:db:2e peer:00:0e:8e:27:db:2c > >> > >> I don't see anything wrong in the logs. That said, I can only see one > >> side of the protocol. You might want to compare the logs between two > >> peers and check the following: > >> > >> 1. mesh gtk is correctly communicated to peers: > >> > >> for instance, peer one picks this mgtk: > >> > >> mgtk: hexdump > >> c8 2e 98 6d 2d af 50 06 03 0a bd 74 f1 53 8f 87 > >> > >> other peers should show: > >> > >> Received mgtk: hexdump > >> c8 2e 98 6d 2d af 50 06 03 0a bd 74 f1 53 8f 87 > >> > >> 2. Pairwise mtk matches for each pair of peers: > >> > >> mtk: hexdump > >> 56 ea e3 d6 c0 a8 56 ce 7c eb 85 57 ee b8 73 a9 > >> mtk: hexdump > >> 56 ea e3 d6 c0 a8 56 ce 7c eb 85 57 ee b8 73 a9 > >> > >> 3. Peer links make it to the ESTAB state: > >> > >> Mesh plink (peer, state, llid, plid, event): 02:04:05:00:04:00 ESTAB > >> 54937 63155 1 > >> > >> 4. The state is reported correctly by iw > >> > >> iw dev mesh0 station dump > >> Station 02:04:05:00:00:00 (on mesh0) > >> inactive time: 200 ms > >> rx bytes: 17621 > >> rx packets: 331 > >> tx bytes: 2494 > >> tx packets: 19 > >> tx retries: 0 > >> tx failed: 0 > >> signal: -30 dBm > >> signal avg: -30 dBm > >> tx bitrate: 1.0 MBit/s > >> mesh llid: 0 > >> mesh plid: 0 > >> mesh plink: ESTAB > >> > >> Also, what hardware are you using? You should check that the > >> driver/wireless card support Management Frame Protection: > >> > >> # mount -t debugfs null /sys/kernel/debug > >> # cat /sys/kernel/debug/ieee80211/phy14/hwflags > >> 0x1a240 > >> SIGNAL_DBM > >> AMPDU_AGGREGATION > >> MFP_CAPABLE <<<<<<<<<<<<<<<<<<<<<<< > >> SUPPORTS_STATIC_SMPS > >> SUPPORTS_DYNAMIC_SMPS > >> > >> Hope these pointers help. > >> > >> Cheers, > >> > >> Javier > >> > >> > >> > Thanks, > >> > Ming Ann > >> > > >> >> From: jav...@cozybit.com > >> >> Date: Mon, 9 May 2011 10:38:34 -0700 > >> >> Subject: Re: FW: Problem on Release0.4.0 > >> >> To: devil_eddi...@hotmail.com > >> >> > >> >> Hi Ming > >> >> > >> >> Can you retry? Your membership request to the list was approved so > >> >> you should have no problems sending messages there. Regarding the > >> >> problems you see, can you post the authsae debug logs? > >> >> > >> >> j > >> >> > >> >> On Sun, May 8, 2011 at 5:43 PM, MingANn Ng <devil_eddi...@hotmail.com> > >> >> wrote: > >> >> > > >> >> > I'm having problem sending mail to the devel list, sorry that I have > >> >> > to > >> >> > send > >> >> > it directly to you. > >> >> > ________________________________ > >> >> > From: devil_eddi...@hotmail.com > >> >> > To: devel@lists.open80211s.org > >> >> > Subject: Problem on Release0.4.0 > >> >> > Date: Fri, 6 May 2011 15:39:02 +0800 > >> >> > > >> >> > Hi, > >> >> > > >> >> > I had downloaded the latest kernel and authsae from release 0.4.0. > >> >> > I'm currently using ath9k driver for my wireless card on 2 PC. > >> >> > I'd configure the mesh as in the HOWTO page, but the peer failed to > >> >> > establish and iw station dump shows the peer is always in Listen > >> >> > stage. > >> >> > > >> >> > There is situation where only one of the peer is trasmitting beacon > >> >> > (observation from Wireshark), the peer which is receiving the beacon > >> >> > is > >> >> > in > >> >> > Listen stage where as on the other peer, iw station dump did not show > >> >> > anything. > >> >> > > >> >> > When the two peer are trasmiting beacon, after a few retries, both > >> >> > peer > >> >> > is > >> >> > on Listen stage and failed to establish. > >> >> > > >> >> > In configuring the mesh network I'd enter the following command on 2 > >> >> > separate PC: > >> >> > > >> >> >>sudo iw wlan0 interface add mesh type mp > >> >> >>sudo iw mesh set channel 11 > >> >> >>sudo ifconfig mesh up > >> >> >>sudo linux/meshd-nl80211 -I config -s mesh -i mesh > >> >> > > >> >> > the sae.conf file is as below: > >> >> > > >> >> > > >> >> > #debug=128 > >> >> > #debug=96 > >> >> > #debug=32 > >> >> > #debug=256 > >> >> > debug=480 > >> >> > password=thisisreallysecret > >> >> > # > >> >> > group=19 26 21 25 20 > >> >> > # > >> >> > blacklist=5 > >> >> > # > >> >> > thresh=5 > >> >> > # > >> >> > lifetime=3600 > >> >> > > >> >> > The meshd.conf is as follow: > >> >> > > >> >> > # > >> >> > ssid=byteme > >> >> > # > >> >> > #interface=ath0 > >> >> > #interface=lo0 > >> >> > # > >> >> > passive=0 > >> >> > # > >> >> > debug=1 > >> >> > # > >> >> > # STA=0, ADHOC=1, HOSTAP=2, MONITOR=3 > >> >> > mediaopt=1 > >> >> > # > >> >> > band=11g > >> >> > # > >> >> > channel=11 > >> >> > > >> >> > Is there anything wrong in my configuration? > >> >> > I'd tried on OpenMesh configuration on this same Kernel, it's working > >> >> > fine. > >> >> > Please help on this.Thanks. > >> >> > > >> >> > Regards, > >> >> > Ming Ann > >> >> > >> >> > >> >> > >> >> -- > >> >> Javier Cardona > >> >> cozybit Inc. > >> >> http://www.cozybit.com > >> > > >> > >> > >> > >> -- > >> Javier Cardona > >> cozybit Inc. > >> http://www.cozybit.com > > > > > > -- > Javier Cardona > cozybit Inc. > http://www.cozybit.com
_______________________________________________ Devel mailing list Devel@lists.open80211s.org http://open80211s.com/mailman/listinfo/devel
