From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
alexandre derumier <aderumier@odiso.com>
Subject: Re: [pve-devel] [PATCH pve-common] network: disable unicast flooding on tap|veth|fwln ports
Date: Wed, 15 Sep 2021 19:09:28 +0200 [thread overview]
Message-ID: <478a4600-48f4-3fe8-91ec-e2dbb27bd2c8@proxmox.com> (raw)
In-Reply-To: <790dd453ab8b0fab53942c7dd4b536d5285a3c00.camel@odiso.com>
On 15.09.21 17:33, alexandre derumier wrote:
> I have looked at other hypervisors implementations (as it don't see to
> have problem with hetzner),
>
>
> https://listman.redhat.com/archives/libvir-list/2014-December/msg00173.html
>
>
> https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-C5752084-A582-4AEA-BD5D-03FE5DBC746E.html
>
>
> Both vmware && libvirt have a mode to manually manage fdb entries in
> bridge mac table.
>
> This will work if only 1mac is behind 1 nic, so it should be an option
> (nested hypervisor for examples).
>
> but for classic vm , it could allow to disable unicast_flood &&
> learning for the tap interface, but also promisc mode on tap interface!
>
> I was think about add an option on vmbrX or vnetX directly to
> enable/disable.
As this would be on the VM tap devices it would sound somewhat reasonable to
have it as per vNIC setting, but naturally it would then be a bit annoying to
change for all; a tradeoff could be to allow setting the default value per
bridge, node or datacenter (I'd do only one of those).
What do you think?
>
> I'm going to do tests, testing vlan aware && live migration too.
great, thanks for your work on this!
next prev parent reply other threads:[~2021-09-15 17:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 0:26 Alexandre Derumier
2021-09-14 6:32 ` alexandre derumier
2021-09-15 15:33 ` alexandre derumier
2021-09-15 17:09 ` Thomas Lamprecht [this message]
2021-09-16 21:48 ` alexandre derumier
2022-01-14 10:51 ` Wolfgang Bumiller
2022-01-14 11:23 ` Josef Johansson
2022-01-28 3:39 ` Josef Johansson
2022-01-14 16:50 ` DERUMIER, Alexandre
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=478a4600-48f4-3fe8-91ec-e2dbb27bd2c8@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=aderumier@odiso.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.