Le Samedi, 9 Février 2008 14:41:09 -0500, lanas <[EMAIL PROTECTED]> a écrit :
> Does this general understanding of the basic UML networking makes > sense: the UMLs do not communicate between each other. They > communicate with their tun/tap devices which have instances on the > host. On the other hand these host instances do communicate > together. If this is right, I do not see how multicast would work if > no additional interface is created on the host. But then I might be > wrong. OK, it's explained later in the book. mcast uses a form of IPC. What I'd like to attain, is a virtual UML network for testing networking situations. With TUN/TAP I've seen that bringing down the ethx interfaces of a routing UML2 will not affect UML1 and UML3 and both 1 and 3 will be able to ping themselves even though the UML2 router in the middle that was making the forwarding has seen both its ethx interfaces put down. In such a case the host interfaces/routing have to be adjusted. While this could be a viable solution, it can be error prone when testing anything more complex than a simple VRRP setup. I hope that with multicast - once it works - I will be able to only deal with UML networking configs to simulate network setups and failures. Cheers, Al ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ User-mode-linux-user mailing list User-mode-linux-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
