From: David Miller <davem@davemloft.net>
To: john.dykstra1@gmail.com
Cc: brian.haley@hp.com, dada1@cosmosbay.com,
nicolas.dichtel@6wind.com, fw@strlen.de, netdev@vger.kernel.org
Subject: Re: [PATCH] ipv4/ipv6: check hop limit field on input
Date: Mon, 01 Jun 2009 19:02:28 -0700 (PDT) [thread overview]
Message-ID: <20090601.190228.75178984.davem@davemloft.net> (raw)
In-Reply-To: <1243907646.15854.16.camel@merlyn>
From: John Dykstra <john.dykstra1@gmail.com>
Date: Mon, 01 Jun 2009 20:54:06 -0500
> On Mon, 2009-06-01 at 14:55 -0400, Brian Haley wrote:
>> I don't know if that difference
>> in behavior is desired. Do we know how any other OSes behave?
>
> FWIW, the random BSD flavors I have on hand all check hop limit when
> forwarding, but not when processing local ingress traffic.
>
> Also FWIW, as I remember, the TAHI tests only check hop limit behavior
> on forwarded traffic.
And this is the behavior that makes the most sense to me.
The local system is "accounted for" in the hop limit by the previous
hop system. No other behavior makes any sense.
And I even remember there are applications that use multicast and
a hop limit of zero explicitly to keep application traffic only on
the local subnet. So any change like that proposed could break
things.
next prev parent reply other threads:[~2009-06-02 2:02 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 [this message]
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
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=20090601.190228.75178984.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brian.haley@hp.com \
--cc=dada1@cosmosbay.com \
--cc=fw@strlen.de \
--cc=john.dykstra1@gmail.com \
--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).