> 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
