From: Yang Yingliang <yangyingliang@huawei.com>
To: netdev <netdev@vger.kernel.org>, "David S. Miller" <davem@davemloft.net>
Subject: A problem about ICMP packet-too-big message handler
Date: Tue, 27 Jan 2015 20:58:53 +0800 [thread overview]
Message-ID: <54C78B8D.1070104@huawei.com> (raw)
Hi,
My kernel is 3.10 LTS.
I got a problem here about handling ICMP packet-too-big message.
Before sending a packet-too-big packet :
# ip -6 route list table local
local ::1 dev lo metric 0
local fe80:: dev lo metric 0
local fe80:: dev lo metric 0
local fe80:: dev lo metric 0
local fe80:: dev lo metric 0
local fe80:: dev lo metric 0
local fe80:: dev lo metric 0
local fe80::1 dev lo metric 0 //It does not have expire value
local fe80::200:ff:fe00:0 dev lo metric 0
local fe80::200:ff:fe00:0 dev lo metric 0
local fe80::200:ff:fe00:0 dev lo metric 0
local fe80::200:ff:fe00:0 dev lo metric 0
local fe80::200:ff:fe00:2 dev lo metric 0
local fe80::5054:ff:fe12:3456 dev lo metric 0
After sending a packet-too-big packet
ip -6 route list table local
local ::1 dev lo metric 0
local fe80:: dev lo metric 0
local fe80:: dev lo metric 0
local fe80:: dev lo metric 0
local fe80:: dev lo metric 0
local fe80:: dev lo metric 0
local fe80:: dev lo metric 0
local fe80::1 dev lo metric 0 expires _597_ //It has expire value
local fe80::200:ff:fe00:0 dev lo metric 0
local fe80::200:ff:fe00:0 dev lo metric 0
local fe80::200:ff:fe00:0 dev lo metric 0
local fe80::200:ff:fe00:0 dev lo metric 0
local fe80::200:ff:fe00:2 dev lo metric 0
local fe80::5054:ff:fe12:3456 dev lo metric 0
When time is up, I can't ping fe80::1 .
Is it ok or a bug ?
Regards,
Yang
next reply other threads:[~2015-01-27 12:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 12:58 Yang Yingliang [this message]
2015-01-28 5:19 ` A problem about ICMP packet-too-big message handler Martin Lau
2015-01-28 6:46 ` Yang Yingliang
2015-01-28 12:45 ` Eric Dumazet
2015-01-29 1:04 ` Yang Yingliang
2015-01-28 8:42 ` Hannes Frederic Sowa
2015-01-28 10:07 ` Yang Yingliang
2015-01-28 12:10 ` Steffen Klassert
2015-01-28 12:11 ` [PATCH RFC 1/2] ipv6: Fix after pmtu events dissapearing host routes Steffen Klassert
2015-01-29 10:26 ` Hannes Frederic Sowa
2015-01-29 10:44 ` Steffen Klassert
2015-02-05 23:56 ` Martin Lau
2015-02-09 10:26 ` Steffen Klassert
2015-03-09 9:00 ` Steffen Klassert
2015-01-28 12:12 ` [PATCH RFC 2/2] ipv6: Extend the route lookups to low priority metrics Steffen Klassert
2015-01-29 3:16 ` A problem about ICMP packet-too-big message handler Yang Yingliang
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=54C78B8D.1070104@huawei.com \
--to=yangyingliang@huawei.com \
--cc=davem@davemloft.net \
--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;
as well as URLs for NNTP newsgroup(s).