Hi Yeoh, On Tue, May 3, 2011 at 1:07 AM, Yeoh Chun Yeow <yeohchuny...@gmail.com> wrote: > Hi, Javier > I have confirmed the combination of ath9k and 802.11s in > compat-wireless-2011-04-06 is working. But not compat-wireless-2010-4-19. > Can you pinpoint where should we look into in the ath9k source code in case > somethings wrong with 802.11s.
If I knew exactly what could be wrong with the ath9k driver I would fix it right away :) I think the first step is to confirm the assumption that beaconing in mesh mode is broken. Just try to start an open mesh and observe with a sniffer if you see beacons coming from that interface: iw phy $phy interface add mesh0 type mesh ifconfig mesh0 up iw dev mesh0 mesh join testfoo <beaconing should have started by now> If you don't, you should look into the part of the driver that enables beaconing: ath_beacon_config() and so on. Did you ask in ath9k-devel? If basic mesh functionality is broken, they should be able to help. Specially if there is a very easy test like the one described above. This is unrelated to the new security features. And as you've seen, it work on ath5k (hint: telling the ath9k guys that something works on ath5k is a very good way to get their attention };) Javier > On Tue, May 3, 2011 at 2:10 PM, Yeoh Chun Yeow <yeohchuny...@gmail.com> > wrote: >> >> It seems that the current trunk version of OpenWRT using >> compat-wireless-2010-04-19 works well ath5k and not ath9k. I switch to >> 802.11b/g/a network card and ath5k with same setup and it works. >> > > -- Javier Cardona cozybit Inc. http://www.cozybit.com _______________________________________________ Devel mailing list Devel@lists.open80211s.org http://open80211s.com/mailman/listinfo/devel
