Hi all.
The Scale servers from OVH cannot use bridge mode. we need to use router mode instead.
Using this guide https://pve.proxmox.com/wiki/Network_Configuration#_routed_configuration we can configure and access our server:
But when we create de CT, only bridge is available to select. If we create the CT and do pct enter, it can't access to internet.
Then, we change network config as OVH describes here https://docs.ovh.com/us/en/dedicated/proxmox-network-hg-scale/
Result: No access to our server
Then, change this config to forze using static ip:
Same result, we cannot access to our server
The Scale servers from OVH cannot use bridge mode. we need to use router mode instead.
Using this guide https://pve.proxmox.com/wiki/Network_Configuration#_routed_configuration we can configure and access our server:
Code:
auto lo
iface lo inet loopback
iface enp193s0f0np0 inet manual
auto enp193s0f0np0
iface enp193s0f0np0 inet static
address 135.XXX:XXX.XXX/32 ----> Server IP
gateway 100.XXX.0.1. ------> Server gateway
hwaddress XX:XX:XX:XX:XX
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up echo 1 > /proc/sys/net/ipv4/conf/eno1/proxy_arp
auto vmbr0
iface vmbr0 inet static
address 51.XXX.XXX.XXX/28 ---> Failover to attach to vm
bridge-ports none
bridge-stp off
bridge-fd 0
But when we create de CT, only bridge is available to select. If we create the CT and do pct enter, it can't access to internet.
Then, we change network config as OVH describes here https://docs.ovh.com/us/en/dedicated/proxmox-network-hg-scale/
Code:
auto lo
iface lo inet loopback
auto enp193s0f0np0
iface enp193s0f0np0 inet manual
auto enp193s0f1np1
iface enp193s0f1np1 inet manual
auto enp133s0f0np0
iface enp133s0f0np0 inet manual
auto enp133s0f1np1
iface enp133s0f1np1 inet manual
auto bond0
iface bond0 inet dhcp
bond-slaves enp193s0f0np0 enp193s0f1np1
bond-miimon 100
bond-mode 802.3ad
post-up echo 1 > /proc/sys/net/ipv4/conf/bond0/proxy_arp
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
auto vmbr0
iface vmbr0 inet static
address 192.168.0.1
netmask 255.255.255.255
bridge-ports none
bridge-stp off
bridge-fd 0
post-up ip route add XXX.XXX.XXX.XXX/32 dev vmbr0. ------> Ip failover
Result: No access to our server
Then, change this config to forze using static ip:
Code:
auto lo
iface lo inet loopback
auto enp193s0f0np0
iface enp193s0f0np0 inet manual
auto enp193s0f1np1
iface enp193s0f1np1 inet manual
auto enp133s0f0np0
iface enp133s0f0np0 inet manual
auto enp133s0f1np1
iface enp133s0f1np1 inet manual
auto bond0
iface bond0 inet static
address 135.XXX:XXX.XXX/32 ----> Server IP
gateway 100.XXX.0.1. ------> Server gateway
hwaddress XX:XX:XX:XX:XX
bond-slaves enp193s0f0np0 enp193s0f1np1
bond-miimon 100
bond-mode 802.3ad
post-up echo 1 > /proc/sys/net/ipv4/conf/bond0/proxy_arp
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
auto vmbr0
iface vmbr0 inet static
address 192.168.0.1
netmask 255.255.255.255
bridge-ports none
bridge-stp off
bridge-fd 0
post-up ip route add 51.254.144.227/32 dev vmbr0
Same result, we cannot access to our server