From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Stefan Hanreich <s.hanreich@proxmox.com>
Subject: [pve-devel] applied: [PATCH proxmox-firewall 0/3] create ipsets with auto-merge option enabled
Date: Sat, 4 Oct 2025 14:58:40 +0200 [thread overview]
Message-ID: <175958267536.2042357.7714728106538562502.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250925161250.436548-1-s.hanreich@proxmox.com>
On Thu, 25 Sep 2025 18:12:44 +0200, Stefan Hanreich wrote:
> nftables interval sets do not merge overlapping / adjacent CIDRs / ranges by
> default. Instead, nftables errors out, refusing to insert new set elements. This
> was a problem with proxmox-firewall, since ip sets with overlapping entries
> could cause the firewall daemon to refuse working.
>
> Since v1.1.0 [1] (and therefore, Debian trixie) the nftables json interface
> supports setting the auto-merge options for sets.
>
> [...]
Applied, thanks!
[1/3] nftables: add support for auto-merge set option
commit: ed03912fd5c596ec7eb2659a5b89ef23ec9302b8
[2/3] firewall: set auto-merge flag for ipsets
commit: fce33f8ca6784afa69a662f8401c7946c2c221c2
[3/3] firewall: tests: regenerate snapshot
NOTE: squashed into former commit to avoid breaking build temporarily
without reason.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-10-04 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 16:12 [pve-devel] " Stefan Hanreich
2025-09-25 16:12 ` [pve-devel] [PATCH proxmox-firewall 1/3] nftables: add support for auto-merge set option Stefan Hanreich
2025-09-25 16:12 ` [pve-devel] [PATCH proxmox-firewall 2/3] firewall: set auto-merge flag for ipsets Stefan Hanreich
2025-09-25 16:12 ` [pve-devel] [PATCH proxmox-firewall 3/3] firewall: tests: regenerate snapshot Stefan Hanreich
2025-10-04 12:58 ` Thomas Lamprecht [this message]
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=175958267536.2042357.7714728106538562502.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@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.