[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c36dceb4-8128-4fe7-ba19-e8bcafa0ba4b@kernel.org>
Date: Mon, 12 Jan 2026 08:25:45 -0700
From: David Ahern <dsahern@...nel.org>
To: Ido Schimmel <idosch@...dia.com>, netdev@...r.kernel.org
Cc: davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
edumazet@...gle.com, horms@...nel.org, petrm@...dia.com
Subject: Re: [PATCH net-next 2/5] selftests: fib-onlink: Remove "wrong nexthop
device" IPv6 tests
On 1/11/26 5:08 AM, Ido Schimmel wrote:
> The command in the test fails as expected because IPv6 forbids a nexthop
> device mismatch:
>
> # ./fib-onlink-tests.sh -v
> [...]
> COMMAND: ip -6 ro add table 1101 2001:db8:102::103/128 via 2001:db8:701::64 dev veth5 onlink
> Error: Nexthop has invalid gateway or device mismatch.
>
> TEST: Gateway resolves to wrong nexthop device - VRF [ OK ]
> [...]
>
> Where:
>
> # ip route get 2001:db8:701::64 vrf lisa
> 2001:db8:701::64 dev veth7 table 1101 proto kernel src 2001:db8:701::1 metric 256 pref medium
>
> This is in contrast to IPv4 where a nexthop device mismatch is allowed
> when "onlink" is specified:
>
> # ip route get 169.254.7.2 vrf lisa
> 169.254.7.2 dev veth7 table 1101 src 169.254.7.1 uid 0
> # ip ro add table 1101 169.254.102.103/32 via 169.254.7.2 dev veth5 onlink
> # echo $?
> 0
>
> Remove these tests in preparation for aligning IPv6 with IPv4 and
> allowing nexthop device mismatch when "onlink" is specified.
>
> A subsequent patch will add tests that verify that both address families
> allow a nexthop device mismatch with "onlink".
>
> Reviewed-by: Petr Machata <petrm@...dia.com>
> Signed-off-by: Ido Schimmel <idosch@...dia.com>
> ---
> tools/testing/selftests/net/fib-onlink-tests.sh | 7 -------
> 1 file changed, 7 deletions(-)
>
Reviewed-by: David Ahern <dsahern@...nel.org>
Powered by blists - more mailing lists