From: David Ahern <dsahern@kernel.org>
To: gaoxingwang <gaoxingwang1@huawei.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org
Cc: liaichun@huawei.com, yanan@huawei.com
Subject: Re: [Discuss]iproute2: ipv6 route add fail
Date: Sun, 21 Jan 2024 21:10:20 -0700 [thread overview]
Message-ID: <90209854-8515-4f1e-8d6b-0182c8cab7ea@kernel.org> (raw)
In-Reply-To: <20240105094255.1498461-1-gaoxingwang1@huawei.com>
On 1/5/24 2:42 AM, 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
> # ip -6 route add 2409:8080:5a0a:60c7::8/128 via 2409:8080:5a0a:60c7::7 dev eth2
> RTNETLINK answers: No route to host
>
> Does the kernel not support this application scenario?
> Or should the kernel not allow routes with the same destination address as the gateway address to be added so that other more meaningful routes can be added successfully?
>
> This question puzzles me, thank you very much if your can reply.
try running `perf record -e fib6:*` and then run both route commands
above. After both have run, Ctrl-C on perf and then run `perf script`
next prev parent reply other threads:[~2024-01-22 4:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 9:42 gaoxingwang
2024-01-22 4:10 ` David Ahern [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-30 6:57 ip6_gre: paninc in ip6gre_header Eric Dumazet
2024-01-23 3:08 ` [Discuss]iproute2: ipv6 route add fail gaoxingwang
2024-01-23 4:59 ` 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=90209854-8515-4f1e-8d6b-0182c8cab7ea@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gaoxingwang1@huawei.com \
--cc=kuba@kernel.org \
--cc=liaichun@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yanan@huawei.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
all inboxes | Powered by JetHome®