From: Bartek Kois <bartek.kois@gmail.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: Problem with queuing vlan tagged packets after migration from 3.16.0 to 4.9.0
Date: Sun, 30 Dec 2018 22:14:28 +0100 [thread overview]
Message-ID: <de2e92c4-3b4b-3b0a-2f5c-e91da15e08a3@gmail.com> (raw)
In-Reply-To: <CAM_iQpUnXGM45=w6ts2DEDX3+eS46FDtG95CCy07R0Fa0pmcaw@mail.gmail.com>
Hi
I haven`t tested any newer kernels cause I thought that something
related to packet classification has been changed permanently and I have
to figure out what. Which one should I test?
Best regards
Bartek Kois
W dniu 30.12.2018 o 19:53, Cong Wang pisze:
> Hello,
>
> On Sat, Dec 29, 2018 at 11:54 AM Bartek Kois <bartek.kois@gmail.com> wrote:
>>
>> Hi,
>> I`ve got problem while queuing with HFSC vlan tagged packets after
>> migrating my tc scripts from Debian 8.2 (3.16.0-4-amd64) to Debian 9.5
>> (4.9.0-6-amd64). tc filters added to eth1 do not classify correctly src
>> and dst ip addresses anymore if they are encapsulated with vlan tag
>> which wasn`t a problem previously. It works fine if I run them without
>> vlan tagging oraz if the root device is a vlan (eg. tc filter add dev
>> eth1.20). Could you please help me find out what has changed in kernel
>> between those two versions and what is walkaround for that problem?
> Does this problem still exist on some latest kernel? 4.9 is still too old
> for upstream to be interesting. :(
next prev parent reply other threads:[~2018-12-30 21:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-29 12:52 Problem with queuing vlan tagged packets after migration from 3.16.0 to 4.9.0 Bartek Kois
2018-12-30 18:53 ` Cong Wang
2018-12-30 21:14 ` Bartek Kois [this message]
2018-12-31 18:13 ` Bartek Kois
2019-01-01 19:33 ` Cong Wang
2019-01-01 19:46 ` Bartek Kois
2019-01-03 3:30 ` Cong Wang
2019-01-03 15:25 ` Bartek Kois
2019-01-03 20:44 ` Cong Wang
2019-01-04 18:11 ` Bartek Kois
2019-01-05 5:03 ` Cong Wang
2019-01-06 14:44 ` Jamal Hadi Salim
2019-01-10 13:45 ` Simon Horman
2019-01-12 12:12 ` Jamal Hadi Salim
2019-01-13 18:22 ` Cong Wang
2019-01-15 15:09 ` Jamal Hadi Salim
2019-01-15 18:19 ` Cong Wang
2019-01-16 14:13 ` Jamal Hadi Salim
2019-01-14 8:12 ` Simon Horman
2019-01-15 15:16 ` Jamal Hadi Salim
2019-01-18 4:32 ` Eric W. Biederman
2019-01-03 21:49 ` Anton Danilov
2019-01-04 7:07 ` Bartek Kois
2018-12-31 21:47 ` Jakub Kicinski
2018-12-31 22:12 ` Bartek Kois
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=de2e92c4-3b4b-3b0a-2f5c-e91da15e08a3@gmail.com \
--to=bartek.kois@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).