OVH Community, your new community space.

Failover IP / MAC on bridged VM tip...


DigitalDaz
28-01-2010, 20:40
For VM's use the failover or RIPE IP of the virtual machine as the gateway with a 32bit subnet mask.

eg

ip 1.2.3.4
mask 255.255.255.255
gateway 1.2.3.4

pdu
28-01-2010, 16:20
re above, failover IPs don't have a .254 gateway because they are routed, I know this because one of my failover IP addresses actually ends .254 itself, so please, don't do this, or you'll potentially end up throwing traffic at other unsuspecting ovh customers

kenzacm
24-01-2010, 09:18
yep when i do that the Virtual Machine still cannot connect to the network

Myatu
24-01-2010, 04:42
Re: "The Gateway of your physical machine".

To try make that as simple as possible: You replace whatever comes after the last dot/period of your server's IP with 254. The server IP is the one you received when you first got your welcome e-mail from OVH and use to access SSH and other things; Not your failover IP!

So if your server's IP is 91.2.3.4, replace "4" so it becomes 91.1.2.3.254. If it's 87.11.22.33, it becomes 87.11.22.254, and so on.

That IP is your gateway.

kenzacm
24-01-2010, 04:15
The Bit:
the Gateway of your physical machine
confused the hell outta me.

i decided to go with windows and even following the guids i only get VM to Host Connectivity!!!!

Can anyone perhaps help?

Myatu
23-01-2010, 16:49
After some digging, OVH seems to have a well hidden article about bridging VMs (basically the same what I had to do with the "add route" vs. "gateway"). It includes details for Centos, kenzacm: http://help.ovh.co.uk/BridgeClient

kenzacm
22-01-2010, 00:03
Hi Guys,
im having a major problem with the IP's etc. in Citrix XENServer can anyone post a config for CENTOS that WILL work.

The VM's can ping the physical server but nothing else.

Cheers

derchris
21-01-2010, 14:32
Now that Bridge mode seems to work, I should give Xen and co another try.
Thanks Myatu for the heads up

IainK
21-01-2010, 13:31
Ahh. It works on VMware and Xen Darn proxmox being difficult

Myatu
21-01-2010, 13:28
No, that wont' work, that was my point Not on Proxmox full KVMs at least!

IainK
21-01-2010, 13:11
Or you can simply use the following:
iface eth0 inet auto
address 91.2.3.4
netmask 255.255.255.255
gateway 91.2.3.4
on either routed or bridged mode.

Myatu
21-01-2010, 13:07
Just in case you're having trouble with the Failover IP / MAC on a bridged VM (Proxmox, VMWare, Xen): Don't specify the gateway but use routing!

Incorrect:
Code:
iface eth0 inet auto
    address 91.2.3.4
    netmask 255.255.255.255
    gateway 91.1.2.254
Correct:
Code:
iface eth0 inet auto
    address 91.2.3.4
    netmask 255.255.255.255
    post-up route add 91.1.2.254 dev eth0
    post-up route default gw 91.1.2.254
Otherwise the OS gets confused at how you can get 91.2.3.4/32 on a completely different subnet... And you'll be wondering why everything comes back as "Network is Unreachable". Tsk, tsk!

By the way, OVH has Proxmox 1.5 available (even though it says 1.4). Toying with it right now - if you keep the above in mind, it works like a charm!