From: Ethan Zuo <yuxuan.zuo@outlook.com>
To: pve-devel@lists.proxmox.com
Cc: Ethan Zuo <yuxuan.zuo@outlook.com>
Subject: [PATCH container 1/2] Revert "pve-firewall.service: update-alternative ip-/eb- tables to legacy versions"
Date: Thu, 12 Feb 2026 04:16:41 +0800 [thread overview]
Message-ID: <SY0P300MB0609E6899D965FC3179735259C63A@SY0P300MB0609.AUSP300.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <SY0P300MB06098F4400B1D066ABA676409C63A@SY0P300MB0609.AUSP300.PROD.OUTLOOK.COM>
This reverts commit c743e671dad7a36871b6ab8e061e4200e64a4f54.
The original commit introduced a workaround forcing the use of
legacy iptables and ebtables backends via `update-alternatives`
in the systemd service unit. This was originally required due to
critical bugs in the nftables-based variants.
As these upstream issues have been fixed and the nftables backend
is now stable and preferred in Debian, this workaround is no longer
necessary.
Signed-off-by: Ethan Zuo <yuxuan.zuo@outlook.com>
---
debian/pve-firewall.service | 3 ---
1 file changed, 3 deletions(-)
diff --git a/debian/pve-firewall.service b/debian/pve-firewall.service
index f95ce6d..63fc57f 100644
--- a/debian/pve-firewall.service
+++ b/debian/pve-firewall.service
@@ -8,9 +8,6 @@ Before=shutdown.target
Conflicts=shutdown.target
[Service]
-ExecStartPre=-/usr/bin/update-alternatives --set ebtables /usr/sbin/ebtables-legacy
-ExecStartPre=-/usr/bin/update-alternatives --set iptables /usr/sbin/iptables-legacy
-ExecStartPre=-/usr/bin/update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy
ExecStart=/usr/sbin/pve-firewall start
ExecStop=/usr/sbin/pve-firewall stop
ExecReload=/usr/sbin/pve-firewall restart
--
2.51.0
next prev parent reply other threads:[~2026-02-12 7:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 20:16 [PATCH pve-firewall 0/2] switch iptables/ebtables alternatives back to nft-based versions Ethan Zuo
2026-02-11 20:16 ` Ethan Zuo [this message]
2026-02-11 20:16 ` [PATCH container 2/2] d/postinst: reset iptables/ebtables alternatives to auto Ethan Zuo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SY0P300MB0609E6899D965FC3179735259C63A@SY0P300MB0609.AUSP300.PROD.OUTLOOK.COM \
--to=yuxuan.zuo@outlook.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.