From: stian@nixia.no
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Cc: user-mode-linux-devel
<user-mode-linux-devel@lists.sourceforge.net>,
netdev@oss.sgi.com
Subject: Re: [uml-devel] multicast on loopback: mcast networking at the cottage
Date: Mon, 25 Jul 2005 19:20:57 +0200 (CEST) [thread overview]
Message-ID: <42036.85.166.82.153.1122312057.squirrel@85.166.82.153> (raw)
In-Reply-To: <6048.1122248129@marajade.sandelman.ottawa.on.ca>
> I suspect that for people who want to do multicast between hosts on an
> actual wire won't want to have just a route to lo, they may want a route
> for 224.0.0.0/4 on all of their interfaces. Maybe that should be
> automatic?
>
> I think that applications that are multicast aware are supposed to
> figure out which interfaces that they want to bind to anyway, so they
> should not be confused by the multiple routes.
If I remember things right (I might be wrong here):
ipv6 does this automatically, so should ipv4 have done too if multicast is
supported on a device. Multicast aware programs should always bind to a
device, or broadcast on all devices for discovery.
This is not uml-specific, but vanilla kernel. Some distroes add
multicast-routing for ipv4 during init scripts.
Stian
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2005-07-25 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-24 23:35 [uml-devel] multicast on loopback: mcast networking at the cottage Michael Richardson
2005-07-25 17:20 ` stian [this message]
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=42036.85.166.82.153.1122312057.squirrel@85.166.82.153 \
--to=stian@nixia.no \
--cc=mcr@sandelman.ottawa.on.ca \
--cc=netdev@oss.sgi.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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