Hello,
BTW, I wrote a small module which checks the features member of the
8139 RTL net device.
(see: include/linux/netdevice.h in the kernel tree).
I found out the followoing :
NETIF_F_VLAN_CHALLENGED is not set => VLANs is supported
NETIF_F_HW_VLAN_RX is NOT set => no HW VLAN RX acceleration
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 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.
It is 8139 (RTL).
No VLAN hw acceleration as far as I know,
Ian
On Jan 27, 2008 10:34 PM, Guy Harris <[EMAIL PROTECTED]> wrote:
> Ian Brown wrote:
>
> > - I tried sniffing in various ways , like by "tcpdump -f vlan" and
> > "tcpdump -f vlan and net 192.168.0.0" and "tcpdump -f vlan and udp
> >
Ian Brown wrote:
- I tried sniffing in various ways , like by "tcpdump -f vlan" and
"tcpdump -f vlan and net 192.168.0.0" and "tcpdump -f vlan and udp
port 9" and many other ways . on both sides,
(192.168.0.10 and the source machine , where pktgen runs) but I could
not catch any VLAN frames.
Hello,
- I am using pktgen on Linux to generate vlan traffic.
- I am sniffing with tcpdump on both sides (src and dest) and cannot
catch VLAN traffic.
- I tried sniffing in various ways , like by "tcpdump -f vlan" and
"tcpdump -f vlan and net 192.168.0.0" and "tcpdump -f vlan and udp
port
