Hi Javier,
> Hi Ming,
>
> On Tue, May 10, 2011 at 11:47 PM, MingAnn Ng <devil_eddi...@hotmail.com>
> wrote:
> > 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?
>
> Nice! Looks like you completed SAE and AMPE successfully. In order
> to use encryption your hardware needs to support multiple GTKs (each
> peer uses a different MGTK). This is only available on newer
> hardware.
Do you mean that to successfully ping the other peer, we need to use encryption?
>From the log of both peers, I can See that the received MGTK was different
>from each other. What I mean is:
Tx MGTK of peer 1= Rx MGTK of peer 2;
Rx MGTK of peer 1= Tx MGTK of peer 2;
but Tx MGTK and Rx MGTK of peer 1 is different.
Is this What you mean by support multiple GTKs?
> What card do you use? You can try to force encryption to take place
> in software by loading ath9k with 'nohwcrypt=1'
> We could not get that to work on our older Atheros cards (AR5418) but
> maybe you get lucky.
I'm currently using AR9160 802.11 abgn card. From modinfo ath9k; nohwcrypt:
Disable harware encryption (int).
This means 'nohwcrypt=1' right?
I tested it again by ping to the other peer, but it still failed.
> We are enlisting driver developers to help us support the different
> wireless cards. If you can provide more info about your hardware will
> be useful.
> Cheers,
>
> Javier
Thanks,
Ming
_______________________________________________
Devel mailing list
Devel@lists.open80211s.org
http://open80211s.com/mailman/listinfo/devel
