CT with 2 veth - Only one veth is up on boot

[vmware]

Hi all!

Have a similar issue like this one: https://forum.proxmox.com/threads/veth-does-not-come-up-anymore-on-several-lxc-containers.63317/

I created a brand new unprivileged Ubuntu CT with 2 veth: eth0, eth1. DHCP on for both. On CT boot only eth0 is up. eth1 is in DOWN state:

3: eth1@if136: <BROADCAST,MULTICAST> mtu 9000 qdisc noop state DOWN group default qlen 1000
link/ether 54:34:a0:f8:93:b8 brd ff:ff:ff:ff:ff:ff link-netnsid 0

If I manually bring up the veth and assign an IP address using the ip command, it will work OK. The CT runs Ubuntu 20.04, systemd version is 245.4-4ubuntu3.4

I have 4-5 existing CT that have the same dual veth config, and they all seem to work fine. This is the first one exhibiting this issue. Have tried moving the CT to another node in the Proxmox cluster, same issue.

Any help or guidance would be greatly appreciated! Thanks.

 

[Richard]

Hi all!

Have a similar issue like this one: https://forum.proxmox.com/threads/veth-does-not-come-up-anymore-on-several-lxc-containers.63317/

I created a brand new unprivileged Ubuntu CT with 2 veth: eth0, eth1. DHCP on for both. On CT boot only eth0 is up. eth1 is in DOWN state:

3: eth1@if136: <BROADCAST,MULTICAST> mtu 9000 qdisc noop state DOWN group default qlen 1000
link/ether 54:34:a0:f8:93:b8 brd ff:ff:ff:ff:ff:ff link-netnsid 0

If I manually bring up the veth and assign an IP address using the ip command, it will work OK. The CT runs Ubuntu 20.04, systemd version is 245.4-4ubuntu3.4

I have 4-5 existing CT that have the same dual veth config, and they all seem to work fine. This is the first one exhibiting this issue. Have tried moving the CT to another node in the Proxmox cluster, same issue.

Any help or guidance would be greatly appreciated! Thanks.

For further investigation it would be necessary to have lot at the containers configuration file as well as at the hosts IP configuration, e.g.

ip addr

in the host.