[PVE7] Manually Set Up Bond and Modified VMBR0; Now any change to network settings inside the PVE Web GUI adds "auto" interface commands; break access

[SInisterPisces]

Hello,

The PVE tutorial I was using said to do set up a NIC bond and modify vmbr0 by hand, instead of using the PVE GUI. I assume this is because if you tried to do it all in the web GUI you'd probably get locked out somewhere in the middle of the process. I manually edited the /etc/network/interfaces file to set up a bond between two 2.5GbE ports on my machine, then pointed vmbr0 at them.

Now, if I do anything in the PVE web UI's networking interface, even adding a comment, it adds the "auto" lines and I lose networking.

So, like, it wants to do this when I add a comment to eno1:

+auto eno1
 iface eno1 inet manual

I don't know what the auto command is supposed to do, but it breaks my access to the web GUI when it's there. And it wasn't in the auto-generated config file. In fact, I had no issues modifying the network config via the Web GUI to add comments before I manually set up the bond.

Here's what my current, working network config looks like.

Any ideas? I'm stumped.

~# cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

iface eno1 inet manual

iface enp2s0 inet manual

iface wlp3s0 inet manual

iface enx0024278808c1 inet manual

auto bond0
iface bond0 inet manual
        bond-slaves eno1 enp2s0
        bond-miimon 100
        bond-mode balance-alb

auto vmbr0
iface vmbr0 inet static
        address 10.10.100.140/24
        gateway 10.10.100.1
        bridge-ports bond0
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

 

[vesalius]

Did you try to reinstall ifup2down as suggested in the other thread you responded in?

Post in thread 'Upgrade to Proxmox 7 - Bond (LACP) Interface not working anymore'
https://forum.proxmox.com/threads/u...terface-not-working-anymore.92060/post-472796

 

[SInisterPisces]

Not yet. I've destroyed the bond, for now.

I noticed that my nightly backup job wasn't running anymore, and on closer look, the PVE node suddenly couldn't access any network storage anymore. I hadn't noticed right off, since this is a new install with no active VM or CT yet, but since I'm using network storage for all my ISOs, templates, backups, and everything else but VM images directly on the node, that was no good.

Destroying the bond made everything start working again.

 

[SInisterPisces]

Did you try to reinstall ifup2down as suggested in the other thread you responded in?

Post in thread 'Upgrade to Proxmox 7 - Bond (LACP) Interface not working anymore'
https://forum.proxmox.com/threads/u...terface-not-working-anymore.92060/post-472796

Okay, so... I tried this.

Reinstalled ifupdown2, rebooted, and I'm still seeing it insert "auto" commands into the interface file when I use the GUI.

Here's an example of what happens when I try to add a comment.

Pending changes (Either reboot or use 'Apply Configuration' (needs ifupdown2) to activate)
--- /etc/network/interfaces    2022-10-19 14:49:43.450852825 -0500
+++ /etc/network/interfaces.new    2022-10-19 15:10:22.349753733 -0500
@@ -12,8 +12,11 @@
 auto lo
 iface lo inet loopback
 
+auto eno1
 iface eno1 inet manual
+#Built-in 2.5GbE (Intel) - Port 1
 
+auto enp2s0
 iface enp2s0 inet manual
 
 iface wlp3s0 inet manual