Thread (8 messages) flat view 8 messages, 3 authors, 2021-04-09

Re: [BUG / question] in routing rules, some options (e.g. ipproto, sport) cause rules to be ignored in presence of packet marks

From: Florian Westphal <fw@strlen.de>
Date: 2021-04-09 13:03:04

Michal Soltys [off-list ref] wrote:
On 3/29/21 10:52 PM, Ido Schimmel wrote:
quoted
ip_route_me_harder() does not set source / destination port in the
flow key, so it explains why fib rules that use them are not hit after
mangling the packet. These keys were added in 4.17, but I
don't think this use case every worked. You have a different experience?
So all the more recent additions to routing rules - src port, dst port, uid
range and ipproto - are not functioning correctly with the second routing
check.

Are there plans to eventually fix that ?

While I just adjusted/rearranged my stuff to not rely on those, it should
probably be at least documented otherwise (presumably in ip-rule manpage and
perhaps in `ip rule help` as well).
Fixing this would be better. As Ido implies it should be enough to fully
populate the flow keys in ip(6)_route_me_harder.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help