From: BlaisorBlade <bla...@ya...> - 2004-09-29 18:50:04
|
On Saturday 25 September 2004 22:15, pa...@bo... wrote: > Please, help ! > I have a big, big trouble..... > > The host server have the IP 209.123.8.163 > And the UML virtual server have the IP 66.246.187.16 > Well, I don't understand nothing about network, but I think that host ip > and uml ip are not compatible, or something that...... > I'm always create UMLs in other servers (but with all the IPs in same > class) Yes, from my understanding of the problem, this problem cannot happen with IPs in the same local network. > and I never had problems before, but in this machine, when I will > configure UML network, I never can't add the default route ! > See: > > UML # ifconfig eth0 66.246.187.16 netmask 255.255.255.255 up you must add, before, a "route" command to say how to reach the host, like this: route add -host 209.123.8.163 dev eth0 And after this, do route add default gw 209.123.8.163 Normally this is not needed, because (to use very non-technical terms) when, for instance, the UML ip is 192.168.0.2, and the host IP is 192.168.0.1, since the addresses begin "the same way", Linux knows they are next to each other. Here, instead, when you do "add default gw", he does not know how to contact the default gw. Ah, ok, you know a bit more than I thought, so: the "route add -host..." is not needed when the gateway is in the same local network (but note that actually, there is a route for the local network which is always added, but it's added automagically). > UML # route add default gw 209.123.8.163 > SIOCADDRT: Network is unreachable > UML # > The host OS, the host kernel version, the uml filesystem and the kernel > filesystem are the same that I use in other machines! > Only in this machine that I have this problem.... I guess/hope that you have this problem only here because you have such IPs only here. Bye -- Paolo Giarrusso, aka Blaisorblade Linux registered user n. 292729 |