Netdev List
 help / color / mirror / Atom feed
From: Hangbin Liu <liuhangbin@gmail.com>
To: David Ahern <dsahern@kernel.org>
Cc: netdev@vger.kernel.org
Subject: selftest fib_nexthop_multiprefix failed due to route mismatch
Date: Tue, 21 Nov 2023 14:40:35 +0800	[thread overview]
Message-ID: <ZVxQ42hk1dC4qffy@Laptop-X1> (raw)

Hi David,

Recently when run fib_nexthop_multiprefix test I saw all IPv6 test failed.
e.g.

# ./fib_nexthop_multiprefix.sh
TEST: IPv4: host 0 to host 1, mtu 1300                              [ OK ]
TEST: IPv6: host 0 to host 1, mtu 1300                              [FAIL]

With -v it shows

COMMAND: ip netns exec h0 /usr/sbin/ping6 -s 1350 -c5 -w5 2001:db8:101::1
PING 2001:db8:101::1(2001:db8:101::1) 1350 data bytes
From 2001:db8:100::64 icmp_seq=1 Packet too big: mtu=1300

--- 2001:db8:101::1 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

Route get
2001:db8:101::1 via 2001:db8:100::64 dev eth0 src 2001:db8:100::1 metric 1024 expires 599sec mtu 1300 pref medium
Searching for:
    2001:db8:101::1 from :: via 2001:db8:100::64 dev eth0 src 2001:db8:100::1 .* mtu 1300

TEST: IPv6: host 0 to host 1, mtu 1300                              [FAIL]

So we can get the Packet too big from 2001:db8:100::64 successfully. There
is no "from ::" anymore. I plan to fix this issue. But I can't find which
commit changed the behavior and the client could receive Packet too big
message with correct src address.

Do you have any hints?

Thanks
Hangbin

             reply	other threads:[~2023-11-21  6:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21  6:40 Hangbin Liu [this message]
2023-11-21 17:40 ` selftest fib_nexthop_multiprefix failed due to route mismatch David Ahern
2023-12-06  3:47   ` Hangbin Liu
2023-12-08 19:21     ` David Ahern
2023-12-11  9:22       ` Hangbin Liu
2023-12-11 13:45         ` 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=ZVxQ42hk1dC4qffy@Laptop-X1 \
    --to=liuhangbin@gmail.com \
    --cc=dsahern@kernel.org \
    --cc=netdev@vger.kernel.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