netdev - Re: Add `auto` VRF table ID option in iproute2

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: <8c364f52-7173-433a-aa4a-dc2f9908dd5e@gmail.com>
Date: Wed, 14 Aug 2024 10:12:04 -0600
From: David Ahern <dsahern@...il.com>
To: Ido Schimmel <idosch@...sch.org>, Mike Waterman <mwaterman@...tr.com>
Cc: netdev@...r.kernel.org, stephen@...workplumber.org,
 Daniel Gröber <dxld@...kboxed.org>
Subject: Re: Add `auto` VRF table ID option in iproute2

On 8/14/24 10:03 AM, Ido Schimmel wrote:
> AFAICT in ifupdown2 they have a table that keeps track of allocate IDs
> and they simply pick the next available one. Unlike ifupdown2, iproute2
> does not have state and it will need to query this information from the
> kernel which you can do yourself in a script before calling this
> command.
> 
> Overall I don't really see the benefit in something like that in
> iproute2 and I don't recall other iproute2 commands that work like that.
> 
> Also note that ifupdown2 reorders the FIB rules so that the l3mdev rule
> is before the local rule. This is something that iproute2 does not (and
> should not) do.
> 
> Adding David who might have a different opinion.

I agree with the summary. Table id management is for interface managers,
not tools like iproute2.