<div dir="ltr">most likely you offload enabled on your card, try disabling that to see if tcpdump does the right thing for you<div><br></div><div>----</div><div>kind regards</div><div>anupam</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 21, 2014 at 10:19 AM, Amit Agarwal <span dir="ltr"><<a href="mailto:amit@amit-agarwal.co.in" target="_blank">amit@amit-agarwal.co.in</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
I have query on vlan tagged packets received by network interface.<br>
<br>
Problem: I have application which would receive all packets on the interface<br>
and process them ( this could be including vlan tagged packets). However when<br>
the 8021q (vlan) module is not loaded and the appropriate interfaces for all<br>
the IDs are not created I see that the application is not able to decode them.<br>
When we capture with tcpdump/tshark/wireshark as well we see that the packets<br>
are not correctly displayed. The Ethernet header type itself is not correctly<br>
identified and thus the rest of the packet cannot be decoded. What could be<br>
causing this and is there a way to fix this?<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Thanks,<br>
-aka<br>
<br>
<br>
_______________________________________________<br>
Kernelnewbies mailing list<br>
<a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a><br>
<a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">In the beginning was the lambda, and the lambda was with Emacs, and Emacs was the lambda. </div>
</div>