Hi Fred, I don't have a solution, but I can provide some pointers. See inline:
On Sun, Sep 2, 2012 at 4:56 PM, fred veldini <[email protected]> wrote: > Cell 03 - Address: 00:14:6D:65:8B:FE > Channel:157 > Frequency:5.785 GHz (Channel 157) > Quality=43/70 Signal level=-67 dBm > Encryption key:on > ESSID:"" > Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s > 36 Mb/s; 48 Mb/s; 54 Mb/s > ESSID:"my-mesh5gs" > Extra:Mesh Network Path Selection Protocol ID: 0x01 > Extra:Path Selection Metric ID: 0x01 > Extra:Congestion Control Mode ID: 0x00 > Extra:Synchronization ID: 0x01 > Extra:Authentication ID: 0x00 > Extra:Formation Info: 0x1E > Extra:Capabilities: 0x09 > Mode:Unknown/bug > Extra:tsf=000000000ba86004 > Extra: Last beacon: 2059ms ago > IE: Unknown: 0000 > IE: Unknown: 01088C129824B048606C > IE: IEEE 802.11i/WPA2 Version 1 > Group Cipher : CCMP > Pairwise Ciphers (1) : CCMP > Authentication Suites (1) : unknown (8) > IE: Unknown: 720A6D792D6D657368356773 > IE: Unknown: 710701010001001E09 These last two unknown IEs are the mesh ID (0x72) and the mesh config (0x71) information elements. Your version of iw does not seem to recognize those. > Cell 03 - Address: 00:14:6D:65:8B:FE > Channel:157 > Frequency:5.785 GHz (Channel 157) > Quality=43/70 Signal level=-67 dBm > Encryption key:off > ESSID:"" > Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s > 36 Mb/s; 48 Mb/s; 54 Mb/s > ESSID:"my-mesh5gs" > Extra:Mesh Network Path Selection Protocol ID: 0x01 > Extra:Path Selection Metric ID: 0x01 > Extra:Congestion Control Mode ID: 0x00 > Extra:Synchronization ID: 0x01 > Extra:Authentication ID: 0x00 > Extra:Formation Info: 0x00 > Extra:Capabilities: 0x09 > Mode:Unknown/bug > Extra:tsf=000000000222e004 > Extra: Last beacon: 2048ms ago > IE: Unknown: 0000 > IE: Unknown: 01088C129824B048606C > IE: Unknown: 720A6D792D6D657368356773 > IE: Unknown: 710701010001000009 These are stranger: 0x00 is SSID and 0x01 is supported rates. I don't know why iw would report them as unknown if they seem to be correctly parsed above. But probably no big deal. > Notice the encryption goes away. But authsae is still running. > > If I restart authsae I will get > > Mesh plink: incorrect plink ie length 3 6 This is reported by authsae: a PLINK_CLOSE IE is received of size 6 bytes. Should be 22 or 24 bytes (see ampe.c:942). May not be important. > then the nlerror, cmd 11, seq 1346629691: Invalid argument Cmd 11 is NL80211_CMD_NEW_KEY, and the kernel seems to be rejecting it. The invalid argument error is -EINVAL, which could be raised by cfg80211_validate_key_settings (see Yeoh's patch). authsae will install 3 keys for each newly established peer. See estab_peer_link, in meshd-nl80211.c Maybe you can try to commenting out one by one and determine which one fails. Hopefully this helps you narrow down the problem. Cheers, Javier >> _______________________________________________ >> Devel mailing list >> [email protected] >> http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel > > > > > _______________________________________________ > Devel mailing list > [email protected] > http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel > -- Javier Cardona cozybit Inc. http://www.cozybit.com _______________________________________________ Devel mailing list [email protected] http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
