PVE Networking got jacked up

RCNunya

Active Member
Nov 17, 2011
16
0
41
So I couldn't connect to my host today. Got a monitor hooked up and with some research found the interface was not up. I have it hard coded, but when I manually brought it up using 'ip link set eno1 up', it got a DHCP address it seems. I also had to use 'ifup vmbr0'

If I reboot, I have to manually bring the interfaces up again and goes to the DHCP address even though the screen says to connect to the static address I have assigned.

/etc/network/interfaces looks like below

auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet dhcp
address 192.168.0.250/24
gateway 192.168.0.1
bridge-ports eno1
bridge-stp off
bridge-fd 0

How can I get this back to my static IP address and fix the networking?
 
So I couldn't connect to my host today. Got a monitor hooked up and with some research found the interface was not up. I have it hard coded, but when I manually brought it up using 'ip link set eno1 up', it got a DHCP address it seems. I also had to use 'ifup vmbr0'

If I reboot, I have to manually bring the interfaces up again and goes to the DHCP address even though the screen says to connect to the static address I have assigned.

/etc/network/interfaces looks like below

auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet dhcp
address 192.168.0.250/24
gateway 192.168.0.1
bridge-ports eno1
bridge-stp off
bridge-fd 0

How can I get this back to my static IP address and fix the networking?
For staric IP it should be "iface vmbr0 inet static" instead of "iface vmbr0 inet dhcp". All other lines look fine,
 
Last edited:
Sorry sorry, that was my bad, left that there while I was trying something. I saw the 'inet manual' and forgot about the 'inet dhcp'.

So That did fix my IP issue, but networking is still failing to start upon reboot.
systemctl restart networking doesn't seem to work, but the 'ip link set eno1 up' and 'ifup vmbr0' get's it back up.
 
Then I would have a look at the syslog and see why upping the interfaces fails.
 
Looks like this is happening at each boot -
Apr 15 15:59:28 proxmox kernel: [ 1725.371481] vmbr0: port 1(eno1) entered blocking state
Apr 15 15:59:28 proxmox kernel: [ 1725.371484] vmbr0: port 1(eno1) entered disabled state
Apr 15 15:59:28 proxmox kernel: [ 1725.371672] device eno1 entered promiscuous mode
Apr 15 15:59:28 proxmox kernel: [ 1725.374784] vmbr0: port 1(eno1) entered blocking state
Apr 15 15:59:28 proxmox kernel: [ 1725.374801] vmbr0: port 1(eno1) entered forwarding state
 
OK, looks like I got it. I had a line in fstab to mount a folder that was failing. I removed it and reboot worked as expected.
I probably added it when playing with Jellyfin and forgot to remove.

Apr 15 17:24:37 proxmox networking[1465]: error: vmbr0 : eno1 : (eno1: up cmd '/etc/network/if-up.d/fstab' failed: retu> Apr 15 17:24:37 proxmox networking[1465]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log m> Apr 15 17:24:37 proxmox networking[1465]: )) Apr 15 17:24:37 proxmox networking[1465]: warning: vmbr0: interface not recognized - please check interface configurati> Apr 15 17:24:37 proxmox kernel: CIFS: Attempting to mount \\192.168.0.245\Movies Apr 15 17:24:37 proxmox kernel: CIFS: VFS: Error connecting to socket. Aborting operation. Apr 15 17:24:37 proxmox kernel: CIFS: VFS: cifs_mount failed w/return code = -101
 

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!