Hi, > Finally i went grave digging on the list and found this: > > "It's pretty trivial to do. Get either driver to export another net_dev > to userspace, and everything that is sent from userspace down that > device goes to the air directly. NOTE: you cannot send frames with > invalid FCS since the hardware appends it."
Hah, that was me. I stand by it. > The other question is: is it possible to convince the firmware that we > are doing (everything that is sent from userspace down that device goes to > the air directly) > is legitimate? The firmware doesn't care as long as 1) the plcp is correct (should probably be generated by the driver) and 2) the FCS is correct (the hardware appends it, so it is forced correct) I think that's all, but there might be something wrt. the 802.11 header. johannes
signature.asc
Description: This is a digitally signed message part
