netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: akepner@sgi.com
Cc: netdev@vger.kernel.org, arenaud@sgi.com
Subject: Re: [PATCH] don't put multicasts with mc_ttl=0 on the wire
Date: Tue, 15 May 2007 13:45:40 -0700 (PDT)	[thread overview]
Message-ID: <20070515.134540.45873471.davem@davemloft.net> (raw)
In-Reply-To: <20070515195602.GK19036@sgi.com>

From: akepner@sgi.com
Date: Tue, 15 May 2007 12:56:02 -0700

> A colleague of mine found that multicasts with a ttl of 0
> can be sent on the wire. This happens if the sender doesn't
> belong to the destination multicast group.
> 
> With the following the multicast ttl is respected whether
> or not the sender belongs to the destination multicast group.
> 
> Signed-off-by: Arthur Kepner <akepner@sgi.com>

This is actually used by some things if I remember correctly.
See this command and code in net/ipv4/route.c:

			/* Special hack: user can direct multicasts
			   and limited broadcast via necessary interface
			   without fiddling with IP_MULTICAST_IF or IP_PKTINFO.
			   This hack is not just for fun, it allows
			   vic,vat and friends to work.
			   They bind socket to loopback, set ttl to zero
			   and expect that it will work.
			   From the viewpoint of routing cache they are broken,
			   because we are not allowed to build multicast path
			   with loopback source addr (look, routing cache
			   cannot know, that ttl is zero, so that packet
			   will not leave this host and route is valid).
			   Luckily, this hack is good workaround.
			 */

			fl.oif = dev_out->ifindex;
			goto make_route;

  reply	other threads:[~2007-05-15 20:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 19:56 [PATCH] don't put multicasts with mc_ttl=0 on the wire akepner
2007-05-15 20:45 ` David Miller [this message]
2007-05-15 21:40 ` David Stevens

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=20070515.134540.45873471.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akepner@sgi.com \
    --cc=arenaud@sgi.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 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).