Hello All,

I am having some trouble transmitting a SNAP packets on my machine. It appears 
that something is modifying the length field of the Ethernet frame before the 
packet is transmitted.

When tracing the outgoing packets with Wireshark, the length field is correct. 
However, when the receiver see's these packets the length field has changed. 
The length field the receiver see's is consistently 8 higher than it should be 
(IE: if the payload is 40 bytes long, the length field is 48).

I believe the problem has something to do with the length of the buffer. I ran 
a VM on the sender & had the VM generate the SNAP packets. The results were 
different; the VM padded all of the packets to the minimum Ethernet frame 
length before they got to the ath9k driver. The trace from the sender still 
showed the correct length for the packet. The length fields transmitted were 
now all set to 54 (IE: the length of the padded payload + 8).

The sender is running the ath9k driver on a Qualcomm Atheros AR9485 Wireless 
Network Adaptor. It's a 64 bit kernel (3.11.0-12-generic). I was able to 
transmit the SNAP packets with the same code on a machine with a Broadcom 
wireless card. This makes me think that I'm doing something wrong that only 
your driver is catching.

Is there anywhere in the ath9k driver where the Ethernet header's length value 
is modified on an outgoing packet?

Thanks,
Sean Stalley
_______________________________________________
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel

Reply via email to