New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Is it actually an OVH server or is it a SYS/KIMSUFI.
If it's an actual OVH machine and If you dont mind losing 3 IP's from the subnet it might be better to stuff it in Vrack otherwise you have do a load of routing hacks to deal with the out of subnet gateway and also register the MAC address of the VM's with OVH or their switches/routers will block it.
The gateway is the main IP of your system with .254 as the last octet.
Just configure bridge like you normally would.
it's OVH
I try configure like this but not working ? can you help me ? do you have experience in OVH Bridge ?
make sure to assign a virtual mac from OVH panel to each IP, and then assign each mac to corresponding VM.
I cannot help you in detail, but here is my network setup (debian/ubuntu based) on a OVH machine for a host-routed KVM setup (replace aa.bb.cc.dd etc. as appropriate. Also you may need some iptables/sysctl rules to make forwarding, proxyarp, etc. work):
Btw, as far as I know, OVH only supports IPv4 for assigning virtual macs. That's why I opted for routed hosting of the VMs.
You can do it in conventional way( tons of tutorials are available online ) for which will you have to free 3 IPv4 addresses out of assigned block.The other (OVH) recommended way is very simple, all you have to do for each failover is as follows:
Suppose main IP of your server is 1.1.1.1 & your IPv4 block is 2.2.2.1/30 then for example if you assign 2.2.2.1 to your first VPS the netmask & gateway will be
IP = 2.2.2.1
Netmask = 255.255.255.255
Gateway = 1.1.1.254 ( IP of your main server but last octet ending in 254 )
Similarly for 2.2.2.2
Netmask = 255.255.255.255
Gateway = 1.1.1.254 ( IP of your main server but last octet ending in 254 )
Remember you have to generate vMac address for each IP from OVH Manager & use that in the VPS. If a VPS has more than one IPv4, then every IPv4 assigned to that VPS must have same vMac.
Following is a sample configuration for bridge
/etc/sysconfig/network-scripts/ifcfg-eth0 should look like
etc/sysconfig/network-scripts/ifcfg-br0 should look like
+1 , that's totally it.
if you use debian/ubuntu instead you might want to use POINTOPOINT in /etc/network/interfaces of the guest, we covered that lately in one of the proxmox threads ;-)
That's why I said if it's an OVH machine and you don't mind wasting 3 IP's from the subnet just use Vrack and then it behaves like a normal subnet (They say not to use the last 3 as presumably they plan to run some kind of HSRP)