From: David Miller <davem@davemloft.net>
To: nicolas.dichtel@6wind.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] ipv4/ipv6: check hop limit field on input
Date: Tue, 02 Jun 2009 02:37:51 -0700 (PDT) [thread overview]
Message-ID: <20090602.023751.68661975.davem@davemloft.net> (raw)
In-Reply-To: <4A24F29D.1090106@dev.6wind.com>
From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Date: Tue, 02 Jun 2009 11:36:29 +0200
> David Miller wrote:
>> From: Nicolas Dichtel <nicolas.dichtel@dev.6wind.com>
>> Date: Mon, 01 Jun 2009 17:13:43 +0200
>>
>>> RFC indicates that a router must drop the packet if this field is 0.
>> It only must do this when executing the forwarding function. It's an
>> egress check, not an ingress one.
> In my understanding, it can be on input to:
> RFC4443 Section 3.3:
> If a router receives a packet with a Hop Limit of zero, or if a
> router decrements a packet's Hop Limit to zero, it MUST discard the
> packet and originate an ICMPv6 Time Exceeded message with Code 0 to
> the source of the packet.
I think this was unintentional.
Usage of zero TTL by multicast applications is very well established.
Running such an application on a router should work as well.
prev parent reply other threads:[~2009-06-02 9:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 15:13 [PATCH] ipv4/ipv6: check hop limit field on input Nicolas Dichtel
2009-06-01 16:19 ` Florian Westphal
2009-06-01 16:49 ` Nicolas Dichtel
2009-06-01 17:13 ` Florian Westphal
2009-06-02 9:30 ` Nicolas Dichtel
2009-06-01 18:43 ` Eric Dumazet
2009-06-01 18:55 ` Brian Haley
2009-06-02 1:54 ` John Dykstra
2009-06-02 2:02 ` David Miller
2009-06-02 9:22 ` John Dykstra
2009-06-02 9:32 ` David Miller
2009-06-02 9:35 ` Nicolas Dichtel
2009-06-02 9:30 ` Nicolas Dichtel
2009-06-02 9:30 ` Nicolas Dichtel
2009-06-02 2:04 ` David Miller
2009-06-02 5:31 ` Eric Dumazet
2009-06-02 5:43 ` David Miller
2009-06-02 9:36 ` Nicolas Dichtel
2009-06-02 9:37 ` David Miller [this message]
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=20090602.023751.68661975.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.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;
as well as URLs for NNTP newsgroup(s).