From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 2/3] pvesdn: add note to port isolation to use firewall in clusters
Date: Wed, 20 Nov 2024 13:02:04 +0100 [thread overview]
Message-ID: <20241120120205.163868-2-a.lauterer@proxmox.com> (raw)
In-Reply-To: <20241120120205.163868-1-a.lauterer@proxmox.com>
since port isolation is only local on the host. To get better port
isolation, the VNET firewall can be used.
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
pvesdn.adoc | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/pvesdn.adoc b/pvesdn.adoc
index 2e24dd2..1541e54 100644
--- a/pvesdn.adoc
+++ b/pvesdn.adoc
@@ -388,6 +388,10 @@ but not for the interface itself. This means guests can only send traffic to
non-isolated bridge-ports, which is the bridge itself. In order for this setting
to take effect, you need to restart the affected guest.
+NOTE: Port isolation is local to each host. Use the
+xref:pvesdn_firewall_integration[VNET Firewall] to further isolate traffic in
+the VNET across nodes. For example, DROP by default and only allow traffic from
+the IP subnet to the gateway and the vice versa.
[[pvesdn_config_subnet]]
Subnets
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-11-20 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 12:02 [pve-devel] [PATCH docs 1/3] pvesdn: add chapter reference for sdn firewall Aaron Lauterer
2024-11-20 12:02 ` Aaron Lauterer [this message]
2024-11-20 15:57 ` [pve-devel] applied: [PATCH docs 2/3] pvesdn: add note to port isolation to use firewall in clusters Thomas Lamprecht
2024-11-20 12:02 ` [pve-devel] [PATCH manager 3/3] ui: sdn firewall: add online help Aaron Lauterer
2024-11-20 12:05 ` [pve-devel] [PATCH docs 1/3] pvesdn: add chapter reference for sdn firewall Stefan Hanreich
2024-11-20 15:57 ` [pve-devel] applied: " Thomas Lamprecht
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=20241120120205.163868-2-a.lauterer@proxmox.com \
--to=a.lauterer@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.