On Tue, 12 Nov 2024 16:54:25 +0100 Stefan Hanreich <s.hanre...@proxmox.com> wrote:
> Signed-off-by: Stefan Hanreich <s.hanre...@proxmox.com> > --- > pvesdn.adoc | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/pvesdn.adoc b/pvesdn.adoc > index 39de80f..b1f2578 100644 > --- a/pvesdn.adoc > +++ b/pvesdn.adoc > @@ -383,6 +383,11 @@ Tag:: The unique VLAN or VXLAN ID > VLAN Aware:: Enables vlan-aware option on the interface, enabling > configuration > in the guest. > > +Isolate Ports:: Sets the isolated flag for all members of this port, except > for > +the bridge port. This means that every port can only send traffic to the > bridge > +port. In order for this setting to take effect, you need to restart the VMs > +that have interfaces on the VNet. > + Reading through the VNet docs - I'd rename bridge port to 'interface' and members to guest ports. - maybe like this: ``` Isolate Ports:: Sets the isolated flag for all guest ports of this interface, but not for the interface itself. This means that guests cannot send traffic to each other. In order for this setting to take effect, you need to restart the affected guest. ``` > > [[pvesdn_config_subnet]] > Subnets _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
