From: Ido Schimmel <idosch@nvidia.com>
To: Yaroslav Dudkov <aroslavdudkov622@gmail.com>
Cc: netdev@vger.kernel.org, David Ahern <dsahern@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Wei Wang <weiwan@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] ipv6: ignore link state in gateway check
Date: Fri, 30 Oct 2026 18:06:43 +0200 [thread overview]
Message-ID: <20261030160643.GA116970@shredder> (raw)
In-Reply-To: <20261028152634.3355852-1-aroslavdudkov622@gmail.com>
On Wed, Oct 28, 2026 at 03:26:33PM +0000, Yaroslav Dudkov wrote:
> IPv6 route cannot be added in table when all
> following conditions are true:
> - gateway is not link-local address
> - ignore_routes_with_linkdown=1 on device
> - nexthop has no carrier
> - gateway is not present or covered by any route in table already
> Also multipath routes addition is invalidated by kernel even
> if only one of added nexthops satisfies all above conditions.
>
> Reproducer:
>
> ip netns add t
> ip -n t link add va type veth peer name vb
> ip -n t link set va up
> ip -n t addr add fd00::1/64 dev va nodad
> ip netns exec t sysctl -w \
> net.ipv6.conf.va.ignore_routes_with_linkdown=1
> ip -n t -6 route add 2001:db8::/64 via fd00::2 dev va
> # added
> ip -n t -6 route add 2001:db8::/64 table 100 via fd00::2 dev va
> # RTNETLINK answers: No route to host
> ip -n t -6 route show table all
> ip netns del t
>
> Route should be added because:
> - RT6_LOOKUP_F_IGNORE_LINKSTATE in commit d5d32e4b7668
> ("net: ipv6: Do not consider link state for nexthop validation")
> was added for this
> - the same route is valid in main table (when no specifying table id
> while adding route)
> - fib6_nh_init() initializes nexthops with no carrier
> - IPv4 already does this (fib_check_nh_v4_gw() ignores link state
> using the FIB_LOOKUP_IGNORE_LINKSTATE flag)
>
> Before commit b2c709cce682 ("ipv6: Convert gateway validation to
> use fib6_info") rt6_lookup() was used for checking if nexthop is
> valid, rt6_lookup called rt6_device_match() which does not check the
> link state. After change rt6_lookup() to fib6_lookup()
> find_match() under fib6_lookup() started to invalidate linkdown
> devices, because RT6_LOOKUP_F_IGNORE_LINKSTATE is not passed to it.
>
> Adding RT6_LOOKUP_F_IGNORE_LINKSTATE to flags for ip6_route_check_nh()
> solves the problem. RT6_LOOKUP_F_IGNORE_LINKSTATE is already used
> inside the first search ip6_nh_lookup_table() and fixes the
> bug in second search fib6_lookup(). Also RT6_LOOKUP_F_IGNORE_LINKSTATE
> isn't read inside fib6_select_path().
>
> Fixes: b2c709cce682 ("ipv6: Convert gateway validation to use fib6_info")
> Signed-off-by: Yaroslav Dudkov <aroslavdudkov622@gmail.com>
> ---
> IPv4 example of this situation:
> ip netns add t
> ip -n t link add va type veth peer name vb
> ip -n t link set va up
> ip -n t addr add 192.168.0.1/24 dev va
> ip netns exec t sysctl -w \
> net.ipv4.conf.va.ignore_routes_with_linkdown=1
> ip -n t route add 192.0.2.0/24 table 100 via 192.168.0.2 dev va
> # added
> ip -n t route show table all
> ip netns del t
Please turn this into a selftest so that it doesn't regress in the
future. Something like [1] (vibe coded).
>
> Also when adding RT6_LOOKUP_F_IGNORE_LINKSTATE to flags of
> ip6_route_check_nh() makes adding this flag inside of
> ip6_nh_lookup_table() unnecessary for this call, making another call in
> ip6_route_check_nh_onlink() with flags=0 the only place where it is
> needed.
> ---
> net/ipv6/route.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/ipv6/route.c b/net/ipv6/route.c
> index 94e5ef1c4f83..95d7b5b10e51 100644
> --- a/net/ipv6/route.c
> +++ b/net/ipv6/route.c
> @@ -3426,7 +3426,7 @@ static int ip6_route_check_nh(struct net *net,
> {
> const struct in6_addr *gw_addr = &cfg->fc_gateway;
> struct net_device *dev = _dev ? *_dev : NULL;
> - int flags = RT6_LOOKUP_F_IFACE;
> + int flags = RT6_LOOKUP_F_IFACE | RT6_LOOKUP_F_IGNORE_LINKSTATE;
Maintain reverse xmas tree:
https://docs.kernel.org/next/process/maintainer-netdev.html#local-variable-ordering-reverse-xmas-tree-rcs
> struct fib6_result res = {};
> int err = -EHOSTUNREACH;
>
> --
> 2.54.0
>
[1]
diff --git a/tools/testing/selftests/net/fib_tests.sh b/tools/testing/selftests/net/fib_tests.sh
index 7c47d7fe250d..76f950eaef52 100755
--- a/tools/testing/selftests/net/fib_tests.sh
+++ b/tools/testing/selftests/net/fib_tests.sh
@@ -406,10 +406,48 @@ fib_carrier_unicast_test()
cleanup
}
+fib_carrier_gw_test()
+{
+ echo
+ echo "Gateway validation with carrier down"
+
+ setup
+
+ set -e
+ $NS_EXEC sysctl -qw net.ipv4.conf.dummy0.ignore_routes_with_linkdown=1
+ $NS_EXEC sysctl -qw net.ipv6.conf.dummy0.ignore_routes_with_linkdown=1
+ $IP link set dev dummy0 carrier off
+ sleep 1
+ set +e
+
+ $IP route add 203.0.113.0/25 via 198.51.100.2 dev dummy0
+ log_test $? 0 "IPv4 route in main table"
+ $IP -6 route add 2001:db8:10::/64 via 2001:db8:1::2 dev dummy0
+ log_test $? 0 "IPv6 route in main table"
+
+ $IP route add 203.0.113.0/25 table 100 via 198.51.100.2 dev dummy0
+ log_test $? 0 "IPv4 route in non-main table"
+ $IP -6 route add 2001:db8:10::/64 table 100 via 2001:db8:1::2 dev dummy0
+ log_test $? 0 "IPv6 route in non-main table"
+
+ $IP route add 203.0.113.128/25 table 100 via 198.51.100.2
+ log_test $? 0 "IPv4 route in non-main table without device"
+ $IP -6 route add 2001:db8:11::/64 table 100 via 2001:db8:1::2
+ log_test $? 0 "IPv6 route in non-main table without device"
+
+ $IP route show table 100 203.0.113.0/25 | grep -q "linkdown"
+ log_test $? 0 "IPv4 linkdown flag set"
+ $IP -6 route show table 100 2001:db8:10::/64 | grep -q "linkdown"
+ log_test $? 0 "IPv6 linkdown flag set"
+
+ cleanup
+}
+
fib_carrier_test()
{
fib_carrier_local_test
fib_carrier_unicast_test
+ fib_carrier_gw_test
}
fib_rp_filter_test()
prev parent reply other threads:[~2026-10-30 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 15:26 [PATCH net] ipv6: ignore link state in gateway check Yaroslav Dudkov
2026-10-30 16:06 ` Ido Schimmel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261030160643.GA116970@shredder \
--to=idosch@nvidia.com \
--cc=aroslavdudkov622@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=weiwan@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox