Myatu
20-11-2011, 11:24
Originally Posted by airwalker
When you install Ubuntu, or any other Linux distro for that matter, you usually are only given the option to perform that first part. So you'd enter the failover IP, netmask and gateway.
Whilst this will create a default route/path, telling Linux all network traffic has to go through that gateway, Linux does not automatically assume that the gateway is on "eth0" (as Windows would). So it doesn't know where the gateway is - and of course will give you grief now
I'm not sure how you're installing the distro. For within VM's, you need to use the normal ISO's as provided by the Linux distros (some also have pre-made VM's - and Proxmox provides them too).
If they're installed through a VNC-like interface, then simply continue without configuring the network details. The re-boot at the end of the install will take a bit longer than usual, as it'll try to find a DHCP server, but it'll continue to where you can login. That's where you can open a terminal window (if you're using a desktop distro) or use the CLI, and edit /etc/network/interfaces (in Debian or Ubuntu) and modify it according to the guide you've read earlier -- you then have a chance to add the route/path with the "post-up" and "post-down" portions.
Now, if this keeps giving you grief, you can also try an alternative, which is to use an Class A, B or C private IP address for the VM, say 192.168.0.1 and give your bridge an IP of say, 192.168.0.254 (netmask 255.255.0.0 or 255.255.255.0 for that). On Virtualisation SW like Proxmox, you could then access the VM from the host by its private IP address - including SSH.