-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
My problem was caused by an using an out-of-date CRDA. Updating to the
latest CRDA and regulatory DB got me past the problem.
For anyone else experiencing problems with git-pull or git-clone of
the CRDA you should note that it was moved
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm verifying a model of the 802.11 channel contention behaviours
experimentally and have discovered something odd i in ath5k which I
don't understand. It appears that both before and after sending a
beacon a station incurs an unexplained delay
Hi
This came up a few weeks back and I've run some tests in ad hoc mode both in
madwifi (2.6.24. and MadWifi-ng 0.9.4) and ath5k (2.6.30.4). I am using a
PRISM II card as my reference because it documents the timestamp resolution
and says the timestamp is for the first symbol and so all my tests
Hi,
I've asked elsewhere but I can't seem to find an answer.
Is it possible to lock an ath5k managed interface into 802.11b mode?
MadWifi-NG allows this with iwpriv ath0 mode 11b but, of course, there's
no equivalent in ath5k.
I looked at the hardware initialization and it seems to be that we
