PVE 6.0 no mac address in GUI

[alitvak69]

When I create a new container I leave network interface set with auto mac. Recently container stopped displaying autogenerated mac in GUI. It shows empty space. The problem is that with firewall on interface enabled and no mac address displayed I loose connectivity. I can either disable the firewall on the interface and let hackers invade or I can manually add a mac address to the interface. Neither is an adequate solution. What was broken, and why mac address no longer appears in GUI?

 

[alitvak69]

BTW,

MAC Address is being generated, just is not being assigned to an interface in gui

 

[dcsapak]

mhmm... works here, can you post a screenshot and the container config? (pct config ID)

 

[alitvak69]

arch: amd64
cores: 4
hostname: test3.teletownhall.us
memory: 4096
net0: bridge=vmbr0,name=eth0,ip=10.10.10.11/24,gw=10.10.10.1,firewall=1
ostype: centos
rootfs: volume1:vm-104-disk-0,size=80G
swap: 4096

 

[alitvak69]

No hardware address shown if I leave auto in the field.

 

[alitvak69]

 

[alitvak69]

Maybe a clue

Nov 6 03:40:43 virt3 pvedaemon[15570]: starting CT 104: UPID:virt3:00003CD2:00023167:5DC2870B:vzstart:104:root@pam:
Nov 6 03:40:43 virt3 pvedaemon[5406]: <root@pam> starting task UPID:virt3:00003CD2:00023167:5DC2870B:vzstart:104:root@pam:
Nov 6 03:40:43 virt3 systemd[1]: Starting PVE LXC Container: 104...
Nov 6 03:40:44 virt3 kernel: [ 1437.814376] EXT4-fs (dm-6): mounted filesystem with ordered data mode. Opts: (null)
Nov 6 03:40:44 virt3 kernel: [ 1438.058424] audit: type=1400 audit(1573029644.395:22): apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-104_</var/lib/lxc>" pid=15612 comm="apparmor_parser"
Nov 6 03:40:44 virt3 systemd-udevd[15579]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 6 03:40:44 virt3 systemd-udevd[15579]: Using default interface naming scheme 'v240'.
Nov 6 03:40:44 virt3 systemd-udevd[15579]: Could not generate persistent MAC address for vethYK256A: No such file or directory
Nov 6 03:40:44 virt3 systemd-udevd[15578]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 6 03:40:44 virt3 systemd-udevd[15578]: Using default interface naming scheme 'v240'.
Nov 6 03:40:44 virt3 systemd-udevd[15579]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 6 03:40:44 virt3 systemd-udevd[15579]: Could not generate persistent MAC address for fwbr104i0: No such file or directory
Nov 6 03:40:44 virt3 systemd-udevd[15578]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 6 03:40:44 virt3 systemd-udevd[15574]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 6 03:40:44 virt3 systemd-udevd[15578]: Could not generate persistent MAC address for fwpr104p0: No such file or directory
Nov 6 03:40:44 virt3 systemd-udevd[15574]: Using default interface naming scheme 'v240'.
Nov 6 03:40:44 virt3 systemd-udevd[15574]: Could not generate persistent MAC address for fwln104i0: No such file or directory
Nov 6 03:40:44 virt3 kernel: [ 1438.436844] fwbr104i0: port 1(fwln104i0) entered blocking state
Nov 6 03:40:44 virt3 kernel: [ 1438.436847] fwbr104i0: port 1(fwln104i0) entered disabled state
Nov 6 03:40:44 virt3 kernel: [ 1438.436922] device fwln104i0 entered promiscuous mode
Nov 6 03:40:44 virt3 kernel: [ 1438.437036] fwbr104i0: port 1(fwln104i0) entered blocking state
Nov 6 03:40:44 virt3 kernel: [ 1438.437038] fwbr104i0: port 1(fwln104i0) entered forwarding state
Nov 6 03:40:44 virt3 kernel: [ 1438.440413] vmbr0: port 3(fwpr104p0) entered blocking state
Nov 6 03:40:44 virt3 kernel: [ 1438.440415] vmbr0: port 3(fwpr104p0) entered disabled state
Nov 6 03:40:44 virt3 kernel: [ 1438.440472] device fwpr104p0 entered promiscuous mode
Nov 6 03:40:44 virt3 kernel: [ 1438.440509] vmbr0: port 3(fwpr104p0) entered blocking state
Nov 6 03:40:44 virt3 kernel: [ 1438.440510] vmbr0: port 3(fwpr104p0) entered forwarding state
Nov 6 03:40:44 virt3 kernel: [ 1438.443486] fwbr104i0: port 2(veth104i0) entered blocking state
Nov 6 03:40:44 virt3 kernel: [ 1438.443488] fwbr104i0: port 2(veth104i0) entered disabled state
Nov 6 03:40:44 virt3 kernel: [ 1438.443546] device veth104i0 entered promiscuous mode
Nov 6 03:40:44 virt3 kernel: [ 1438.506753] eth0: renamed from vethYK256A
Nov 6 03:40:44 virt3 kernel: [ 1438.628176] audit: type=1400 audit(1573029644.963:23): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="/usr/bin/lxc-start" name="/proc/sys/kernel/random/boot_id" pid=15613 comm="lxc-start" srcname="/d
ev/.lxc-boot-id" flags="rw, bind"
Nov 6 03:40:44 virt3 systemd[1]: Started PVE LXC Container: 104.
Nov 6 03:40:44 virt3 pvedaemon[5406]: <root@pam> end task UPID:virt3:00003CD2:00023167:5DC2870B:vzstart:104:root@pam: OK
Nov 6 03:40:45 virt3 kernel: [ 1438.975772] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Nov 6 03:40:45 virt3 kernel: [ 1438.975812] fwbr104i0: port 2(veth104i0) entered blocking state
Nov 6 03:40:45 virt3 kernel: [ 1438.975813] fwbr104i0: port 2(veth104i0) entered forwarding state
Nov 6 03:40:52 virt3 pvedaemon[5414]: <root@pam> successful auth for user 'root@pam'
Nov 6 03:41:00 virt3 systemd[1]: Starting Proxmox VE replication runner...
Nov 6 03:41:00 virt3 systemd[1]: pvesr.service: Succeeded.

 

[alitvak69]

Any clue? How do you even debug this?

 

[oguz]

hi,

check the bug report[0]

there's an initial patch available as well. it should be fixed and packaged soon.

[0]: https://bugzilla.proxmox.com/show_bug.cgi?id=2453

 

[alitvak69]

Thank you. Is it save to try the patch before the official package is available?

 

[alitvak69]

Added the patch in the Config.pm do you need to restart anything?

 

[oguz]

Thank you. Is it save to try the patch before the official package is available?

it's not fully reviewed/tested, so do at your own risk.

Added the patch in the Config.pm do you need to restart anything?

pvedaemon and pveproxy

 

[alitvak69]

I made a backup copy of the original Config.pm. After restarting pvedaemon and pveproxy newly created machine seems to work with MAC address added to the GUI and firewall works as well.