On Tue, Jan 15, 2019 at 7:09 AM Jamal Hadi Salim <j...@mojatatu.com> wrote: > > On 2019-01-13 1:22 p.m., Cong Wang wrote: > > On Sat, Jan 12, 2019 at 4:12 AM Jamal Hadi Salim <j...@mojatatu.com> wrote: > >> > >> It will be a new feature in the sense the user will have to specify > >> something like (adding "mark" for clarify): > >> > >> tc filter add .... protocol 802.1q .. u32 \ > >> match u32 0 0 \ > >> mark 15 \ > >> vlanid 1234 > >> action vlan pop reclassify > > > > This is clearly a new feature, however, it only solves one part of > > the problem, the length of IPv4 header is still various and there > > is no way to predict it. > > > As i mentioned in my earlier email, that feature should work. > What is broken?
I never say it is broken. I am saying you only fix vlan case by introducing "vlanid XXX" and leave IPv4 option cases unfixed. As I keep saying, this is a kinda design flaw of u32 probably can't be workarounded. Thanks.
