On 11/27/06, Jeff Dike <[EMAIL PROTECTED]> wrote: > On Mon, Nov 27, 2006 at 05:25:47PM +0200, Samuel Korpi wrote: > > UM1: ubd0=cow1,/home/samuel/src/uml/uml-fedora/FedoraCore5-AMD64-root_fs > > eth0=tuntap,tap0 eth1=mcast mem=256M umid=um1 con1=tty:/dev/tty > > > > UM2: ubd0=cow2,/home/samuel/src/uml/uml-fedora/FedoraCore5-AMD64-root_fs > > eth0=mcast mem=256M umid=um2 con1=tty:/dev/tty6 > > > > Why eth0 on one and eth1 on the other? > No particular reason. But as you can see, I configured eth0 on UM1 with tuntap, so it would provide a gateway to host and to outside network. I could have just as well but eth0=mcast for both (and eth1=tuntap,tap0 for UM1), but I didn't think that would make a difference.
> > > > Then I tried pinging one from the other, but nothing. What could be > > the problem? Guest kernel is 2.6.18. 'dmesg' shows nothing which > > could explain this, the mcast device should be configured ok AFAIK: > > > > Could something on the host affect how mcast works? > > It could, but there would be errors in dmesg and from ifconfig. I take it > the ifconfigs succeeded, and there's nothing new in dmesg? > Yep, that's right. Furthermore, both tuntap and daemon networking work just fine. And for my purposes those probably are sufficient. I was just pretty surprised that multicast didn't work, as I couldn't find anything wrong with my setup. /Samuel ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ User-mode-linux-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
