public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: "DERUMIER, Alexandre" <Alexandre.DERUMIER@groupe-cyllene.com>
To: "pve-user@lists.proxmox.com" <pve-user@lists.proxmox.com>,
	"dziobek@hlrs.de" <dziobek@hlrs.de>
Subject: Re: [PVE-User] Proxmox VE 7.2 - Problem of understanding 'bridge-disable-mac-learning'
Date: Thu, 5 May 2022 13:24:31 +0000	[thread overview]
Message-ID: <3eace3432f6ca87b660f01390a8cf13395322e12.camel@groupe-cyllene.com> (raw)
In-Reply-To: <20220504153959.19ffadc1@rosa.proxmox.com>

mmm,looking at the git, it seem that qemu-server && pve-container patch
es to register mac address in bridge are not applied ...


[pve-devel] [PATCH V2 qemu-server 0/3] add disable bridge learning
feature
	https://lists.proxmox.com/pipermail/pve-devel/2022-March/052210.html
	
[pve-devel] [PATCH V2 pve-container 0/1] add disable bridge learning
feature
		https://lists.proxmox.com/pipermail/pve-devel/2022-March/052206.html




Le mercredi 04 mai 2022 à 15:39 +0200, Stoiko Ivanov a écrit :
> hi,
> 
> 
> On Wed, 4 May 2022 14:10:59 +0200
> Martin Dziobek <dziobek@hlrs.de> wrote:
> 
> > Dear all,
> > 
> > In the Release Notes of 7.2, it says:
> > 
> > "Administrators can now disable MAC learning on a bridge in
> > /etc/network/interfaces with the bridge-disable-mac-learning flag.
> > This reduces the number of packets flooded on all ports (for
> > unknown MAC addresses), preventing issues with certain hosting 
> > providers (for example, Hetzner), which resulted in the Proxmox VE
> > node getting disconnected"
> > 
> > where as in descriptions of how to disable mac bridge learning
> > for example on 
> > https://antiphishing.cetsi.fr/proxy/v3?i=ZUcyY1RmWEJYTXg4endZcf4pHMlLXnVUx16Ppu9iYP8&r=N3ZnQkVkbG1hOHVwcWFJNMLpdiUetyglobBNT6FebFASxxZ1q4z56SmutCfWl0tQ&f=RkdqNzdIQkFjZzVZTkZxbZ21HjwKhyMg-rZGU8E0XD_frmmy_SGxhjX_N0NdVXVt8hYCzR91DADKO1rwT7UlwQ&u=https%3A//www.xmodulo.com/disable-mac-learning-linux-bridge.html&k=YkLs
> > 
> > it says:
> > 
> > "Once MAC learning is turned off, a Linux bridge will flood every
> > incoming packet to the rest of the ports. 
> > Understand this implication before proceeding."
> > 
> > So flooding is reduced *or* increased ...
> > 
> > May someone shed a light on this ?
> I think the commit message of the relevant commit describes the
> situation
> quite well:
> https://antiphishing.cetsi.fr/proxy/v3?i=ZUcyY1RmWEJYTXg4endZcf4pHMlLXnVUx16Ppu9iYP8&r=N3ZnQkVkbG1hOHVwcWFJNMLpdiUetyglobBNT6FebFASxxZ1q4z56SmutCfWl0tQ&f=RkdqNzdIQkFjZzVZTkZxbZ21HjwKhyMg-rZGU8E0XD_frmmy_SGxhjX_N0NdVXVt8hYCzR91DADKO1rwT7UlwQ&u=https%3A//git.proxmox.com/%3Fp%3Dpve-common.git%3Ba%3Dcommit%3Bh%3D354ec8dee37d481ebae49b488349a8e932dce736&k=YkLs
> 
> it disables learning on the individual ports - but at the same time
> also
> the unicast_flood flag is set to false - see `man 8 bridge` - so I'd
> expect the combination of the 2 to work as advertised
> (and will try to rephrase the release note entry a bit too be less
> confusing)
> 
> I hope this helps!
> 
> Best regards,
> stoiko
> 
> 
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://antiphishing.cetsi.fr/proxy/v3?i=ZUcyY1RmWEJYTXg4endZcf4pHMlLXnVUx16Ppu9iYP8&r=N3ZnQkVkbG1hOHVwcWFJNMLpdiUetyglobBNT6FebFASxxZ1q4z56SmutCfWl0tQ&f=RkdqNzdIQkFjZzVZTkZxbZ21HjwKhyMg-rZGU8E0XD_frmmy_SGxhjX_N0NdVXVt8hYCzR91DADKO1rwT7UlwQ&u=https%3A//lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user&k=YkLs
> 


      reply	other threads:[~2022-05-05 13:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04 10:27 [PVE-User] Proxmox VE 7.2 released! Martin Maurer
2022-05-04 12:10 ` [PVE-User] Proxmox VE 7.2 - Problem of understanding 'bridge-disable-mac-learning' Martin Dziobek
2022-05-04 13:39   ` Stoiko Ivanov
2022-05-05 13:24     ` DERUMIER, Alexandre [this message]

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=3eace3432f6ca87b660f01390a8cf13395322e12.camel@groupe-cyllene.com \
    --to=alexandre.derumier@groupe-cyllene.com \
    --cc=dziobek@hlrs.de \
    --cc=pve-user@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal