Search results

I have the following network config auto lo iface lo inet loopback auto enp193s0f0 iface enp193s0f0 inet manual auto enp133s0f0 iface enp133s0f0 inet manual auto enp133s0f1 iface enp133s0f1 inet manual auto enp193s0f1 iface enp193s0f1 inet manual iface enp9s0f3u2u2c2 inet manual...

It looks like OVH new Scale range does networking differently. To get the IPv4 block I have added post-up ip route add IPBLOCK/27 dev vmbr0 post-up echo 1 >/proc/sys/net/ipv4/ip_forward and then used the Gateway 100.64.0.1 rather than the standard node IP (replacing D class field with...

I have it working now. Looks like you have to add the following for new server ranges in /etc/network/interfaces vmbr0 part post-up ip route add 198.244.139.xxx/32 dev vmbr0 post-up echo 1 >/proc/sys/net/ipv4/ip_forward

Thanks for the info. Here is how I normally get it working with OVH auto lo iface lo inet loopback iface eth0 inet dhcp iface eth1 inet dhcp iface eth2 inet dhcp iface enp5s0f0 inet manual iface enp5s0f1 inet manual iface enp7s0f3u2u2c2 inet manual auto vmbr0 iface vmbr0 inet...

Attemping to use 51.195.234.xxx (nodes public IP) with enp193s0f1 fails it can only be used with enp193s0f0 - Additional IPs do work with enp193s0f1 when I do not set any virtual mac (not in a VM through vmbr) IPs trough vrack is not an option as the first/last IP of each block is unusable

Thank you for the reply but from what I can see this has not changed anything. warning: bond0: attribute bond-min-links is set to '0' Shows but 51.195.234.xxx is working (same as before). Some more config files have been added above for DHCP

I recently got my new OVH Scale range server which comes with redundant network (2xpublic 2xvrack) and can't get the virtual machines network to work with or without virtual MACs Below are the network settings I am not sure how to set it up correctly to get vmbr0 for the VMs working...