Rebooted Long Running Proxmox server. Bridge (set statically) is fighting with dhcpcd

D

DaveHill

New Member
Sep 16, 2021
1
0
1
33
I've had my proxmox server running for years, and occasionally update it. Today i rebooted it and my networking is totally borked on both my host and VM's

Symptoms:

- Initially, when i started debugging, i noticed my vmbr0 interface had TWO ip addresses. My static one and what appeared to be a DHCP lease.

- Stopping dhcpcd and bouncing allows me to ping default interface / access proxmox

- However, with this disabled, i also lost access to my VM's. Even the ones with static IP addresses

- With dhcpcd enabled, i am unable to ping my default gateway, even if i set it with ip route add default 192.168.0.1

My configuration lines up with the documentation i found still

1631817748004.png


I did a yum update, and it's still having the same symptoms. Any ideas?

Sep 16 13:34:19 proxmox pve-ha-crm[2345]: starting server Sep 16 13:34:19 proxmox pve-ha-crm[2345]: status change startup => wait_for_quorum Sep 16 13:34:19 proxmox kernel: [ 9.096588] igb 0000:25:00.0 enp37s0: igb: enp37s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Sep 16 13:34:19 proxmox systemd[1]: Started PVE Cluster HA Resource Manager Daemon. Sep 16 13:34:19 proxmox kernel: [ 9.204266] vmbr0: port 1(enp37s0) entered blocking state Sep 16 13:34:19 proxmox kernel: [ 9.204268] vmbr0: port 1(enp37s0) entered forwarding state Sep 16 13:34:19 proxmox dhcpcd[1898]: enp37s0: carrier acquired Sep 16 13:34:19 proxmox dhcpcd[1898]: enp37s0: IAID c2:b4:cf:01 Sep 16 13:34:19 proxmox dhcpcd[1898]: enp37s0: IAID conflicts with one assigned to vmbr0 Sep 16 13:34:19 proxmox dhcpcd[1898]: enp37s0: adding address fe80::c2cf:5756:589c:44a1 Sep 16 13:34:19 proxmox dhcpcd[1898]: ipv6_addaddr1: Permission denied Sep 16 13:34:19 proxmox dhcpcd[1898]: vmbr0: carrier acquired Sep 16 13:34:19 proxmox dhcpcd[1898]: vmbr0: IAID c2:b4:cf:01 Sep 16 13:34:19 proxmox dhcpcd[1898]: vmbr0: IAID conflicts with one assigned to enp37s0 Sep 16 13:34:19 proxmox dhcpcd[1898]: vmbr0: adding address fe80::c2cf:5756:589c:44a1 Sep 16 13:34:19 proxmox kernel: [ 9.204487] IPv6: ADDRCONF(NETDEV_CHANGE): vmbr0: link becomes ready Sep 16 13:34:20 proxmox dhcpcd[1898]: vmbr0: rebinding lease of 192.168.0.126 Sep 16 13:34:20 proxmox dhcpcd[1898]: enp37s0: soliciting an IPv6 router Sep 16 13:34:20 proxmox pveproxy[2349]: starting server Sep 16 13:34:20 proxmox pveproxy[2349]: starting 3 worker(s) Sep 16 13:34:20 proxmox pveproxy[2349]: worker 2350 started Sep 16 13:34:20 proxmox dhcpcd[1898]: vmbr0: soliciting an IPv6 router Sep 16 13:34:20 proxmox pveproxy[2349]: worker 2351 started Sep 16 13:34:20 proxmox pveproxy[2349]: worker 2352 started Sep 16 13:34:20 proxmox systemd[1]: Started PVE API Proxy Server. Sep 16 13:34:20 proxmox systemd[1]: Starting PVE Local HA Resource Manager Daemon... Sep 16 13:34:20 proxmox systemd[1]: Starting PVE SPICE Proxy Server... Sep 16 13:34:20 proxmox dhcpcd[1898]: enp37s0: rebinding lease of 192.168.0.126 Sep 16 13:34:20 proxmox systemd[1]: systemd-rfkill.service: Succeeded. Sep 16 13:34:20 proxmox spiceproxy[2360]: starting server Sep 16 13:34:20 proxmox spiceproxy[2360]: starting 1 worker(s) Sep 16 13:34:20 proxmox spiceproxy[2360]: worker 2361 started Sep 16 13:34:20 proxmox systemd[1]: Started PVE SPICE Proxy Server. Sep 16 13:34:20 proxmox pve-ha-lrm[2362]: starting server Sep 16 13:34:20 proxmox pve-ha-lrm[2362]: status change startup => wait_for_agent_lock Sep 16 13:34:20 proxmox systemd[1]: Started PVE Local HA Resource Manager Daemon. Sep 16 13:34:20 proxmox systemd[1]: Starting PVE guests... Sep 16 13:34:21 proxmox dhcpcd[1898]: vmbr0: Router Advertisement from fe80::c2c9:e3ff:fe0a:7d0c Sep 16 13:34:21 proxmox dhcpcd[1898]: vmbr0: adding default route via fe80::c2c9:e3ff:fe0a:7d0c Sep 16 13:34:21 proxmox dhcpcd[1898]: vmbr0: soliciting a DHCPv6 lease Sep 16 13:34:21 proxmox pve-guests[2364]: <root@pam> starting task UPID:proxmox:00000944:00000455:61438E2D:startall::root@pam: Sep 16 13:34:21 proxmox pvesh[2364]: Starting VM 101 Sep 16 13:34:21 proxmox pve-guests[2372]: <root@pam> starting task UPID:proxmox:00000945:00000456:61438E2D:qmstart:101:root@pam: Sep 16 13:34:21 proxmox pve-guests[2373]: start VM 101: UPID:proxmox:00000945:00000456:61438E2D:qmstart:101:root@pam: Sep 16 13:34:21 proxmox systemd[1]: Created slice qemu.slice. Sep 16 13:34:21 proxmox systemd[1]: Started 101.scope. Sep 16 13:34:21 proxmox systemd-udevd[1424]: Using default interface naming scheme 'v240'. Sep 16 13:34:21 proxmox systemd-udevd[1424]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Sep 16 13:34:21 proxmox systemd-udevd[1424]: Could not generate persistent MAC address for tap101i0: No such file or directory Sep 16 13:34:21 proxmox dhcpcd[1898]: tap101i0: waiting for carrier Sep 16 13:34:21 proxmox dhcpcd[1898]: tap101i0: carrier acquired Sep 16 13:34:21 proxmox dhcpcd[1898]: tap101i0: IAID e8:4a:40:a2 Sep 16 13:34:21 proxmox dhcpcd[1898]: tap101i0: adding address fe80::25ba:b01:7abb:f533 Sep 16 13:34:22 proxmox kernel: [ 11.708877] device tap101i0 entered promiscuous mode Sep 16 13:34:22 proxmox kernel: [ 11.715146] vmbr0: port 2(tap101i0) entered blocking state Sep 16 13:34:22 proxmox kernel: [ 11.715147] vmbr0: port 2(tap101i0) entered disabled state Sep 16 13:34:22 proxmox kernel: [ 11.715252] vmbr0: port 2(tap101i0) entered blocking state Sep 16 13:34:22 proxmox kernel: [ 11.715253] vmbr0: port 2(tap101i0) entered forwarding state Sep 16 13:34:22 proxmox dhcpcd[1898]: tap101i0: soliciting an IPv6 router Sep 16 13:34:22 proxmox dhcpcd[1898]: tap101i0: soliciting a DHCP lease Sep 16 13:34:23 proxmox dhcpcd[1898]: enp37s0: probing address 192.168.0.126/24 Sep 16 13:34:24 proxmox dhcpcd[1898]: vmbr0: leased 192.168.0.126 for 7200 seconds Sep 16 13:34:24 proxmox dhcpcd[1898]: vmbr0: adding route to 192.168.0.0/24 Sep 16 13:34:24 proxmox dhcpcd[1898]: vmbr0: adding default route via 192.168.0.1 Sep 16 13:34:24 proxmox systemd[1]: Stopping Network Time Synchronization... Sep 16 13:34:24 proxmox systemd[1]: systemd-timesyncd.service: Succeeded. Sep 16 13:34:24 proxmox systemd[1]: Stopped Network Time Synchronization. Sep 16 13:34:24 proxmox systemd[1]: Starting Network Time Synchronization... Sep 16 13:34:24 proxmox systemd[1]: Started Network Time Synchronization. Sep 16 13:34:25 proxmox systemd-timesyncd[2520]: Synchronized to time server for the first time 162.159.200.1:123 (0.debian.pool.ntp.org). Sep 16 13:34:26 proxmox pvesh[2364]: Starting VM 102 Sep 16 13:34:26 proxmox pve-guests[2372]: <root@pam> starting task UPID:proxmox:000009DB:000005E7:61438E32:qmstart:102:root@pam: Sep 16 13:34:26 proxmox pve-guests[2523]: start VM 102: UPID:proxmox:000009DB:000005E7:61438E32:qmstart:102:root@pam: Sep 16 13:34:26 proxmox systemd[1]: Started 102.scope. Sep 16 13:34:26 proxmox systemd-udevd[1424]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Sep 16 13:34:26 proxmox systemd-udevd[1424]: Could not generate persistent MAC address for tap102i0: No such file or directory Sep 16 13:34:22 proxmox dhcpcd[1898]: tap101i0: soliciting a DHCP lease Sep 16 13:34:23 proxmox dhcpcd[1898]: enp37s0: probing address 192.168.0.126/24 Sep 16 13:34:24 proxmox dhcpcd[1898]: vmbr0: leased 192.168.0.126 for 7200 seconds Sep 16 13:34:24 proxmox dhcpcd[1898]: vmbr0: adding route to 192.168.0.0/24 Sep 16 13:34:24 proxmox dhcpcd[1898]: vmbr0: adding default route via 192.168.0.1 Sep 16 13:34:24 proxmox systemd[1]: Stopping Network Time Synchronization... Sep 16 13:34:24 proxmox systemd[1]: systemd-timesyncd.service: Succeeded. Sep 16 13:34:24 proxmox systemd[1]: Stopped Network Time Synchronization. Sep 16 13:34:24 proxmox systemd[1]: Starting Network Time Synchronization... Sep 16 13:34:24 proxmox systemd[1]: Started Network Time Synchronization. Sep 16 13:34:25 proxmox systemd-timesyncd[2520]: Synchronized to time server for the first time 162.159.200.1:123 (0.debian.pool.ntp.org). Sep 16 13:34:26 proxmox pvesh[2364]: Starting VM 102 Sep 16 13:34:26 proxmox pve-guests[2372]: <root@pam> starting task UPID:proxmox:000009DB:000005E7:61438E32:qmstart:102:root@pam: Sep 16 13:34:26 proxmox pve-guests[2523]: start VM 102: UPID:proxmox:000009DB:000005E7:61438E32:qmstart:102:root@pam: Sep 16 13:34:26 proxmox systemd[1]: Started 102.scope. Sep 16 13:34:26 proxmox systemd-udevd[1424]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Sep 16 13:34:26 proxmox systemd-udevd[1424]: Could not generate persistent MAC address for tap102i0: No such file or directory
 
Hi,

what do you mean by "yum update"? The PVE is debian based and therefore uses apt and not yum like CentOS/...

Also, please post the outputs of ip address and ip route from your host/VMs. The config of dhcpd might also be interesting.
 
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