all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-firewall v2 03/12] firewall: dump configs locally after applying
Date: Thu,  1 Oct 2026 14:26:16 +0200	[thread overview]
Message-ID: <20261001122625.348730-4-a.bied-charreton@proxmox.com> (raw)
In-Reply-To: <20261001122625.348730-1-a.bied-charreton@proxmox.com>

... and remove them when the firewall is disabled in the config or the
daemon is stopped.

The firewall config lives on pmxcfs, which is only available once
pve-cluster is up, i.e. well after the network. To be able to restore
rules before that, dump the config files needed to recompile the ruleset
(cluster.fw, host.fw and the SDN config as sdn.json) to a local
directory after every successful apply. The guest configs are not
dumped, since pve-guests does not start until the actual firewall daemon
is running.

The last dumped content is cached per file, so the daemon only writes
when something changed since the last dump, or if the dump file does not
exist at all.

Ownership of the dumps is keyed on the nftables option in the host
config. If the firewall is disabled cluster-wide, the dumps are removed.
If nftables is enabled, they are left in place, since proxmox-firewall
owns them in that case.

The dumps are also removed when the daemon is stopped, to prevent a
ruleset restored at boot from living forever if no daemon starts
afterwards.

Signed-off-by: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
Reviewed-by: Thomas Ellmenreich <t.ellmenreich@proxmox.com>
Tested-by: Thomas Ellmenreich <t.ellmenreich@proxmox.com>
---
 debian/dirs                     |  1 +
 src/PVE/Firewall.pm             | 80 +++++++++++++++++++++++++++++----
 src/PVE/Service/pve_firewall.pm |  5 ++-
 3 files changed, 77 insertions(+), 9 deletions(-)

diff --git a/debian/dirs b/debian/dirs
index c9e3b54..e472f56 100644
--- a/debian/dirs
+++ b/debian/dirs
@@ -1 +1,2 @@
 /var/lib/pve-firewall
+/var/lib/pve/firewall
diff --git a/src/PVE/Firewall.pm b/src/PVE/Firewall.pm
index 592e5fe..81901e3 100644
--- a/src/PVE/Firewall.pm
+++ b/src/PVE/Firewall.pm
@@ -17,6 +17,7 @@ use Storable qw(dclone);
 use PVE::Cluster;
 use PVE::Corosync;
 use PVE::Exception qw(raise raise_param_exc);
+use PVE::File;
 use PVE::INotify;
 use PVE::JSONSchema qw(register_standard_option get_standard_option);
 use PVE::Network;
@@ -32,6 +33,8 @@ my $pvefw_conf_dir = "/etc/pve/firewall";
 my $clusterfw_conf_filename = "$pvefw_conf_dir/cluster.fw";
 my $vnetfw_conf_dir = "/etc/pve/sdn/firewall";
 
+my $dump_dir = '/var/lib/pve/firewall';
+
 # dynamically include PVE::QemuServer and PVE::LXC
 # to avoid dependency problems
 my $have_qemu_server;
@@ -4231,7 +4234,7 @@ sub load_sdn_conf {
     return $sdn_config // $empty_sdn_config;
 }
 
-sub save_clusterfw_conf {
+sub serialize_clusterfw_conf {
     my ($cluster_conf) = @_;
 
     my $raw = '';
@@ -4266,11 +4269,21 @@ sub save_clusterfw_conf {
         }
     }
 
+    return $raw;
+}
+
+sub save_clusterfw_conf {
+    my ($cluster_conf, $filename) = @_;
+
+    $filename = $clusterfw_conf_filename if !defined($filename);
+
+    my $raw = serialize_clusterfw_conf($cluster_conf);
+
     if ($raw) {
         mkdir $pvefw_conf_dir;
-        PVE::Tools::file_set_contents($clusterfw_conf_filename, $raw);
+        PVE::Tools::file_set_contents($filename, $raw);
     } else {
-        unlink $clusterfw_conf_filename;
+        unlink($filename);
     }
 }
 
@@ -4294,11 +4307,8 @@ sub load_hostfw_conf {
     return generic_fw_config_parser($filename, $cluster_conf, $empty_conf, 'host');
 }
 
