From: Hajime Tazaki <tazaki@sfc•wide.ad.jp>
To: kafai@fb•com
Cc: netdev@vger•kernel.org, hannes@stressinduktion•org,
steffen.klassert@secunet•com, davem@davemloft•net,
yangyingliang@huawei•com, shengyong1@huawei•com,
Kernel-team@fb•com
Subject: Re: [PATCH net-next 3/5] ipv6: Stop /128 route from disappearing after pmtu update
Date: Sun, 03 May 2015 23:26:45 +0900 [thread overview]
Message-ID: <m28ud5u47u.wl@sfc.wide.ad.jp> (raw)
In-Reply-To: <20150503010055.GC2731450@devbig242.prn2.facebook.com>
At Sat, 2 May 2015 18:00:55 -0700,
Martin KaFai Lau wrote:
> > 09:00:04.401092 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 16) fe80::200:ff:fe00:2 > ff02::2: [icmp6 sum ok] ICMP6, router solicitation, length 16
> > source link-address option (1), length 8 (1): 00:00:00:00:00:02 0x0000: 0000 0000 0002
> Was it captured at the sender side?
> Did the receiver (2001:1::2) get the echo request?
the capture was on the sender side.
the receiver got the echo request: I will detail the next
email but since two nodes connected back to back via
point-to-point data link, the receiver side also has exactly
the same pcap.
> > (snip)
> > - 'ip -6 a' at the ping6 sender
> > 7: sim0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qlen 1000
> > inet6 2001:1::1/64 scope global
> > valid_lft forever preferred_lft forever
> > inet6 fe80::200:ff:fe00:1/64 scope link
> > valid_lft forever preferred_lft forever
> >
> > - 'ip -6 r show' at the ping6 sender
> > 2001:1::/64 dev sim0 proto kernel metric 256
> > fe80::/64 dev sim0 proto kernel metric 256
> >
> hmm...It is weird. It is a /64 route, so it should have
> failed the (rt->dst.flags & DST_HOST) test anyway...
>
> > # the results of ip command on receiver side are almost
> > similar.
> >
> > I found that the test uses non-ARP interface between nodes:
> > if I changed the interface to 'non-NOARP' NIC, the issue has
> > gone away without the revert.
> >
> > I'm using the following scenario: just FYI.
> >
> > https://gist.github.com/thehajime/26be8606ddbb924f357c
> >
> You meant without 'arp off'?
Yes, I meant that.
> Can you grep those IP from 'ip -6 neigh'?
there is no output from 'ip -6 neigh' since the interfaces
is configured with IFF_NOARP.
> Can you try this patch just to confirm:
I applied the updated patch and the ping successfully got
replies.
-- Hajime
next prev parent reply other threads:[~2015-05-03 14:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 20:03 [PATCH net-next 0/5] ipv6: Stop /128 route from disappearing after pmtu update Martin KaFai Lau
2015-04-28 20:03 ` [PATCH net-next 1/5] ipv6: Consider RTF_CACHE when searching the fib6 tree Martin KaFai Lau
2015-04-28 20:03 ` [PATCH net-next 2/5] ipv6: Extend the route lookups to low priority metrics Martin KaFai Lau
2015-04-28 20:03 ` [PATCH net-next 3/5] ipv6: Stop /128 route from disappearing after pmtu update Martin KaFai Lau
2015-05-02 22:41 ` Hajime Tazaki
2015-05-02 23:20 ` Martin KaFai Lau
2015-05-03 0:19 ` Hajime Tazaki
2015-05-03 1:00 ` Martin KaFai Lau
2015-05-03 1:03 ` Martin KaFai Lau
2015-05-03 14:26 ` Hajime Tazaki [this message]
2015-05-03 3:38 ` Martin KaFai Lau
2015-05-03 14:29 ` Hajime Tazaki
2015-05-03 19:01 ` Martin KaFai Lau
2015-05-04 0:29 ` Martin KaFai Lau
2015-05-04 1:11 ` Hajime Tazaki
2015-04-28 20:03 ` [PATCH net-next 4/5] ipv6: Stop rt6_info from using inet_peer's metrics Martin KaFai Lau
2015-04-28 20:03 ` [PATCH net-next 5/5] ipv6: Remove DST_METRICS_FORCE_OVERWRITE and _rt6i_peer Martin KaFai Lau
2015-05-02 1:01 ` [PATCH net-next 0/5] ipv6: Stop /128 route from disappearing after pmtu update David Miller
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=m28ud5u47u.wl@sfc.wide.ad.jp \
--to=tazaki@sfc$(echo .)wide.ad.jp \
--cc=Kernel-team@fb$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=hannes@stressinduktion$(echo .)org \
--cc=kafai@fb$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=shengyong1@huawei$(echo .)com \
--cc=steffen.klassert@secunet$(echo .)com \
--cc=yangyingliang@huawei$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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