From: Chris A. <uml...@na...> - 2004-04-02 12:55:59
|
> Have you checked that your gateway machine can ping the UML? It might be > that the returned ICMP packets aren't getting routed back to the UML. > Try adding a route on the gateway machine to explicity send the packets > back ("route add -host {UML IP} gw {host IP}") and possibly to the host > as well. i was able to ping the UML from another machine on the network, and was able to ssh into it. i can ssh and ping the uml from my machine 9.174.101.45, but cannot ping this address from within the UML. this leads me to think it is a routing problem on the host level... > Reading the bridging document you linked to at the start, it would seem > that eth0 and uml-conn0 should both have the address 0.0.0.0, rather > than a 192.168.1.* address. The uml-bridg interface gets a proper IP > address, and eth0 in the UML gets another proper IP address. this is correct - both uml-conn0 and eth0 on the host are set to 0.0.0.0 and promisc. eth0 in the uml has the proper IP. > Any particular reason you need to use bridging? I've got about a dozen > UMLs running on my server, each with their own 10.0.x.1 address, and it > seems to make setting up the networking much easier when they're > all on different networks (just a case of setting the right default route) i want each UML to have it's own IP and access to and from the outside world, as if they were a normal host. what's the other way of achieving this? thanks chris |