ipfailover and PVE 2.0

[stef1777]

Hello!

With PVE 1.9, I can have an openvz container with an IP on a different subnet than the PVE node. This doesn't work with PVE 2.0.

Any idea of the problem?


Example (not the real IPs):

PVE node on eth0 : 10.10.0.1
IP 10.50.0.1 is an ipfailover mapped on the PVE node card eth0
The openvz container use 10.0.0.1 with venet

With PVE 1.9 I can access the openvz container but not with PVE 2.0 (no ping).

 

[stef1777]

I finally solved the problem.

The solution is easy, we simply need to edit /etc/vz/vz.conf file and change the 'NEIGHBOUR_DEVS=detect' to 'NEIGHBOUR_DEVS=all' (or eth0).

But not sure to deeply understand the problem. On PVE 1.9, NEIGHBOUR_DEVS=detect and the container work without this modification.