From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id E85EA8DAE2 for ; Wed, 9 Nov 2022 15:19:25 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id C8C3F1D102 for ; Wed, 9 Nov 2022 15:19:25 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Wed, 9 Nov 2022 15:19:25 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id D65EE4308A for ; Wed, 9 Nov 2022 15:19:18 +0100 (CET) Message-ID: Date: Wed, 9 Nov 2022 15:19:17 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.0 To: pve-devel@lists.proxmox.com References: <20220824162644.1632804-1-aderumier@odiso.com> <20220824162644.1632804-4-aderumier@odiso.com> Content-Language: en-US From: Mira Limbeck In-Reply-To: <20220824162644.1632804-4-aderumier@odiso.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.261 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -0.001 Looks like a legit reply (A) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [qemuserver.pm] Subject: Re: [pve-devel] [PATCH V3 qemu-server 1/3] tap_plug: add support for bridge disable learning X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2022 14:19:26 -0000 On 8/24/22 18:26, Alexandre Derumier wrote: > This disabling mac learning && unicast flood for the tap interface > > for vmstart, we don't add mac directly to fdb. > We set it latter if it's a migration or a fresh start. > > for nic hotplug, we directly add mac to fdb > > Signed-off-by: Alexandre Derumier > --- > PVE/QemuServer.pm | 8 +++++++- > vm-network-scripts/pve-bridge | 6 +++++- > 2 files changed, 12 insertions(+), 2 deletions(-) > > diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm > index c706653..0114d06 100644 > --- a/PVE/QemuServer.pm > +++ b/PVE/QemuServer.pm > @@ -5137,8 +5137,14 @@ sub vmconfig_update_net { > > if ($have_sdn) { > PVE::Network::SDN::Zones::tap_plug($iface, $newnet->{bridge}, $newnet->{tag}, $newnet->{firewall}, $newnet->{trunks}, $newnet->{rate}); > + PVE::Network::SDN::Zones::add_bridge_fdb($iface, $newnet->{macaddr}, $newnet->{bridge}, $newnet->{firewall}); > } else { > - PVE::Network::tap_plug($iface, $newnet->{bridge}, $newnet->{tag}, $newnet->{firewall}, $newnet->{trunks}, $newnet->{rate}); > + my $interfaces_config = PVE::INotify::read_file('interfaces'); > + my $bridge = $newnet->{bridge}; > + my $opts = {}; > + $opts->{learning} = 0 if $interfaces_config->{ifaces}->{$bridge} && $interfaces_config->{ifaces}->{$bridge}->{'bridge-disable-mac-learning'}; > + PVE::Network::tap_plug($iface, $newnet->{bridge}, $newnet->{tag}, $newnet->{firewall}, $newnet->{trunks}, $newnet->{rate}, $opts); > + PVE::Network::add_bridge_fdb($iface, $newnet->{macaddr}, $newnet->{firewall}) if defined($opts->{learning}) && !$opts->{learning}; > } > } elsif (safe_num_ne($oldnet->{rate}, $newnet->{rate})) { > # Rate can be applied on its own but any change above needs to > diff --git a/vm-network-scripts/pve-bridge b/vm-network-scripts/pve-bridge > index d37ce33..38cf2f6 100755 > --- a/vm-network-scripts/pve-bridge > +++ b/vm-network-scripts/pve-bridge > @@ -47,8 +47,12 @@ if ($have_sdn) { > PVE::Network::SDN::Zones::tap_create($iface, $net->{bridge}); > PVE::Network::SDN::Zones::tap_plug($iface, $net->{bridge}, $net->{tag}, $net->{firewall}, $net->{trunks}, $net->{rate}); > } else { > + my $interfaces_config = PVE::INotify::read_file('interfaces'); > + my $bridge = $net->{bridge}; > + my $opts = {}; > + $opts->{learning} = 0 if $interfaces_config->{ifaces}->{$bridge} && $interfaces_config->{ifaces}->{$bridge}->{'bridge-disable-mac-learning'}; > PVE::Network::tap_create($iface, $net->{bridge}); > - PVE::Network::tap_plug($iface, $net->{bridge}, $net->{tag}, $net->{firewall}, $net->{trunks}, $net->{rate}); > + PVE::Network::tap_plug($iface, $net->{bridge}, $net->{tag}, $net->{firewall}, $net->{trunks}, $net->{rate}, $opts); > } Why not add the bridge in the pve-bridge script as well? This way there would be no need for patch 2 for qemu-server since we always add the MAC address to the FDB whenever the tap device is plugged. If we then remove it in the pve-bridgedown script, there should be no need for patch 3, right?