Hi,
I'm working on support for hardware-based frame decryption in zd1211rw.
While doing so I encountered some strange behaviour in ieee80211 which
I'm wondering if someone can clarify. Alternatively if someone could
just confirm how the Intel hardware behaves here that would be useful...
The normal structure of a WEP-encrypted frame is:
1. 802.11 header (including WEP bit)
2. IV (4 bytes)
3. Encrypted data
The structure of a frame coming from the zd1211 device where the frame
has been decrypted in hardware is:
1. 802.11 header (including WEP bit)
2. IV (4 bytes)
3. Decrypted data
We pass this up to ieee80211_rx as usual, but things don't work right.
ieee80211 converts the frame to an ethernet frame as usual, but includes
the WEP IV as the first 4 bytes of the data. (Instead, I want it to skip
over the IV, successful decryption has already been verified)
This is easy enough to fix with another ieee80211 flag or something like
that, but I am wondering why it already works for existing drivers which
decrypt in hardware. When doing hardware decryption, does the Intel
hardware really cut out the 4 byte IV and shift the rest of the data so
that it continues immediately on from the header? Seems like a
complicated operation to do in hardware (although I don't really know
much about hw design...)
Daniel
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
