VMBR0 active but not available in GUI after updating IP address

[lilotter45]

I recently moved my Proxmox box from my office, where I initially configured it, to my home network, requiring a change in the network configuration. After making the network updates I am able connect to the server and access the GUI, but vmbr0 does not show up under System > Network in the GUI. If I try to update the static IP of existing VMs, or create new VMs, there are no options that show up for network adapter.

I have tried recreating vmbr0 in the GUI, but it tells me it already exists.

Have I missed something in making this change that is causing the vmbr0 to not show up? I can't think of anything else to try to bring it back up.


I edited /etc/network/interfaces to reflect the change in my home network from 10.0.0.1/24 to 192.168.1.1/24:

auto lo
iface lo inet loopback

iface enp1s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.25
        netmask 255.255.255.0
        gateway 192.168.1.1
        bridge_ports enp1s0
        bridge_stp off
        bridge_fd 0

iface eno2 inet manual

This is the configuration created during setup and fully functional at my office, with the exception of the change in IP range.

I also updated the DNS server and Hosts file to reflect the change in IP range.

The output of ifconfig is:

enp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether b4:2e:99:aa:42:86  txqueuelen 1000  (Ethernet)
        RX packets 15050  bytes 4070999 (3.8 MiB)
        RX errors 0  dropped 35  overruns 0  frame 0
        TX packets 3271  bytes 2093533 (1.9 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0xa1100000-a111ffff

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 771  bytes 186553 (182.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 771  bytes 186553 (182.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vmbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.25  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::b62e:99ff:feaa:4286  prefixlen 64  scopeid 0x20<link>
        ether b4:2e:99:aa:42:86  txqueuelen 1000  (Ethernet)
        RX packets 14948  bytes 3853750 (3.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2949  bytes 2076145 (1.9 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

System > Network in GUI:


Updating adapter settings - tells me vmbr0 does not exist and I cannot save any changes:

 

[Moayad]

Hi,

Did you reboot your host after editing the Network Configuration?

and is there an error if you did the following command? ifreload -a

 

[lilotter45]

Yes, I have rebooted the server a number of times since applying the new network configuration. I also deleted the updated configuration file, copied and updated from the backup to no avail.

This morning I tried running ifreload -a, found out I didn't have ifupdown2 installed, so added it.

The first time I ran it from the physical machine and got the following output:

root@pve:~# ifreload -a
[176819.542731] Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
[176819.631298] vmbr0: the hash_elasticity option has been deprecated and is always 16

I just now ran the same command via PuTTY to copy/paste the output here and received no errors and the bridge is now showing up in the GUI. I didn't check the GUI before running the command via PuTTY, so I'm not sure at what point the bridge appeared in the GUI.

Since then, I've restarted the server to make sure the bridge comes back up on restart and it does.

I don't know if ifreload did something, or if it is just coincidence, but I've been working on this, off-and-on, for the better part of a week without any progress until now.

Anyway, it seems to be fixed now. Thanks for your input.