[SOLVED] SOLVED: Mac address issue / NetworkManager

M

mangelot

Member
Apr 7, 2021
16
1
8
44
Hi,

I have the following problem on te latest proxmox version 7.2-4

I have lxc containers with ipv4 (eth0) and ipv6 (eth1) both bridged to vmbr0
Everytime when I reboot an lxc container the ipv6 isn't working inside the container,
I need to manually remove the mac address from the network settings in Proxmox gui (set it to auto) and save,
after that the ipv6 is working without any problem inside the container.

This issue is since I use version 7.x, what could caused this weird behaviour?

regards, Marco
 
Hi,

is your firewall enabled? How are your containers receiving/generating their IPv6 addresses?
 
Hi,

Thanks for your response..
Yes the firewall is enabled. containers are running Almalinux (migrated from Centos8)
network is setup from within Proxmox Gui like screenshot below.

proxmox network.png

Settings inside one of the LXC containers (masked ip-address and changed search domain)

/etc/resolv.conf

# Generated by NetworkManager search domain.com nameserver 1.1.1.1 nameserver 8.8.4.4

/etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0 ONBOOT=yes UUID=321f5718-e75a-11ec-8ed9-90b11c141857 BOOTPROTO=none IPADDR=xxx.xxx.25.155 NETMASK=255.255.255.0 GATEWAY=xxx.xxx.25.1 DNS1=1.1.1.1 DNS2=8.8.4.4 DNS3=2606:4700:4700::1111 DOMAIN=domain.com

/etc/sysconfig/network-scripts/ifcfg-eth1
DEVICE=eth1 ONBOOT=yes UUID=321fe76e-e75a-11ec-8ed9-90b11c141857 BOOTPROTO=none IPADDR=xxx.xxx.25.156 NETMASK=255.255.255.0 GATEWAY=xxx.xxx.25.1 DNS1=1.1.1.1 DNS2=8.8.4.4 DNS3=2606:4700:4700::1111 DOMAIN=domain.com

/etc/sysconfig/network-scripts/ifcfg-eth2
DEVICE=eth2 ONBOOT=yes UUID=32203020-e75a-11ec-8ed9-90b11c141857 BOOTPROTO=none IPV6INIT=yes IPV6ADDR=xxxx:xxxx:x:xx:25::156/128 DNS1=1.1.1.1 DNS2=8.8.4.4 DNS3=2606:4700:4700::1111 DOMAIN=domain.com

/etc/sysconfig/network-scripts/ifcfg-eth3
DEVICE=eth2 ONBOOT=yes UUID=32203020-e75a-11ec-8ed9-90b11c141857 BOOTPROTO=none IPV6INIT=yes IPV6ADDR=xxxx:xxxx:x:xx:25::156/128 DNS1=1.1.1.1 DNS2=8.8.4.4 DNS3=2606:4700:4700::1111 DOMAIN=domain.com

/etc/sysconfig/network-scripts/route6-eth2
# --- BEGIN PVE --- xxxx:xxxx:x:xx::1 dev eth2 default via xxxx:xxxx:x:xx::1 dev eth2 # --- END PVE ---


/etc/sysconfig/network-scripts/route6-eth3
# --- BEGIN PVE --- xxxx:xxxx:x:xx::1 dev eth2 default via xxxx:xxxx:x:xx::1 dev eth2 # --- END PVE ---


eth0 and eth1 have no issues, using ipv4.
eth2 and eth3 have the issue, using ipv6.


nmcli randomly shows:

eth2: connecting (getting IP configuration) to System eth2 "eth2" ethernet (veth), 4A:9F:FC:E9:77:37, sw, mtu 1500 ip6 default eth3: connecting (getting IP configuration) to System eth3 "eth3" ethernet (veth), 2A:0E:FF:6E:B3:A3, sw, mtu 1500

and ping is working without problems (ping6 -c4 ipv6.google.com)


nmcli also randomly shows (some time later)

