Vmbr0 is down after reboot

atideath

New Member
Mar 13, 2023
7
0
1
Hello.

I have a problem with my one Proxmox instances long time ago. I tried lot of suggestion and solution but it isn't working. :( Currently updated my proxmox instance to 8.2.4 (latest) version and the problem is still active.

The problem is: When I restart or start the proxmox server, vmbr0 is down, the server isn't available. When I phisically type ifup vmbr0 from console, everything is working until I will restart the server. I tried to reinstall ifupdown2 with apt it isn't resolve the problem. Who can help in this problem? Lot of thanks!
 
Web-UI --> network --> vmbr0 --> check for auto-start yes and device under the bridge, eg. eno1 (check your's), should auto-start no because it's startet by the bridge itself !!
 
Web-UI --> network --> vmbr0 --> check for auto-start yes and device under the bridge, eg. eno1 (check your's), should auto-start no because it's startet by the bridge itself !!
This is set correctly. There is a problem with it as well.

1724740594641.png
 
Take a look at cmd dmesg and /var/log/<messages>|<kern.log>|<daemon.log> to find anythink about your vmbr0+eno1 problem.
 
Take a look at cmd dmesg and /var/log/<messages>|<kern.log>|<daemon.log> to find anythink about your vmbr0+eno1 problem.
I am only found this in the kern.log:

Code:
2024-08-27T10:08:07.830820+02:00 morpheus kernel: [   30.549235] igb 0000:02:00.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
2024-08-27T10:08:07.831682+02:00 morpheus NetworkManager[1260]: <info>  [1724746087.8309] device (eno1): carrier: link connected
2024-08-27T10:08:07.831918+02:00 morpheus NetworkManager[1260]: <info>  [1724746087.8315] device (eno1): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
2024-08-27T10:08:07.832463+02:00 morpheus NetworkManager[1260]: <info>  [1724746087.8323] policy: auto-activating connection 'Wired connection 1' (eba70939-1f69-3b49-aece-88ee56b29df4)
2024-08-27T10:08:07.833115+02:00 morpheus NetworkManager[1260]: <info>  [1724746087.8330] device (eno1): Activation: starting connection 'Wired connection 1' (eba70939-1f69-3b49-aece-88ee56b29df4)
2024-08-27T10:08:07.833273+02:00 morpheus NetworkManager[1260]: <info>  [1724746087.8331] device (eno1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
2024-08-27T10:08:07.833644+02:00 morpheus NetworkManager[1260]: <info>  [1724746087.8335] manager: NetworkManager state is now CONNECTING
2024-08-27T10:08:07.833937+02:00 morpheus NetworkManager[1260]: <info>  [1724746087.8338] device (eno1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
2024-08-27T10:08:07.834940+02:00 morpheus NetworkManager[1260]: <info>  [1724746087.8348] device (eno1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
2024-08-27T10:08:07.835587+02:00 morpheus NetworkManager[1260]: <info>  [1724746087.8355] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
2024-08-27T10:08:07.859848+02:00 morpheus NetworkManager[1260]: <info>  [1724746087.8597] device (eno1): ip:ac6: addrconf6: kernel does not support IPv6
2024-08-27T10:08:07.876424+02:00 morpheus NetworkManager[1260]: <warn>  [1724746087.8763] platform-linux: do-add-ip6-address[2: fe80::4c30:9d7f:45d0:37e0]: failure 95 (Operation not supported)
2024-08-27T10:08:09.877784+02:00 morpheus NetworkManager[1260]: <warn>  [1724746089.8773] platform-linux: do-add-ip6-address[2: fe80::b3a1:3886:605a:47d3]: failure 95 (Operation not supported)
2024-08-27T10:08:11.879395+02:00 morpheus NetworkManager[1260]: <warn>  [1724746091.8790] platform-linux: do-add-ip6-address[2: fe80::817d:ec17:c600:d67]: failure 95 (Operation not supported)
2024-08-27T10:08:11.968988+02:00 morpheus networking[1460]: warning: vrf: cache v6: cmd '/bin/ip -6 rule show' failed: returned 255 (RTNETLINK answers: Address family not supported by protocol
2024-08-27T10:08:11.969087+02:00 morpheus networking[1460]: Dump terminated
2024-08-27T10:08:11.969129+02:00 morpheus networking[1460]: )
2024-08-27T10:08:11.969192+02:00 morpheus /usr/sbin/ifup[1460]: warning: vrf: cache v6: cmd '/bin/ip -6 rule show' failed: returned 255 (RTNETLINK answers: Address family not supported by protocol#012Dump terminated#012)
2024-08-27T10:08:12.428868+02:00 morpheus NetworkManager[1260]: <info>  [1724746092.4287] manager: (vmbr0): new Bridge device (/org/freedesktop/NetworkManager/Devices/6)
2024-08-27T10:08:12.430589+02:00 morpheus networking[1460]: warning: error writing to file /proc/sys/net/ipv6/conf/eno1/disable_ipv6([Errno 2] No such file or directory: '/proc/sys/net/ipv6/conf/eno1/disable_ipv6')
2024-08-27T10:08:12.430803+02:00 morpheus /usr/sbin/ifup[1460]: warning: error writing to file /proc/sys/net/ipv6/conf/eno1/disable_ipv6([Errno 2] No such file or directory: '/proc/sys/net/ipv6/conf/eno1/disable_ipv6')
2024-08-27T10:08:12.433774+02:00 morpheus kernel: [   35.151975] vmbr0: port 1(eno1) entered blocking state
2024-08-27T10:08:12.433798+02:00 morpheus kernel: [   35.151985] vmbr0: port 1(eno1) entered disabled state
2024-08-27T10:08:12.433799+02:00 morpheus kernel: [   35.152007] igb 0000:02:00.0 eno1: entered allmulticast mode
2024-08-27T10:08:12.433801+02:00 morpheus kernel: [   35.152189] igb 0000:02:00.0 eno1: entered promiscuous mode
2024-08-27T10:08:12.439993+02:00 morpheus networking[1460]: warning: error writing to file /proc/sys/net/ipv6/conf/vmbr0/forwarding([Errno 2] No such file or directory: '/proc/sys/net/ipv6/conf/vmbr0/forwarding')
2024-08-27T10:08:12.440136+02:00 morpheus /usr/sbin/ifup[1460]: warning: error writing to file /proc/sys/net/ipv6/conf/vmbr0/forwarding([Errno 2] No such file or directory: '/proc/sys/net/ipv6/conf/vmbr0/forwarding')
2024-08-27T10:08:12.445768+02:00 morpheus kernel: [   35.164632] vmbr0: port 1(eno1) entered blocking state
2024-08-27T10:08:12.445779+02:00 morpheus kernel: [   35.164639] vmbr0: port 1(eno1) entered forwarding state
2024-08-27T10:08:12.446194+02:00 morpheus NetworkManager[1260]: <info>  [1724746092.4461] device (vmbr0): carrier: link connected
2024-08-27T10:08:12.531313+02:00 morpheus NetworkManager[1260]: <info>  [1724746092.5311] manager: (vmbr1): new Bridge device (/org/freedesktop/NetworkManager/Devices/7)
2024-08-27T10:08:13.174042+02:00 morpheus systemd[1]: Finished networking.service - Network initialization.
2024-08-27T10:08:13.174599+02:00 morpheus systemd[1]: Reached target network.target - Network.
 
And it is my interfaces file content:
Code:
auto lo
iface lo inet loopback

iface eno1 inet manual

iface eno2 inet manual

iface eno3 inet manual

iface eno4 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.20/24
        gateway 192.168.1.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0

auto vmbr1
iface vmbr1 inet manual
        bridge-ports none
        bridge-stp off
        bridge-fd 0
 

Attachments

  • kern.log
    197.1 KB · Views: 2
Last edited:
Have you ipv6 defined in the vmbr0 config window ? Content of /etc/hosts ?
No.
1724749099333.png

But in the host file is contain:

Code:
127.0.0.1 localhost.localdomain localhost
192.168.1.20 morpheus.xyxy.eu morpheus

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
 
Last edited:
Do you have these ipv6 lines included also ? Else include them.
cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
#
# ... maybe some of your own here
 
We got some NetworkManager infos also while there is no nmcli cmd installed, eg.:
/var/log/messages.1:Jun 28 10:31:45 ... kernel: [3106457.988580] task:NetworkManager state:D stack: 0 pid:3595108 ppid:3594872 flags:0x00004000
/var/log/messages.1:Jun 28 10:33:46 ... kernel: [3106578.820052] task:NetworkManager state:D stack: 0 pid:3595108 ppid:3594872 flags:0x00004000
PS: Chat made some auto emoj's from the lines but that doesn't any matter.
 
Last edited:
There are still parts of NetworkManager installed but not the cmd nmcli. Do you have the binary by testing "nmcli con show" ?
 
There are still parts of NetworkManager installed but not the cmd nmcli. Do you have the binary by testing "nmcli con show" ?
Currently I disabled the networkmanager with these commands and restart the server:
Code:
sudo systemctl stop NetworkManager-wait-online.service
sudo systemctl disable NetworkManager-wait-online.service

sudo systemctl stop NetworkManager-dispatcher.service
sudo systemctl disable NetworkManager-dispatcher.service

sudo systemctl stop network-manager.service
sudo systemctl disable network-manager.service

The nmcli con show say now: "NetworkManager isn't running", but currently after the restart the server is reachable again in the network. Not need to cmd ifup vmbr0. It is possible that the docker installed the NetworkManager and that caused the problem.

Thanks a lot for the helping.
 

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!

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!