From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH proxmox-firewall 0/2] Fix auto-generated IPAM ipsets in firewall
Date: Thu, 12 Feb 2026 09:48:28 +0100 [thread overview]
Message-ID: <20260212084832.63278-1-s.hanreich@proxmox.com> (raw)
proxmox-firewall did not include the auto-generated IPAM ipsets when looking up
ipsets in the firewall rule generation logic. This would cause proxmox-firewall
to fail generating a ruleset when those IPAM ipsets were included in the
ruleset. This is a regression introduced in the patch series that added support
for legacy ipset / alias names [1].
This issue was reported in the forum by a user [2].
[1] https://lore.proxmox.com/all/20250925122403.230867-1-s.hanreich@proxmox.com/
[2] https://forum.proxmox.com/threads/sdn-aliases-not-found-by-firewall.180549/
proxmox-firewall:
Stefan Hanreich (2):
firewall: chore: autoformat imports
firewall: fix ipset lookup for auto-generated ipam ipsets
proxmox-firewall/src/config.rs | 48 +++-
proxmox-firewall/src/firewall.rs | 11 +-
proxmox-firewall/tests/input/host.fw | 2 +
.../integration_tests__firewall.snap | 250 +++++++++++++++++-
4 files changed, 293 insertions(+), 18 deletions(-)
Summary over all repositories:
4 files changed, 293 insertions(+), 18 deletions(-)
--
Generated by git-murpp 0.8.0
next reply other threads:[~2026-02-12 8:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 8:48 Stefan Hanreich [this message]
2026-02-12 8:48 ` [PATCH proxmox-firewall 1/2] firewall: chore: autoformat imports Stefan Hanreich
2026-02-12 8:48 ` [PATCH proxmox-firewall 2/2] firewall: fix ipset lookup for auto-generated ipam ipsets Stefan Hanreich
2026-02-16 19:22 ` applied: [PATCH proxmox-firewall 0/2] Fix auto-generated IPAM ipsets in firewall Thomas Lamprecht
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=20260212084832.63278-1-s.hanreich@proxmox.com \
--to=s.hanreich@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox