Bridge does not forward packets to a tap device

at 00:00:0c:07:ac:00, length 46 11:12:50.535085 ARP, Request who-has 10.35.19.120 tell 10.35.16.244, length 28 11:12:50.535106 ARP, Request who-has 10.35.19.120 tell 10.35.16.244, length 42 11:12:50.535372 ARP, Reply 10.35.19.120 is-at 00:1a:4a:23:13:cb, length 42 -- Thanks, Ido Barkan -- To unsubs

Re: cannot classify vlanned traffic using tc-ematch

For whom that this might be interesting, the missing part was a prfix of the flowid: $ tc filter replace dev eno2 protocol all parent 1389: pref 168 basic match 'meta(vlan eq 168)' flowid 1389:a8 Thanks, Ido On Thu, Oct 15, 2015 at 2:08 PM, Ido Barkan wrote: > Hi all, > >

cannot classify vlanned traffic using tc-ematch

. kernel 3.10.0-320.el7.x86_64 Can you help? -- Thanks, Ido Barkan -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

using iperf over a veth pair

ruls seems right, as they are automatically being created upon assigning ip addresses to the veth pair ends. Does the kernel short-circuits traffic here? How can I Tell it to pass traffic via my virtual devices? -- Thanks, Ido Barkan -- To unsubscribe from this list: send the line "unsubscri