netdev - Need a creative way to negate u32 filter matches

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 29 May 2015 22:32:09 -0400
From:	"John A. Sullivan III" <jsullivan@...nsourcedevel.com>
To:	netdev <netdev@...r.kernel.org>
Subject: Need a creative way to negate u32 filter matches

Hello, all.  I understand there is no direct way to negate a u32 match.
I have a setup where I am redirecting all ingress traffic from the
physical interface to an ifb interface with a u32 match u8 0 0 action
mirred egress redirect filter attached to ffff:

I do not want to send ingress ESP packets to the IFB interface.  How do
I exclude those?
I tried creating a filter with a lower prio and added before the above
rule which matches ESP packets and does nothing with them (action pass)
in the hope that it would be the first match and ESP packets would then
not be matched against the second filter.  That does not appear to be
working from tc -s filter.  The rule is hit, the match succeeds, but the
success count is 0 and I see the filter on the IFB interface which
identifies ESP packets is successfully being hit.

How do I redirect all packets EXCEPT ESP packets to an IFB interface?
Thanks - John

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html