Hi Holger, On Thu, Mar 19, 2009 at 9:23 AM, Holger Winkelmann <[email protected]> wrote: > I'm reading tue o11s List for a whole now. Re your point 'mesh > authentication' I'm wondering is there any authentication defined in > 11s to decide if a mesh node is allowed to join a mesh or not ?
11s defines a pre-shared secret based authentication, but has not been implemented in o11s. The way things are today an o11s mesh node will try to establish a peer link with any other node with the same Mesh ID on the same channel. There is an open reference implementation of the authentication algorithm that's in the current 11s draft. It is available here: http://authsae.cvs.sourceforge.net/viewvc/authsae/authsae If anyone out there is interested in integrating it with o11s we'd be happy to provide guidance, and we may even be able to partially sponsor the development. Cheers, Javier > -- > > Holger Winkelmann > Travelping GmbH > +49-171-5594745 > > > On 18.03.2009, at 19:46, Javier Cardona <[email protected]> wrote: > >> Hi Steve, >> >> 2009/3/18 Steve Glass <[email protected]>: >>> (...) >>> Running wireshark it appears that Mesh Peer Link actions go out >>> with Mesh >>> Link Open repeated a few times and then several Mesh Peer Link >>> actions go >>> out with Mesh Link Close. The reason code for the close is "Reason >>> code: >>> Class 2 frame received from nonauthenticated station (0x0006)". >>> Thus no >>> links are created and none reported for "iw dev mesh0 station dump" >>> and I >>> cannot ping between stations. >>> >>> I see the Mesh Peer Link frames all originate at the same station. >>> (...) >>> Can anyone suggest a possible remedy? >> >> Not really a remedy, but maybe a starting point. If you see Mesh Link >> Open frames it means that the sender has successfully discovered a >> mesh neighbor, i.e that the sender has seen a beacon from the receiver >> and is trying to establish a peer link. >> The reason code that you see is interpreted by wireshark as "Class 2 >> frame received from nonauthenticated station" but that's because the >> mesh is re-using reason codes until ANA assigns new ones. If you look >> in mesh_plink.c you'll see that 0x6 is for MESH_MAX_RETRIES. This is >> triggered when the sender does not receive a response to several Mesh >> Link Open requests. >> >> So the sender seems to be behaving correctly, and all we know about >> the receiver is that it is sending beacons. >> >> That's not much, but hopefully it saves you from trying to debug mesh >> authentication (...there isn't one!). >> >> Cheers, >> >> Javier >> >> -- >> Javier Cardona >> cozybit Inc. >> _______________________________________________ >> Devel mailing list >> [email protected] >> http://open80211s.com/mailman/listinfo/devel > _______________________________________________ > Devel mailing list > [email protected] > http://open80211s.com/mailman/listinfo/devel > -- Javier Cardona cozybit Inc. _______________________________________________ Devel mailing list [email protected] http://open80211s.com/mailman/listinfo/devel
