netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org, jani@ubuntu.com
Subject: Re: [Bugme-new] [Bug 12109] New: Multicast packets with TTL 0 sent out if not local listener
Date: Thu, 27 Nov 2008 09:34:12 -0800	[thread overview]
Message-ID: <20081127093412.9536e5cc.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-12109-10286@http.bugzilla.kernel.org/>


(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Thu, 27 Nov 2008 02:32:27 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=12109
> 
>            Summary: Multicast packets with TTL 0 sent out if not local
>                     listener
>            Product: Networking
>            Version: 2.5
>      KernelVersion: 2.6.27
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: IPV4
>         AssignedTo: shemminger@linux-foundation.org
>         ReportedBy: jani@ubuntu.com
> 
> 
> According to what I have read, setting the IP_MULTICAST_TTL option to 0 on a
> multicast sending socket should prevent it sending to the network, and be
> destined only for listeners on the local computer.
> 
> This only seems to work if there is a local listener on that particular group.
> If such a listener app is stopped other computers on the LAN get the messages,
> and tcpdump -v shows they have  TTL 0
> 
> I am not sure if this is intended behaviour but it is unexpected.
> 
> 


           reply	other threads:[~2008-11-27 17:34 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-12109-10286@http.bugzilla.kernel.org/>]

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=20081127093412.9536e5cc.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=jani@ubuntu.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).