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 v2 1/1] fix #6107: add support for legacy ipset / alias names
Date: Sat, 4 Oct 2025 14:58:44 +0200 [thread overview]
Message-ID: <175958267535.2042357.17937739446186445536.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250925122403.230867-4-s.hanreich@proxmox.com>
On Thu, 25 Sep 2025 14:24:01 +0200, Stefan Hanreich wrote:
> Change the existing firewall rule generation logic to accomodate the
> changes in the config parser, so it can deal with the legacy ipset /
> alias names.
>
> The lookup logic is the same as in pve-firewall: In guest context,
> check if it is contained in the guest config, otherwise check the
> cluster config. In cluster context, only check the cluster
> configuration.
>
> [...]
Applied, thanks!
[1/1] fix #6107: add support for legacy ipset / alias names
commit: 1a91751740b8ced17324e84e696fc5b9d9b8f034
_______________________________________________
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: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 12:23 [pve-devel] [PATCH proxmox{-ve-rs, -firewall} v2 0/3] Add " Stefan Hanreich
2025-09-25 12:23 ` [pve-devel] [PATCH proxmox-ve-rs v2 1/2] config: firewall: add support for legacy " Stefan Hanreich
2025-10-04 12:42 ` [pve-devel] applied: " Thomas Lamprecht
2025-09-25 12:24 ` [pve-devel] [PATCH proxmox-ve-rs v2 2/2] config: firewall: add support for legacy ipset names Stefan Hanreich
2025-10-04 12:43 ` [pve-devel] applied: " Thomas Lamprecht
2025-09-25 12:24 ` [pve-devel] [PATCH proxmox-firewall v2 1/1] fix #6107: add support for legacy ipset / alias names 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=175958267535.2042357.17937739446186445536.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.