LXC Network issues after upgrade from 5.2 to 5.4-2

[yena]

Hello,
after upgrading to last 5 versione all LXC network stop working !!

pveversion -V
proxmox-ve: 5.4-2 (running kernel: 4.15.18-21-pve)
pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec)
pve-kernel-4.15: 5.4-9
pve-kernel-4.15.18-21-pve: 4.15.18-48
pve-kernel-4.15.18-5-pve: 4.15.18-24
pve-kernel-4.13.13-2-pve: 4.13.13-33
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-55
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-38
pve-container: 2.0-40
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-7
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
pve-zsync: 1.7-4
qemu-server: 5.0-54
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2

Thanks!

 

[t.lamprecht]

after upgrading to last 5 versione all LXC network stop working !!

Works here so maybe you add some more information of your setup, a problematic container config, what network do you even have (bridged, OVS, ..), do you still see network devices in the CT, and they just have no address (check your DHCP), ...

AFAICT, there's at least no general problem.

 

[yena]

Works here so maybe you add some more information of your setup, a problematic container config, what network do you even have (bridged, OVS, ..), do you still see network devices in the CT, and they just have no address (check your DHCP), ...

AFAICT, there's at least no general problem.

I Solved changing all MAC ADDRESS on LXC container... i notiche that inside containers i could ping the gateway.. but not outside .. changing MAC i think have done somithing on router arp cache ...