First attempt at o11s on ath5k
Javier Cardona
javier at cozybit.com
Wed Mar 18 14:46:10 EDT 2009
Hi Steve,
2009/3/18 Steve Glass <stevie.glass at gmail.com>:
> (...)
> 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.
More information about the Devel
mailing list