ForstJan 16, 2025
Gosh darn, are the network configuration managers ever annoying to deal with sometimes.
#Proxmox has a patched #ifupdown2, which, for who knows whatever reason, ignores "accept-ra" and a bunch of other sysctl settings for bridges. Isn't it a great idea when your hypervisor trusts RAs from virtual machines by default?
1977erSep 17, 2024
Weil in der /etc/network/interfaces ein "address 2001:db8:100:200:1/64" stand, dachte sich #ifupdown2 einfach mal: ach, dann braucht das iface sicher auch den Rest der Konfig nicht. Danke für garnichts. #grmpf
Robert SanderFeb 20, 2024

TIL: After "apt install ifupdown2 && apt purge ifupdown" you need to "apt install --reinstall ifupdown2 && systemctl enable networking.service"

Otherwise your network will not start any more after the next boot.

#debian #proxmox #ifupdown #ifupdown2

AliveDevilJan 17, 2024

#ifupdown2 - flawless.

Why are vmbr1, vmbr2 and vmbr3 missing the VIDs 2-4094 despite being set in the interface configuration file?

#Proxmox #Linux #Networking

VanessaAug 21, 2019
#SOS: @skorpy und das #AS64475 benötigt dringend manuelle Abhängigkeiten in #ifupdown2. Helfen Sie uns! #cccamp19 DECT: 64475