First attempt at o11s on ath5k

[Andrey Yurovsky]

Hi Steve.  There might be a regression in mac80211 right now that is
affecting you.  On wireshark, do you see beacons from any of your mesh
interfaces that are up?  If not, can you please "iwlist scan" on the
interfaces in question and then see if they start to beacon?  A mesh
interface should send periodic beacons, much like an AP would.
Thanks,

2009/3/18 Steve Glass <stevie.glass at gmail.com>:
> Hi,
>
> I'm trying to test open80211s on ath5k. I'm using wireless-testing (post the
> commit listed on the compatibility page),  can set the meshid and bring up
> the mesh interfaces but they do not associate. I've tried on several
> computers with the same kernel and get the same result. I follow the wiki
> howto up untikl the "iw dev mesh0 station dump" but there's no associations
> reported.
>
> 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. The other
> station is occasionally sending ARP requests (in response to me pinging to
> see if I can force the stations to associate) so perhaps these have upset
> things as they are data frames from an unauthenticated station?
>
> Can anyone suggest a possible remedy?
>
> Steve
>
> _______________________________________________
> Devel mailing list
> Devel at lists.open80211s.org
> http://open80211s.com/mailman/listinfo/devel
>
>



-- 
Andrey Yurovsky
cozybit Inc.