No ifupdown2.conf, no networking.

B

BobhWasatch

Famous Member
Proxmox Subscriber
Mar 16, 2019
1,068
422
128
63
California, USA
I upgraded to PVE 7 and everything went fine. So I decided to switch to ifupdown2, and this happens (copied by hand from the console screen):

Code: 
...
Setting up ifupdown2 (3.1.0-1+pmx2)
Installing new version of config file /etc/default/networking ...
Reloading network config on first install
error: main exception: [Errno 2] No such file or directory '/etc/network/ifupdown2/ifupdown2.conf'
dpkg: error processing package ifupdown2 (--configure):
 installled ifupdown2 package post-isntallation script subprocess returned error exit status 1
...

And the network does not come up. What is the problem here? In the meantime I switched back to ifupdown and it works again.

ETA: I am using the Enterprise repository. My sources.list:

Code: 
root@vm-host:~# cat /etc/apt/sources.list
deb http://ftp.us.debian.org/debian/ bullseye main contrib non-free
deb-src http://ftp.us.debian.org/debian/ bullseye main contrib non-free

deb http://security.debian.org/debian-security bullseye-security main contrib non-free
deb-src http://security.debian.org/debian-security bullseye-security main contrib non-free

# bullseye-updates, previously known as 'volatile'
deb http://ftp.us.debian.org/debian/ bullseye-updates main contrib non-free
deb-src http://ftp.us.debian.org/debian/ bullseye-updates main contrib non-free

Code: 
root@vm-host:~# cat /etc/apt/sources.list.d/pve-enterprise.list 
deb https://enterprise.proxmox.com/debian/pve bullseye pve-enterprise
 
Last edited:
There is no built-in support for SLAAC at all and it breaks existing configurations thereby making it not a drop-in replacement.

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

iface vmbr0 inet6 auto

This no longer works. You will have only a link-local ipv6 address after the upgrade. The "interfaces.new" file the upgrade makes is identical to the original, it does not put in the sysctl magic that is needed, nor does it say anything about "auto" not being supported. The magic invocation that is needed is not documented anywhere in the ifupdown2 docs AFAICT, you just have to know (or find the bug report with Google).

Granted, if this were a server on the real internet it would have a static ipv6. But if ifupdown2 is intended to replace ifupdown for all use cases then this need to be fixed because SLAAC is actually pretty darn common.
 
You must log in or register to reply here.
Top Bottom