I've been working on the commit previous to the PCU code breakage (8485b7f773a8e9883e0165273940f16a086eba2b), but I'm still having problems (beaconing is working, but links are rarely established, most of the time to packets get through). Cheers Keir 2008/12/16 Steve Brown <sbrown@xxxxxxxxxxxx>: > Keir wrote: >> >> Having has no luck with an old rc6 version (basically all plink >> packets were getting lost), I upgraded to the newest git (rc8) however >> now when I run iw dev mesh0 station sump I don't see a single other >> mesh point. This would imply that presumably beaconing is broken? >> >> Does anyone know a revision for which ath5k is properly working? I am >> yet to find one that works on my system. >> >> Cheers >> >> Keir >> -- >> 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 >> > > Beaconing seems broken by Update PCU code > dd1c9abd167de9bb9457a57694a1ab5e5801a0c1. After this patch, beacon debug > says beacons sent, but sniffer sees none. > > A snapshot of ath5k prior to this and git 12/10 > (b6d06c9669f27db31a0317fc98fedc8ff1ba4822) works for me with hostapd/wpa. > It's been running for the past few days. > > Mesh beaconing also works. I didn't test two nodes; I only sniffed the > beacons. > > I had to comment out 5GHz in caps.c because of too many channels. It's a > nl80211 buffer size problem that's been discussed. > > Steve > > > -- 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
