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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Mon, 17 Aug 2020 17:38:44 +0530
From:   satish dhote <>
To:     Cong Wang <>
Cc:     Linux Kernel Network Developers <>,
        Daniel Borkmann <>
Subject: Re: Question about TC filter

Sorry for responding late. I got engaged with other work.
I didn't replace ingress with ffff

To do more experiments, I will have to recompile everything
from fresh as I lost that setup where I was experimenting with
tc utility.

But if we can get inputs from Daniel's about this change,
it will help us to figure out whether this was really a bug or
expected behavior.


On Fri, Aug 7, 2020 at 12:05 AM Cong Wang <> wrote:
> On Thu, Aug 6, 2020 at 10:21 AM satish dhote <> wrote:
> >
> > Hi Cong,
> >
> > I tried adding below patch i.e. "return cl == 0 ? q->block : NULL;"
> > but after this I'm not able to see any output using "tc filter show... "
> > command. Looks like the filter is not getting configured.
> What exact command did you use? If you specify "ingress" rather
> than "ffff:", it is exactly _my_ goal, because prior to clsact, only
> "ffff:" could match ingress qdisc, the keyword "ingress" did not
> even exist.
> Of course, it may not be Daniel's intention, he might expect
> "ingress" to match ingress qdisc too for convenience.
> Thanks.

Powered by blists - more mailing lists