To answer my own question - it seems one can configure the timers to only wake up for dtim rather than every beacon, so you'd only get beacons for that.
Next is figuring out why ath9k and freebsd don't cope well with badly behaving access points that don't beacon out at even remotely predictable times. Adrian On Apr 24, 2014 7:16 PM, "Adrian Chadd" <adr...@freebsd.org> wrote: > On 24 April 2014 19:12, Adrian Chadd <adr...@freebsd.org> wrote: > > .. and to clarify, if I disable ATH_RX_FILT_BEACON (0x4) in the > > rxfilter register, I get no beacons at all. I was hoping I'd get > > something really useful like beacons with my TIM bit set or something. > > > > Also, for some odd reason I'm seeing _all_ beacons, not just beacons > > matching my BSSID. Has anyone else seen that behaviour? > > Man, I feel dumb. Some of the chips support MYBEACON, rather than > BEACON. Time to figure out which chips do and which chips don't. > > My original question still stands though - has anyone seen any mode > where the chip only returns beacons that are worth listening for? > > > -a >
_______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
