From: David Ahern <dsahern@kernel.org>
To: gaoxingwang <gaoxingwang1@huawei.com>, edumazet@google.com
Cc: davem@davemloft.net, liaichun@huawei.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, yanan@huawei.com, yoshfuji@linux-ipv6.org
Subject: Re: [Discuss]iproute2: ipv6 route add fail
Date: Mon, 22 Jan 2024 21:59:22 -0700 [thread overview]
Message-ID: <0e12d8a0-4ef8-4b22-bc61-072247df47a7@kernel.org> (raw)
In-Reply-To: <20240123030813.2493801-1-gaoxingwang1@huawei.com>
On 1/22/24 8:08 PM, gaoxingwang wrote:
>>> Hello everyone,
>>>
>>> Here is a particular problem with routing.
>>> Sometimes users can run the ip -6 route command to add a route whose destination address is the same as the gateway address, and it can be successfully added. However, adding another route with the same gateway address will fail later.
>>>
>>> Example:
>>> # ip -6 route add 2409:8080:5a0a:60c7::7/128 via 2409:8080:5a0a:60c7::7 dev eth2
I missed that this is a self-referencing route. This one really should
fail because it adds itself as a gateway.
>>> # ip -6 route add 2409:8080:5a0a:60c7::8/128 via 2409:8080:5a0a:60c7::7 dev eth2
>>> RTNETLINK answers: No route to host
and this one fails because of the above self referencing route; see
ip6_route_check_nh:
err = ip6_nh_lookup_table(net, cfg, gw_addr,
cfg->fc_table, flags, &res);
/* gw_addr can not require a gateway or resolve to a reject
* route. If a device is given, it must match the result.
*/
>>>
>>> Does the kernel not support this application scenario?
you need to remove the host route that adds a gateway as itself
next prev parent reply other threads:[~2024-01-23 4:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 8:51 ip6_gre: paninc in ip6gre_header gaoxingwang
2023-05-27 9:01 ` Eric Dumazet
2023-05-28 12:53 ` gaoxingwang
2023-05-30 3:21 ` gaoxingwang
2023-05-30 6:57 ` Eric Dumazet
2024-01-23 3:08 ` [Discuss]iproute2: ipv6 route add fail gaoxingwang
2024-01-23 4:59 ` David Ahern [this message]
2024-01-05 9:42 gaoxingwang
2024-01-22 4:10 ` David Ahern
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=0e12d8a0-4ef8-4b22-bc61-072247df47a7@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gaoxingwang1@huawei.com \
--cc=liaichun@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yanan@huawei.com \
--cc=yoshfuji@linux-ipv6.org \
/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
all inboxes | Powered by JetHome®