All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yang Yingliang <yangyingliang@huawei.com>
To: Martin Lau <kafai@fb.com>
Cc: netdev <netdev@vger.kernel.org>, "David S. Miller" <davem@davemloft.net>
Subject: Re: A problem about ICMP packet-too-big message handler
Date: Wed, 28 Jan 2015 14:46:43 +0800	[thread overview]
Message-ID: <54C885D3.70808@huawei.com> (raw)
In-Reply-To: <20150128051929.GA3369592@devbig242.prn2.facebook.com>

On 2015/1/28 13:19, Martin Lau wrote:
> On Tue, Jan 27, 2015 at 08:58:53PM +0800, Yang Yingliang wrote:
>> 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 :
> The expires should be set by the host _receiving_ the icmpv6 too-big.
> 
> Can you spell out some details of the outgoing icmpv6 too-big packet?
> like, the src/dst ip of the icmpv6 and the original ip packet that triggered the
> too-big.
> 

I don't send too-big packet to trigger the err handling.

I just only send a ICMPv6 packet which type is ICMPV6_PKT_TOOBIG.

  reply	other threads:[~2015-01-28  6:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27 12:58 A problem about ICMP packet-too-big message handler Yang Yingliang
2015-01-28  5:19 ` Martin Lau
2015-01-28  6:46   ` Yang Yingliang [this message]
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=54C885D3.70808@huawei.com \
    --to=yangyingliang@huawei.com \
    --cc=davem@davemloft.net \
    --cc=kafai@fb.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.