netdev - Re: [PATCH iproute2-next 0/2] ip: Nexthop flags extensions

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] [day] [month] [year] [list]

Message-ID: <335227b5-56e6-3312-d090-84d2fabff32b@gmail.com>
Date:   Sun, 22 Nov 2020 12:47:23 -0700
From:   David Ahern <dsahern@...il.com>
To:     Ido Schimmel <idosch@...sch.org>, netdev@...r.kernel.org
Cc:     roopa@...dia.com, mlxsw@...dia.com,
        Ido Schimmel <idosch@...dia.com>
Subject: Re: [PATCH iproute2-next 0/2] ip: Nexthop flags extensions

On 11/19/20 6:57 AM, Ido Schimmel wrote:
> From: Ido Schimmel <idosch@...dia.com>
> 
> Patch #1 prints the recently added 'RTNH_F_TRAP' flag.
> 
> Patch #2 makes sure that nexthop flags are always printed for nexthop
> objects. Even when the nexthop does not have a device, such as a
> blackhole nexthop or a group.
> 
> Example output with netdevsim:
> 
> # ip nexthop
> id 1 via 192.0.2.2 dev eth0 scope link trap
> id 2 blackhole trap
> id 3 group 2 trap
> 
> Example output with mlxsw:
> 
> # ip nexthop
> id 1 via 192.0.2.2 dev swp3 scope link offload
> id 2 blackhole offload
> id 3 group 2 offload
> 
> Tested with fib_nexthops.sh that uses "ip nexthop" output:
> 
> Tests passed: 164
> Tests failed:   0
> 
> Ido Schimmel (2):
>   ip route: Print "trap" nexthop indication
>   nexthop: Always print nexthop flags
> 
>  ip/ipnexthop.c | 3 +--
>  ip/iproute.c   | 2 ++
>  2 files changed, 3 insertions(+), 2 deletions(-)
> 

applied to iproute2-next, without preferential treatment.