From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 6BC381FF141 for ; Tue, 05 May 2026 13:21:30 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A47CC247E9; Tue, 5 May 2026 13:21:27 +0200 (CEST) Message-ID: <206b2c30-f05e-42c3-8c93-8e1b45c47be1@proxmox.com> Date: Tue, 5 May 2026 13:21:20 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: Manuel Federanko Subject: Re: [PATCH docs] pve-firewall: update list of implicit rules. To: pve-devel@lists.proxmox.com References: <20260504110438.71713-1-m.federanko@proxmox.com> Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1777979974973 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.744 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com] Message-ID-Hash: 4JOOTQE66PQUSKZUJLIP6DGS37L72YSB X-Message-ID-Hash: 4JOOTQE66PQUSKZUJLIP6DGS37L72YSB X-MailFrom: m.federanko@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On 2026-05-04 1:09 PM, Stefan Hanreich wrote: > There is also a completely separate section which describes the default > firewall ruleset in greater detail [1]. It might make sense to link to > this section and maintain the full list there? This warning could then > be reformulated a bit (just a draft): > > If you enable the firewall, traffic to all hosts will be blocked by > default - with some exceptions for traffic coming from the local network > to the WebUI, SSH and other important services. More information can be > found . > > > [1] > https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_datacenter_incoming_outgoing_drop_reject Thanks for the feedback! I just sent a v2 > On 5/4/26 1:03 PM, Manuel Federanko wrote: >> Updated the documentation note to reflect the current state of >> pve-firewall. Also added a section directing users to the macro system >> if they need additional rules. >> >> Suggested-by: Friedrich Weber >> Signed-off-by: Manuel Federanko >> --- >> pve-firewall.adoc | 11 ++++++++--- >> 1 file changed, 8 insertions(+), 3 deletions(-) >> >> diff --git a/pve-firewall.adoc b/pve-firewall.adoc >> index f04134a..df396d1 100644 >> --- a/pve-firewall.adoc >> +++ b/pve-firewall.adoc >> @@ -172,9 +172,14 @@ set the enable option here: >> enable: 1 >> ---- >> >> -IMPORTANT: If you enable the firewall, traffic to all hosts is blocked by >> -default. Only exceptions is WebGUI(8006) and ssh(22) from your local >> -network. >> +IMPORTANT: If you enable the firewall, traffic to all hosts is blocked >> +by default. The only exceptions are the WebGUI(8006), ssh(22), corosync >> +(5404:5405), VNC(5900:5999), SPICE(3128) and the migration ports >> +(60000:60050) from your local network. >> + >> +Should you have other services running which communicate over the >> +network, you will have to allow them seperately. For some common >> +services there are `macros` available. >> >> If you want to administrate your {pve} hosts from remote, you >> need to create rules to allow traffic from those remote IPs to the web >