No Internet on all VMs after update

If you read this thread you would know that he can not update the packages because of a bug in ifupdown. Please follow along before you post.

Hi,
why are you replying on a thread resolved 2 months ago ?

User had bug with ifupdown2 2.0.1-1+pve4 (a forwarding bug patch was missing), and it was fixed in ifupdown2_2.0.1-1+pve7_all.deb . That's why I said to upgrade to last version.



"
spirit said:
should be fixed in ifupdown2_2.0.1-1+pve7_all.deb , already available in no-subscription repo.

what is your version ?
ifupdown2 2.0.1-1+pve4
"
proxminent said:
ifupdown2 2.0.1-1+pve4
simply "apt update" && "apt dist-upgrade" to update to last version
"
 
Hi, I updated this morning and after rebooting I now have the same problem.
I'm on a hetzner server as well.

This is the output when I try to install this ifupdown2_2.0.1-1+pve7_all.deb

Code:
dpkg: considering removing ifupdown in favour of ifupdown2 ...
dpkg: no, cannot proceed with removal of ifupdown (--auto-deconfigure will help):
ifenslave depends on ifupdown (>= 0.7.46)
  ifupdown is to be removed.

dpkg: regarding ifupdown2_2.0.1-1+pve7_all.deb containing ifupdown2:
ifupdown2 conflicts with ifupdown
  ifupdown (version 0.8.35+pve1) is present and installed.

dpkg: error processing archive ifupdown2_2.0.1-1+pve7_all.deb (--install):
conflicting packages - not installing ifupdown2
Errors were encountered while processing:
ifupdown2_2.0.1-1+pve7_all.deb

ifupdown2 is not installed at all.

Hope someone can help me

Thanks in advance
 
ifupdown2 2.0.1-1+pve4 don't work.
roll back or exclude ifupdown2 for updates
I know, ifupdown2 2.0.1-1+pve4 is not installed.

I have ifupdown 0.8.35+pve1

Here is the list of what has been installed/updated. ifupdown is not even on the list.

Code:
Start-Date: 2020-10-15  10:35:57
Commandline: apt-get -y install base-files libproxmox-acme-perl libproxmox-backup-qemu0 libpve-access-control libpve-cluster-api-perl libpve-cluster-perl libpve-common-perl libpve-guest-common-perl libpve-storage-perl libx11-6 libx11-data libx11-xcb1 linux-image-amd64 linux-libc-dev proxmox-backup-client proxmox-ve proxmox-widget-toolkit pve-cluster pve-container pve-docs pve-firewall pve-firmware pve-ha-manager pve-i18n pve-kernel-5.4 pve-kernel-helper pve-manager pve-qemu-kvm qemu-server
Install: proxmox-archive-keyring:amd64 (1.0, automatic), pve-kernel-5.4.65-1-pve:amd64 (5.4.65-1, automatic), qrencode:amd64 (4.0.2-1, automatic), linux-image-4.19.0-11-amd64:amd64 (4.19.146-1, automatic), libqrencode4:amd64 (4.0.2-1, automatic)
Upgrade: proxmox-widget-toolkit:amd64 (2.2-10, 2.3-1), pve-kernel-5.4:amd64 (6.2-5, 6.2-7), libpve-access-control:amd64 (6.1-2, 6.1-3), linux-libc-dev:amd64 (4.19.132-1, 4.19.146-1), libpve-storage-perl:amd64 (6.2-6, 6.2-8), pve-firmware:amd64 (3.1-2, 3.1-3), pve-qemu-kvm:amd64 (5.0.0-13, 5.1.0-3), libpve-cluster-api-perl:amd64 (6.1-8, 6.2-1), libpve-cluster-perl:amd64 (6.1-8, 6.2-1), pve-docs:amd64 (6.2-5, 6.2-6), pve-ha-manager:amd64 (3.0-9, 3.1-1), libproxmox-acme-perl:amd64 (1.0.4, 1.0.5), pve-firewall:amd64 (4.1-2, 4.1-3), pve-container:amd64 (3.1-13, 3.2-2), proxmox-backup-client:amd64 (0.8.13-1, 0.9.0-2), libx11-6:amd64 (2:1.6.7-1, 2:1.6.7-1+deb10u1), pve-cluster:amd64 (6.1-8, 6.2-1), pve-i18n:amd64 (2.1-3, 2.2-1), pve-manager:amd64 (6.2-11, 6.2-12), libpve-guest-common-perl:amd64 (3.1-2, 3.1-3), linux-image-amd64:amd64 (4.19+105+deb10u5, 4.19+105+deb10u6), libpve-common-perl:amd64 (6.2-1, 6.2-2), qemu-server:amd64 (6.2-14, 6.2-15), libproxmox-backup-qemu0:amd64 (0.6.4-1, 0.7.0-1), libx11-data:amd64 (2:1.6.7-1, 2:1.6.7-1+deb10u1), pve-kernel-helper:amd64 (6.2-5, 6.2-7), libx11-xcb1:amd64 (2:1.6.7-1, 2:1.6.7-1+deb10u1), base-files:amd64 (10.3+deb10u5, 10.3+deb10u6), proxmox-ve:amd64 (6.2-1, 6.2-2)
End-Date: 2020-10-15  10:39:20

So the problem could be somewhere else... :confused:
 
Ok, I found it.

For some reason the name of the network interface has changed after the update and because of that my MASQUERADE settings were all wrong, because it still had the old name.

That's so weird I've never seen this happen.
 
ifupdown2 2.0.1-1+pve4 don't work.
roll back or exclude ifupdown2 for updates
why do you try to install this old version ? (manually with dpkg ?)

last version is ifupdown2_3.0.0-1+pve3_all.deb , and you should install it with "apt install ifupdown2" (I don't think that dpkg is able to handle the remove of ifupdown1)
 

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!