From: John Dykstra <john.dykstra1@gmail.com>
To: David Miller <davem@davemloft.net>
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: Tue, 02 Jun 2009 09:22:10 +0000 [thread overview]
Message-ID: <1243934530.8439.4.camel@Maple> (raw)
In-Reply-To: <20090601.190228.75178984.davem@davemloft.net>
On Mon, 2009-06-01 at 19:02 -0700, David Miller wrote:
> 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.
Are you thinking of multicast apps that explicitly set a hop limit, or Multicast
Listener Discovery? The hop limit specified for MLDv2 messages is one,
not zero.
-- John
next prev parent reply other threads:[~2009-06-02 9:28 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 [this message]
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=1243934530.8439.4.camel@Maple \
--to=john.dykstra1@gmail.com \
--cc=brian.haley@hp.com \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--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).