Recent content by dmul

  1. D

    OVH Failover Cant Access Containers

    It seems the answer is, if you created the LXC NIC with a /32, it will always fail back to that, no matter what you do. You need to remove the NIC, create a new one, and set the proper subnet mask at time of create. In this case, the original NIC was created with a /32, which was wrong. Delete...
  2. D

    OVH Failover Cant Access Containers

    root@pve:/etc/pve/nodes/pve/lxc# cat 101.conf arch: amd64 cores: 1 hostname: lxc2 memory: 2048 nameserver: 1.1.1.1 1.0.0.1 net0: name=eth0,bridge=vmbr0,firewall=1,gw=172.16.1.1,hwaddr=72:60:86:C9:1F:EB,ip=172.16.2.16/24,type=veth onboot: 1 ostype: ubuntu rootfs...
  3. D

    OVH Failover Cant Access Containers

    I am having a similar problem. I have narrowed it down to being an issue with the subnet mask. It seems to be forced to a /32 regardless of what IP I put in on the LXC container config. Example: Container config is: IP 172.16.1.16/24 GW 172.16.1.1 Container ifconfig shows a subnet mask of...