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

Hi all, We want to support host level qos in oVirt hypervisors, but are not able to classify the vlanned traffic generated by the host to our desired hsfc qdisc classes. SInce many of our customers use vlans, and vlans are the way we separate networks in the host, we have to be able to classify