> I'm not convinced that getting frames with bad CRC is a feature needed
> by many users. I see your patch adds some documentation to FAQ, but I
> have never seen any questions about reporting frames with bad CRC in
> monitor mode. FAQ is not a replacement for documentation. It should
> answer questions that are actually asked by the users.
Were it in a mainstream driver, I would use it (and the userbase who
would use it would likely expand accordingly): being able to detect and
process frames with a bad FCS allows for noise and congestion statistics
and processing and lets us leverage the drivers the same way commercial
wireless survey solutions like Fluke and AirMagnet do.
If it isn't added mainstream, I'll probably still use it as a separate
patch once I add fcs calculations and tracking handlers.
My $0.02.
-m
--
Quidquid Latine Dictum Sit, Altum Viditur
(Anything said in latin sounds profound)
pgpieKlOePfwL.pgp
Description: PGP signature
|
