On Wed, 26 Mar 2008 00:01:41 +0100 Markus <[EMAIL PROTECTED]> wrote: > Were there any changes to tcpdump, the em driver, pcap or another part > of the OS in recent history which could lead to such a behavior? > Again, regular packets on any em-interface we can collect just fine, > just the packets coming in through the monitoring port are being > "ignored"...
Reply to myself, for the archives: the issue was resolved. While before and including 5.2.1-RELEASE (and possibly in later releases as well, but NOT in 6.3-RELEASE and 7.0-RELEASE) tcpdump displayed simply ALL packets, regardless whether those packets were VLAN tagged or not, coming in on the specific interface(s) (em(4)), i.e. tcpdump -n -i em3 host a.b.c.d it now (in 6.3-RELEASE and 7.0-RELEASE) requires explicitly the following statement to display VLAN tagged traffic: tcpdump -n -i em3 vlan and host a.b.c.d Or in other words: add "vlan" to the tcpdump expression and it works just fine. Before the latest few releases this wasn't necessary for VLAN tagged packets. Regards Markus _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"