tcpdump mailing list archives
Re: Cannot catch vlan frames with tcpdump
From: "Ian Brown" <ianbrn () gmail com>
Date: Mon, 28 Jan 2008 09:31:28 +0200
Hello, I am sniffing thus, on the side on which the pktgen module and script are running: tcpdump -vv -i eth0 vlan and host 192.168.0.10 whereas 192.168.0.10 is the destination. I also sniff thus: tcpdump -vv -i eth0 vlan And again - nothing in both these two filters. Any ideas ? Regards, Ian On Jan 28, 2008 9:03 AM, Guy Harris <guy () alum mit edu> wrote:
Ian Brown wrote:It is 8139 (RTL).Yes, but what interface name were you capturing on? eth0 (which I'm assuming is the RTL 8139 adapter in question), or some other interface (or pseudo-interface)? - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
- This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
Current thread:
- Cannot catch vlan frames with tcpdump Ian Brown (Jan 27)
- Re: Cannot catch vlan frames with tcpdump Guy Harris (Jan 27)
- Re: Cannot catch vlan frames with tcpdump Ian Brown (Jan 27)
- Re: Cannot catch vlan frames with tcpdump Guy Harris (Jan 27)
- Re: Cannot catch vlan frames with tcpdump Ian Brown (Jan 27)
- Re: Cannot catch vlan frames with tcpdump Ian Brown (Jan 28)
- Re: Cannot catch vlan frames with tcpdump Ian Brown (Jan 27)
- Re: Cannot catch vlan frames with tcpdump Guy Harris (Jan 27)