Ping (DUP!) response on container additionnals IPs

[sebalou84]

Hello,

I just realised that when I ping an additionnal IP present on a container I get this :

64 bytes from ADDITIONNAL_IP: icmp_req=3 ttl=55 time=4.37 ms (DUP!)

(ping test done from my local pc and from a remote server different from the proxmox)

Here is the /etc/network/interfaces conf :

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
        address CONTAINER_IP
        netmask 255.255.255.255
# --- BEGIN PVE ---
        post-up ip route add GATEWAY_IP dev eth0
        post-up ip route add default via GATEWAY_IP dev eth0
        pre-down ip route del default via GATEWAY_IP dev eth0
        pre-down ip route del GATEWAY_IP dev eth0
# --- END PVE ---

auto eth1
iface eth1 inet static
        address ADDITIONNAL_IP
        netmask 255.255.255.255

Clarification : initially I used the proxmox graphical interface (network tab) to add the additional IP with its virtual Mac.

Apart from this ping problem everything seems to be working fine though ...

I'm on PVE 5.4-6 and Debian 8.11 on the container.

Thanks

 

[Dominic]

Please update your installation to Proxmox VE 6. Better sooner than later. Proxmox VE 5 is at end of life. There are no more updates for it, including security updates. Use the upgrade guide in our Wiki.