eth2: disconnected "eth2" 1 connection available ethernet (veth), 4A:9F:FC:E9:77:37, sw, mtu 1500 eth3: disconnected "eth3" 1 connection available ethernet (veth), 2A:0E:FF:6E:B3:A3, sw, mtu 1500

and ping is not working anymore (ping6 -c4 ipv6.google.com) resulting in: connect: Network is unreachable

/var/log/messages

Code: 
Jun  9 08:29:11 srv201 NetworkManager[2897]: <info>  [1654756151.8962] device (eth2): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Jun  9 08:29:11 srv201 NetworkManager[2897]: <warn>  [1654756151.8968] device (eth2): Activation: failed for connection 'System eth2'
Jun  9 08:29:11 srv201 NetworkManager[2897]: <info>  [1654756151.8970] device (eth2): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun  9 08:29:11 srv201 NetworkManager[2897]: <info>  [1654756151.9016] policy: set 'System eth3' (eth3) as default for IPv6 routing and DNS
Jun  9 08:29:11 srv201 NetworkManager[2897]: <info>  [1654756151.9044] policy: auto-activating connection 'System eth2' (32203020-e75a-11ec-8ed9-90b11c141857)
Jun  9 08:29:11 srv201 NetworkManager[2897]: <info>  [1654756151.9051] device (eth2): Activation: starting connection 'System eth2' (32203020-e75a-11ec-8ed9-90b11c141857)
Jun  9 08:29:11 srv201 NetworkManager[2897]: <info>  [1654756151.9052] device (eth2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun  9 08:29:11 srv201 NetworkManager[2897]: <info>  [1654756151.9056] device (eth2): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun  9 08:29:11 srv201 NetworkManager[2897]: <info>  [1654756151.9061] device (eth2): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jun  9 08:29:12 srv201 NetworkManager[2897]: <info>  [1654756152.4391] device (eth3): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Jun  9 08:29:12 srv201 NetworkManager[2897]: <warn>  [1654756152.4397] device (eth3): Activation: failed for connection 'System eth3'
Jun  9 08:29:12 srv201 NetworkManager[2897]: <info>  [1654756152.4399] device (eth3): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun  9 08:29:12 srv201 NetworkManager[2897]: <info>  [1654756152.4442] policy: set 'System eth2' (eth2) as default for IPv6 routing and DNS
Jun  9 08:29:12 srv201 NetworkManager[2897]: <info>  [1654756152.4474] policy: auto-activating connection 'System eth3' (322174a8-e75a-11ec-8ed9-90b11c141857)
Jun  9 08:29:12 srv201 NetworkManager[2897]: <info>  [1654756152.4481] device (eth3): Activation: starting connection 'System eth3' (322174a8-e75a-11ec-8ed9-90b11c141857)
Jun  9 08:29:12 srv201 NetworkManager[2897]: <info>  [1654756152.4482] device (eth3): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun  9 08:29:12 srv201 NetworkManager[2897]: <info>  [1654756152.4485] device (eth3): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun  9 08:29:12 srv201 NetworkManager[2897]: <info>  [1654756152.4489] device (eth3): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jun  9 08:29:43 srv201 NetworkManager[2897]: <info>  [1654756183.5754] device (eth2): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Jun  9 08:29:43 srv201 NetworkManager[2897]: <warn>  [1654756183.5760] device (eth2): Activation: failed for connection 'System eth2'
Jun  9 08:29:43 srv201 NetworkManager[2897]: <info>  [1654756183.5762] device (eth2): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun  9 08:29:43 srv201 NetworkManager[2897]: <info>  [1654756183.5808] policy: set 'System eth3' (eth3) as default for IPv6 routing and DNS
Jun  9 08:29:44 srv201 NetworkManager[2897]: <info>  [1654756184.0559] device (eth3): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Jun  9 08:29:44 srv201 NetworkManager[2897]: <warn>  [1654756184.0565] device (eth3): Activation: failed for connection 'System eth3'
Jun  9 08:29:44 srv201 NetworkManager[2897]: <info>  [1654756184.0568] device (eth3): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
 
looks like it can't configure the interface from the errors. I don't see a reason why a firewall roule outside of the container should change that.

Can you show the output of ip a to see if the iP is there when it is working?
 
When the CT is running, and I change the Mac addresses on the Proxmox Host GUI
the ipv6 network is back up according to nmcli and eth 2 and eth3 can ping6 to ipv6.google.com.


After reboot of the LXC CT nmcli shows for eth2 and eth3, and the ipv6 connection is gone.

eth2: connecting (getting IP configuration) to System eth2 "eth2" ethernet (veth), FE:AE:43:94:8C:A8, sw, mtu 1500 ip6 default eth3: connecting (getting IP configuration) to System eth3 "eth3" ethernet (veth), 5E:0C:4C:81:A0:FD, sw, mtu 1500


after that i tryed command 'ip a' with following output:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0@if521: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether e6:ca:93:0b:5f:fa brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet xxx.xxx.xx.155/24 brd xxx.xxx.xx.255 scope global noprefixroute eth0 valid_lft forever preferred_lft forever inet6 fe80::e4ca:93ff:fe0b:5ffa/64 scope link valid_lft forever preferred_lft forever 3: eth1@if525: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 2a:1f:9a:c1:08:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet xxx.xxx.xx.156/24 brd xxx.xxx.xx.255 scope global noprefixroute eth1 valid_lft forever preferred_lft forever inet6 fe80::281f:9aff:fec1:889/64 scope link valid_lft forever preferred_lft forever 4: eth3@if529: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 5e:0c:4c:81:a0:fd brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 xxxx:xxxx:x:xx:25::155/128 scope global noprefixroute valid_lft forever preferred_lft forever inet6 fe80::5c0c:4cff:fe81:a0fd/64 scope link noprefixroute valid_lft forever preferred_lft forever 5: eth2@if533: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether fe:ae:43:94:8c:a8 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 xxxx:xxxx:x:xx:25::156/128 scope global noprefixroute valid_lft forever preferred_lft forever inet6 fe80::fcae:43ff:fe94:8ca8/64 scope link noprefixroute valid_lft forever preferred_lft forever


P.s. Cannot set ipv6 on eth0 and eth1 because of Vlan (25) settings
 
Did you try to see if this same network setup has problems with a for example debian container as well? To me, it looks a bit like something funny is going on with network management inside the container.
 
I solved the issue for now, seems that proxmox is changing some settings in /etc/sysconfig/network-scripts/ifcfg-xxx files

#nmcli
Ipv4 is working on eth0 and eth1, ipv6 isn't working on eth2 and eth3.

#nm-tui
Setup all interfaces to manual configuration or disabled interface for ipv4 and ipv6 if not needed.

#systemctl restart NetworkManager.service #nmcli
Everything is now green and working on all 4 interfaces ;-)
rebooted CT throught Proxmox GUI
and after reboot

#nmcli
ipv4 is working on eth0 and eth1, ipv6 isn't working on eth2 and eth3.

:-( again same issue

#nm-tui
setup all interfaces again to manual configuration or disabled for ipv4 and ipv6

Prevent overwrite on ifcfg-xxx files by proxmox

#touch /etc/sysconfig/network-scripts/.pve-ignore.ifcfg-eth2 #touch /etc/sysconfig/network-scripts/.pve-ignore.ifcfg-eth3 #touch /etc/sysconfig/network-scripts/.pve-ignore.route6-eth2 #touch /etc/sysconfig/network-scripts/.pve-ignore.route6-eth3

Rebooted and everything stays working, cannot tell what line changed it to work without problems
nmtui is adding some useful lines to the ifcfg-xxx file that proxmox isn't writing to the ifcfg-xxx files.
 
  • Like
Reactions: shrdlicka
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back