Hi Chun-Yeow, On Wed, Nov 9, 2011 at 3:20 AM, Yeoh Chun-Yeow <[email protected]> wrote: > Hi, Thomas > > The previous email is due to my personal mistake of having the same MAC > address. Anyway, the authsae seems not able to make the mesh node to ping > each others. > > Authsae seems complete but I cannot PING the mesh node even with > nohwcrypt=1. > > Regards, > Chun-Yeow > > # ---------- > mgtk: hexdump > 3b 17 61 f3 e4 ee a2 f8 50 a4 10 12 d1 1c d4 d6 > ---------- > > ---------- > 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 > ---------- > > setting freq 5180, mode 1 (seq num=1315497814) > meshd: Starting mesh with mesh id = open80211s > Unexpected error -16 (expected -134) > nlerror, cmd 69, seq 1315497815: Transport endpoint is not connected > NL80211_CMD_NEW_PEER_CANDIDATE(1315497805.412957) > tx_frame(0x42b2f0, 0x7ff7e628, 128) > tx frame (seq num=1315497818) > ---------- > tx frame hexdump > b0 00 00 00 0a 0b 6b b6 5c 3c 0a 0b 6b 7d e3 b9 0a 0b 6b b6 > 5c 3c 00 00 03 00 01 00 00 00 13 00 17 ae 2a fb 87 33 36 20 > c1 01 8c 29 76 6e 46 8d 7b bd 6b de 41 72 ab 9a 22 0e 37 92 > 1d ca ce 96 2f 73 84 96 f4 6a 8b 9e ee 06 2d 7b 5f b4 f2 3a > d9 42 6b 07 0b 76 38 db 0a bf 8b 17 69 80 f9 e9 73 2d ea 95 > ac 0a b1 8d f1 e1 ac fb 71 84 70 ed 0a 48 66 58 68 87 ab a9 > 05 fa 39 f9 22 4d 4a ec > ---------- > > new unauthed sta (seq num=1315497819) > nlerror, cmd 59, seq 1315497818: Device or resource busy
Here NL80211_CMD_FRAME is failing (note the matching sequence number). Is the channel specified in authsae.conf the same as set with iw before bringing up authsae? Switching channels is currently not implemented in authsae. If this does not solve your issue, please post more details about your configuration. Thanks, Thomas _______________________________________________ Devel mailing list [email protected] http://open80211s.com/mailman/listinfo/devel
