On Wed, Jun 3, 2009 at 11:21 AM, Nick Kossifidis <mickflemm@xxxxxxxxx> wrote: > 2009/6/2 Andrey Yurovsky <andrey@xxxxxxxxxxx>: >> With wireless-testing from a couple of days ago, an X86 system, and this patch: >> http://osdir.com/ml/linux-wireless/2009-05/msg01241.html >> ath9k can bring up a mesh point interface and doesn't crash for me, >> but there are no mesh beacons, so mesh isn't working. On ath5k, there >> are also no beacons and mesh doesn't work, but there's no crash. >> > > > Hmm, try adding NL80211_IFTYPE_MESH_POINT here -> > > http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=blob;f=drivers/net/wireless/ath/ath5k/pcu.c;h=ec35503f6a40e6b6a1cc4323287b31e7cdd3a428;hb=HEAD#l733 It's already there, in ath5k_hw_set_opmode. We'll need to trace what's going on and see why we don't get beacons. Last night I had an ath5k MP suddenly start beaconing but I haven't been able to reproduce that yet. Xiao -- to test beaconing, I set up a second network interface in monitor mode and capture frames with wireshark, in my case that's on a separate PC. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
