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 pve-network v2 3/4] vnets : add ports isolation
Date: Mon, 18 Nov 2024 19:46:37 +0100 [thread overview]
Message-ID: <53aad254-0a50-4138-9143-f8b9333559c2@proxmox.com> (raw)
In-Reply-To: <20241112155425.196432-3-s.hanreich@proxmox.com>
Am 12.11.24 um 16:54 schrieb Stefan Hanreich:
> From: Alexandre Derumier via pve-devel <pve-devel@lists.proxmox.com>
>
> Add support for bridge ports isolation
> https://github.com/torvalds/linux/commit/7d850abd5f4edb1b1ca4b4141a4453305736f564
>
> This allow to drop traffic between all ports having isolation enabled
> on the local bridge, but allow traffic with non isolated ports.
>
> Here,we isolate traffic between vms but allow traffic coming from outside.
>
> Main usage is for layer3 routed or natted setup, but some users have requested it
> for layer2/bridge network with proxy arp.
> So we can enable it at vnet level.
>
> Signed-off-by: Alexandre Derumier <alexandre.derumier@groupe-cyllene.com>
> [ SH: improve option naming and description slightly ]
> Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
> ---
> src/PVE/Network/SDN/VnetPlugin.pm | 5 +++++
> src/PVE/Network/SDN/Zones/Plugin.pm | 1 +
> 2 files changed, 6 insertions(+)
>
>
applied this one a bit ago, before getting the review mail from Stoiko, so
without his trailers, thanks to all involved nonetheless!
_______________________________________________
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-18 18:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 15:54 [pve-devel] [PATCH pve-common v2 1/4] tap_plug: add support for bridge port isolation Stefan Hanreich
2024-11-12 15:54 ` [pve-devel] [PATCH pve-manager v2 2/4] sdn: vnet: add isolate-ports option Stefan Hanreich
2024-11-19 16:02 ` [pve-devel] applied: " Thomas Lamprecht
2024-11-12 15:54 ` [pve-devel] [PATCH pve-network v2 3/4] vnets : add ports isolation Stefan Hanreich
2024-11-18 18:46 ` Thomas Lamprecht [this message]
2024-11-12 15:54 ` [pve-devel] [PATCH pve-docs v2 4/4] sdn: add documentation for isolated ports option Stefan Hanreich
2024-11-18 18:52 ` Stoiko Ivanov
2024-11-19 10:06 ` Hannes Dürr
2024-11-19 10:19 ` Stoiko Ivanov
2024-11-19 10:34 ` Hannes Dürr
2024-11-12 16:20 ` [pve-devel] applied: [PATCH pve-common v2 1/4] tap_plug: add support for bridge port isolation Thomas Lamprecht
2024-11-18 18:45 ` [pve-devel] " Stoiko Ivanov
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=53aad254-0a50-4138-9143-f8b9333559c2@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.