Hi Yeoh, On Sun, May 1, 2011 at 8:28 AM, Yeoh Chun Yeow <yeohchuny...@gmail.com> wrote: > Even I did "iw dev wlan0 scan", the problem still there. The beaconing > problem that you mentioned is related to this?
Earlier versions of the ath9k driver also had a beaconing problem in mesh mode that could be worked around by scanning. This does not seem to be the case with the more recent breakage. Maybe you can try to get help from ath9k-devel ? https://lists.ath9k.org/mailman/listinfo/ath9k-devel Javier > Regards, > Chun Yeow > > On Sun, May 1, 2011 at 12:26 AM, Javier Cardona <jav...@cozybit.com> wrote: >> >> Yeoh, >> >> On Fri, Apr 29, 2011 at 11:02 PM, Yeoh Chun Yeow <yeohchuny...@gmail.com> >> wrote: >> > Hi, all >> > Anyone has test the 802.11s using the latest trunk version of OpenWRT >> > with >> > compat-wireless-2011-04-19? >> > I have tested previously with compat-wireless-2011-04-06 and it works. >> > But >> > after the svn update, the nodes fail to establish the peer link. >> > Anyone can provide some tips and hints on how to debug? >> >> Someone recently reported: >> >> > the mesh with the ath5k driver seems fine. The problems are with the >> > ath9k driver. >> > The mesh for ath9k (we use an AR9280) has been broken since build >> > 3-31-2011. >> > Hope this helps. >> >> We also observed that the ath9k driver from wireless-testing head >> won't do mesh. This is probably related to beaconing (that's the most >> frequent cause for driver breakage). A workaround would be to revert >> to an older version of the driver. >> >> Cheers, >> >> j >> >> >> -- >> Javier Cardona >> cozybit Inc. >> http://www.cozybit.com > > -- Javier Cardona cozybit Inc. http://www.cozybit.com _______________________________________________ Devel mailing list Devel@lists.open80211s.org http://open80211s.com/mailman/listinfo/devel