lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a8cb8964-07b0-ef21-5565-9fe76ecf1f9c@gmail.com>
Date:   Mon, 31 Dec 2018 19:13:16 +0100
From:   Bartek Kois <bartek.kois@...il.com>
To:     Cong Wang <xiyou.wangcong@...il.com>
Cc:     Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: Problem with queuing vlan tagged packets after migration from
 3.16.0 to 4.9.0

Hi,
I tested 4.20 and the problem remains (it is not possible to classify 
tagged packets if the root filter is on physical interface).

Best regards
Bartek Kois

W dniu 30.12.2018 o 22:14, Bartek Kois pisze:
> 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@...il.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. :(

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