-sub save_hostfw_conf {
-    my ($hostfw_conf, $filename) = @_;
-
-    $filename = $hostfw_conf_filename if !defined($filename);
-
+sub serialize_hostfw_conf {
+    my ($hostfw_conf) = @_;
     my $raw = '';
 
     my $options = $hostfw_conf->{options};
@@ -4311,6 +4321,16 @@ sub save_hostfw_conf {
         $raw .= "\n";
     }
 
+    return $raw;
+}
+
+sub save_hostfw_conf {
+    my ($hostfw_conf, $filename) = @_;
+
+    $filename = $hostfw_conf_filename if !defined($filename);
+
+    my $raw = serialize_hostfw_conf($hostfw_conf);
+
     if ($raw) {
         PVE::Tools::file_set_contents($filename, $raw);
     } else {
@@ -5432,6 +5452,14 @@ sub remove_pvefw_chains {
 
 }
 
+sub delete_dumps {
+
+    unlink "$dump_dir/cluster.fw";
+    unlink "$dump_dir/host.fw";
+    unlink "$dump_dir/sdn.json";
+
+}
+
 sub remove_pvefw_chains_iptables {
     my ($iptablescmd, $table) = @_;
 
@@ -5530,21 +5558,57 @@ sub init {
     # load required modules here
 }
 
+my $dump_cache = {};
+
+sub dump_if_changed {
+    my ($f, $data) = @_;
+    return if -f $f && defined($dump_cache->{$f}) && $dump_cache->{$f} eq $data;
+    PVE::File::file_set_contents($f, $data);
+    $dump_cache->{$f} = $data;
+    syslog('info', "dumped $f\n");
+}
+
+# The cache is only filled once this daemon wrote the dumps, i.e. while it owns them.
+sub delete_dumps_if_owned {
+    delete_dumps() if $dump_cache->%*;
+}
+
 sub update {
     my $code = sub {
+        my $cfw_dump_path = "$dump_dir/cluster.fw";
+        my $hfw_dump_path = "$dump_dir/host.fw";
+        my $sdn_dump_path = "$dump_dir/sdn.json";
 
         my $cluster_conf = load_clusterfw_conf();
         my $hostfw_conf = load_hostfw_conf($cluster_conf);
 
         if (!is_enabled_and_not_nftables($cluster_conf, $hostfw_conf)) {
             PVE::Firewall::remove_pvefw_chains();
+            $dump_cache = {};
+            # disabled in config: drop stale dumps so the pre-network restore does not resurrect a
+            # disabled ruleset. leave them in nftables mode, since in that case proxmox-firewall
+            # owns the dump directory.
+            delete_dumps() if !$cluster_conf->{options}->{enable};
             return;
         }
 
+        # compile() rewrites rule actions in-place. snapshot the untouched configs now for the
+        # post-apply boot-time dump.
+        my ($cfw_dump, $hfw_dump) = (dclone($cluster_conf), dclone($hostfw_conf));
+
         my ($ruleset, $ipset_ruleset, $rulesetv6, $ebtables_ruleset) =
             compile($cluster_conf, $hostfw_conf);
 
         apply_ruleset($ruleset, $hostfw_conf, $ipset_ruleset, $rulesetv6, $ebtables_ruleset);
+
+        eval {
+            mkdir($dump_dir);
+            chmod(0700, $dump_dir);
+            dump_if_changed($cfw_dump_path, serialize_clusterfw_conf($cfw_dump));
+            dump_if_changed($hfw_dump_path, serialize_hostfw_conf($hfw_dump));
+            dump_if_changed($sdn_dump_path, JSON->new->utf8->canonical->encode($cfw_dump->{sdn}));
+        };
+        syslog('err', "could not persist firewall configs at $dump_dir: $@\n") if $@;
     };
 
     run_locked($code);
diff --git a/src/PVE/Service/pve_firewall.pm b/src/PVE/Service/pve_firewall.pm
index 95901a5..f9fa1dd 100755
--- a/src/PVE/Service/pve_firewall.pm
+++ b/src/PVE/Service/pve_firewall.pm
@@ -51,7 +51,10 @@ sub shutdown {
 
     syslog('info', "clear PVE-generated firewall rules");
 
-    eval { PVE::Firewall::remove_pvefw_chains(); };
+    eval {
+        PVE::Firewall::remove_pvefw_chains();
+        PVE::Firewall::delete_dumps_if_owned();
+    };
     warn $@ if $@;
 
     $self->exit_daemon(0);
-- 
2.47.3





  parent reply	other threads:[~2026-10-01 12:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 12:26 [RFC firewall/manager/proxmox{,-firewall} v2 00/12] fix #5759: keep firewall rules up across boot and shutdown Arthur Bied-Charreton
2026-10-01 12:26 ` [PATCH pve-manager v2 01/12] network interface pinning: write new firewall config to local dir Arthur Bied-Charreton
2026-10-01 12:26 ` [PATCH pve-firewall v2 02/12] firewall: config: sort OPTIONS when serializing Arthur Bied-Charreton
2026-10-01 12:26 ` Arthur Bied-Charreton [this message]
2026-10-01 12:26 ` [PATCH pve-firewall v2 04/12] fix #5759: firewall: do not remove chains when host is shutting down Arthur Bied-Charreton
2026-10-01 12:26 ` [PATCH pve-firewall v2 05/12] firewall: add restore command Arthur Bied-Charreton
2026-10-01 12:26 ` [PATCH pve-firewall v2 06/12] fix #5759: firewall: restore from dumped config before network-pre Arthur Bied-Charreton
2026-10-01 12:26 ` [PATCH proxmox v2 07/12] systemd: systemctl: add is-system-running helper Arthur Bied-Charreton
2026-10-01 12:26 ` [PATCH proxmox-firewall v2 08/12] firewall: fix clippy warnings Arthur Bied-Charreton
2026-10-01 12:26 ` [PATCH proxmox-firewall v2 09/12] fix #5759: firewall: do not clear rules on system shutdown Arthur Bied-Charreton
2026-10-01 12:26 ` [PATCH proxmox-firewall v2 10/12] firewall: dump config to local directory after apply Arthur Bied-Charreton
2026-10-01 12:26 ` [PATCH proxmox-firewall v2 11/12] firewall: add restore command Arthur Bied-Charreton
2026-10-01 12:26 ` [PATCH proxmox-firewall v2 12/12] fix #5759: firewall: restore from dumped config before network-pre Arthur Bied-Charreton

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=20261001122625.348730-4-a.bied-charreton@proxmox.com \
    --to=a.bied-charreton@proxmox.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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal