public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Hannes Laimer <h.laimer@proxmox.com>
To: Stefan Hanreich <s.hanreich@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH pve-network] sdn: zones: look the underlay interface up correctly
Date: Wed, 9 Sep 2026 10:42:07 +0200	[thread overview]
Message-ID: <1ae4e579-51be-4373-9c0f-8a70bb33d194@proxmox.com> (raw)
In-Reply-To: <53fa0049-2e64-49a0-822a-da52f3589d45@proxmox.com>

On 2026-09-09 10:13, Stefan Hanreich wrote:
> On 9/9/26 9:53 AM, Hannes Laimer wrote:
>> The interfaces reader returns the table under a key, and the vxlan and
>> evpn zones looked their underlay interface up at the top level of the
>> reader's result, so the MTU they derive from it never applied and every
>> vnet bridge of theirs got the default or the zone's own MTU.
> 
> Ironically we independently discovered this yesterday [1], but we're a
> bit afraid of breaking setups that implicitly rely on that behavior.

:P

and agree, `ip link` would be the better source for this

> 
> [1] https://bugzilla.proxmox.com/show_bug.cgi?id=8018
> 
>> Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
>> ---
>> the alternative would be already passing `->{ifaces}`, but we'd lose the
>> options like that. i think this is better.
>>
>>  src/PVE/Network/SDN/Zones/EvpnPlugin.pm  | 3 ++-
>>  src/PVE/Network/SDN/Zones/VxlanPlugin.pm | 3 ++-
>>  2 files changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/src/PVE/Network/SDN/Zones/EvpnPlugin.pm b/src/PVE/Network/SDN/Zones/EvpnPlugin.pm
>> index 0e79707..f89decf 100644
>> --- a/src/PVE/Network/SDN/Zones/EvpnPlugin.pm
>> +++ b/src/PVE/Network/SDN/Zones/EvpnPlugin.pm
>> @@ -214,7 +214,8 @@ sub generate_sdn_config {
>>  
>>      my $mtu = 1450;
>>      if ($iface) {
>> -        $mtu = $interfaces_config->{$iface}->{mtu} - 50 if $interfaces_config->{$iface}->{mtu};
>> +        $mtu = $interfaces_config->{ifaces}->{$iface}->{mtu} - 50
>> +            if $interfaces_config->{ifaces}->{$iface}->{mtu};
>>      }
>>      $mtu = $plugin_config->{mtu} if $plugin_config->{mtu};
>>  
>> diff --git a/src/PVE/Network/SDN/Zones/VxlanPlugin.pm b/src/PVE/Network/SDN/Zones/VxlanPlugin.pm
>> index a408261..b4e743e 100644
>> --- a/src/PVE/Network/SDN/Zones/VxlanPlugin.pm
>> +++ b/src/PVE/Network/SDN/Zones/VxlanPlugin.pm
>> @@ -119,7 +119,8 @@ sub generate_sdn_config {
>>  
>>      my $mtu = 1450;
>>      if ($iface) {
>> -        $mtu = $interfaces_config->{$iface}->{mtu} - 50 if $interfaces_config->{$iface}->{mtu};
>> +        $mtu = $interfaces_config->{ifaces}->{$iface}->{mtu} - 50
>> +            if $interfaces_config->{ifaces}->{$iface}->{mtu};
>>      }
>>      $mtu = $plugin_config->{mtu} if $plugin_config->{mtu};
>>  
> 
> 
> 
> 
> 





      reply	other threads:[~2026-09-09  8:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09  7:53 [PATCH pve-network] sdn: zones: look the underlay interface up correctly Hannes Laimer
2026-09-09  8:13 ` Stefan Hanreich
2026-09-09  8:42   ` Hannes Laimer [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=1ae4e579-51be-4373-9c0f-8a70bb33d194@proxmox.com \
    --to=h.laimer@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 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