From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-firewall 1/1] fix #7232: update ports for ceph macro
Date: Tue, 27 Jan 2026 11:25:57 +0100 [thread overview]
Message-ID: <20260127102601.73960-3-s.hanreich@proxmox.com> (raw)
In-Reply-To: <20260127102601.73960-1-s.hanreich@proxmox.com>
The range of ports used by Ceph has changed since the creation of this
firewall macro. Update the macro so it reflects the new range of ports
used by Ceph [1].
[1] https://docs.ceph.com/en/latest/rados/configuration/network-config-ref/#mds-and-manager-ip-tables
Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
src/PVE/Firewall.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/PVE/Firewall.pm b/src/PVE/Firewall.pm
index 93f8c34..92cbcaa 100644
--- a/src/PVE/Firewall.pm
+++ b/src/PVE/Firewall.pm
@@ -260,7 +260,7 @@ my $pve_fw_macros = {
{ action => 'PARAM', proto => 'tcp', dport => '6789' },
# New port for protocol v2
{ action => 'PARAM', proto => 'tcp', dport => '3300' },
- { action => 'PARAM', proto => 'tcp', dport => '6800:7300' },
+ { action => 'PARAM', proto => 'tcp', dport => '6800:7568' },
],
'CVS' => [
"Concurrent Versions System pserver traffic",
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2026-01-27 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 10:25 [pve-devel] [PATCH firewall/proxmox-ve-rs 0/2] fix ports in Ceph firewall macro Stefan Hanreich
2026-01-27 10:25 ` [pve-devel] [PATCH proxmox-ve-rs 1/1] fix #7232: update ports for ceph macro Stefan Hanreich
2026-01-27 10:25 ` Stefan Hanreich [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=20260127102601.73960-3-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 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.