I have recently tried to get corrupted frames, in order to examine how
they are corrupted. In order to do that, I hacked the orinoco.13e
driver with the monitor patch. I identified four candidate tests to
change for getting bad frames, and I am experimenting with disabling
them. I'd like to ask for some help understanding their exact meaning:
1) (status & HERMES_RXSTAT_UNDECRYPTABLE)
What does exactly mean? I am speculating that this is where the PLCP
header CRC is checked. Is this correct?
2) (status & HERMES_RXSTAT_BADCRC)
This follows immediately (in fact is an `else' clause) and I suppose
it is where the MPDU CRC is checked. Is this correct?
3) (length > IEEE802_11_DATA_LEN)
This is a sanity check. I suppose the length is taken from the PLCP
header, right?
4) ( HERMES_RXSTATUS_MACPORT_GET(status) )
If the CRC is bad, this one may be broken, right? That is, if the
CRC is bad, one could get any number here. Can this be broken if the
PLCP header CRC is good?
Thanks for reading, and thanks to those that will care to answer.
--
Francesco Potortì (ricercatore) Voice: +39 050 315 3058 (op.2111)
ISTI - Area della ricerca CNR Fax: +39 050 313 8091
via G. Moruzzi 1, I-56124 Pisa Email:
Potorti-8I8jPFND8kM1GQ1Ptb7lUw@xxxxxxxxxxxxxxxx
Web: http://fly.isti.cnr.it/ Key: fly.isti.cnr.it/public.key
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
|
