[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070515.134540.45873471.davem@davemloft.net>
Date: Tue, 15 May 2007 13:45:40 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: akepner@....com
Cc: netdev@...r.kernel.org, arenaud@....com
Subject: Re: [PATCH] don't put multicasts with mc_ttl=0 on the wire
From: akepner@....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@....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;
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists