all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Stefan Hanreich <s.hanreich@proxmox.com>
Subject: [pve-devel] applied: [PATCH container/docs/firewall/manager/qemu-server v4 0/5] proxmox firewall nftables
Date: Mon, 22 Apr 2024 14:00:57 +0200	[thread overview]
Message-ID: <464ce2d6-4aae-416b-bef2-391002906e05@proxmox.com> (raw)
In-Reply-To: <20240419094238.93874-1-s.hanreich@proxmox.com>

Am 19/04/2024 um 11:42 schrieb Stefan Hanreich:
> This patch series contains the remaining patches that are necessary for
> proxmox-firewall to work. It adds documentation as well as changes how
> firewall-bridges are created when proxmox-firewall is activated. It also patches
> pve-firewall to not generate rules when proxmox-firewall is active.
> 
> Dependencies:
> * qemu-server, pve-container & pve-manager depend on a bump of pve-firewall
> 
> Changes from v3 -> v4:
> * additionally check for the existence of proxmox-firewall bin
> * extracted checks into helper functions
> * update docs to reflect the changes in behavior
> 
> (omitted description & changes only relevant for the firewall itself)
> 
> qemu-server:
> 
> Stefan Hanreich (1):
>   firewall: add handling for new nft firewall
> 
>  vm-network-scripts/pve-bridge | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> 
> pve-container:
> 
> Stefan Hanreich (1):
>   firewall: add handling for new nft firewall
> 
>  src/PVE/LXC.pm | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> 
> pve-firewall:
> 
> Stefan Hanreich (1):
>   add configuration option for new nftables firewall
> 
>  src/PVE/Firewall.pm | 41 ++++++++++++++++++++++++++++++++---------
>  1 file changed, 32 insertions(+), 9 deletions(-)
> 
> 
> pve-manager:
> 
> Stefan Hanreich (1):
>   firewall: expose configuration option for new nftables firewall
> 
>  www/manager6/grid/FirewallOptions.js | 1 +
>  1 file changed, 1 insertion(+)
> 
> 
> pve-docs:
> 
> Stefan Hanreich (1):
>   firewall: add documentation for proxmox-firewall
> 
>  pve-firewall.adoc | 181 ++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 181 insertions(+)
> 
> 
> Summary over all repositories:
>   5 files changed, 224 insertions(+), 13 deletions(-)
> 


applied, thanks!


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


      parent reply	other threads:[~2024-04-22 12:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19  9:42 [pve-devel] " Stefan Hanreich
2024-04-19  9:42 ` [pve-devel] [PATCH qemu-server v4 1/5] firewall: add handling for new nft firewall Stefan Hanreich
2024-04-19  9:42 ` [pve-devel] [PATCH pve-container v4 2/5] " Stefan Hanreich
2024-04-19  9:42 ` [pve-devel] [PATCH pve-firewall v4 3/5] add configuration option for new nftables firewall Stefan Hanreich
2024-04-19  9:42 ` [pve-devel] [PATCH pve-manager v4 4/5] firewall: expose " Stefan Hanreich
2024-04-19  9:42 ` [pve-devel] [PATCH pve-docs v4 5/5] firewall: add documentation for proxmox-firewall Stefan Hanreich
2024-04-23  7:12   ` [pve-devel] applied: " Thomas Lamprecht
2024-04-22 12:00 ` 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=464ce2d6-4aae-416b-bef2-391002906e05@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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal