From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stefan Hanreich <s.hanreich@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-network] fix #5324: non vlanaware zone: add mtu to veth links
Date: Fri, 15 Nov 2024 15:58:13 +0100 [thread overview]
Message-ID: <2bf44af9-b3bd-4b25-b22f-34ea48ccc96b@proxmox.com> (raw)
In-Reply-To: <c834282b-608c-4e1e-99ff-e236f0cba692@proxmox.com>
Am 15.11.24 um 14:44 schrieb Stefan Hanreich:
>> Shouldn't we try to get the MTU of the bridge when it's set to 'auto'
>> and then setup the other interfaces accordingly? Or am I
>> misunderstanding what 'auto' does?
>
> While this is still an issue, it at least makes the MTU work if it is
> explicitly set, we can add the functionality for auto in a subsequent patch.
>
so should this be applied as is for now?
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-11-15 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 17:01 Alexandre Derumier
2024-04-04 13:58 ` Stefan Hanreich
2024-11-15 13:44 ` Stefan Hanreich
2024-11-15 14:58 ` Thomas Lamprecht [this message]
2024-11-15 15:04 ` Stefan Hanreich
2024-11-15 15:08 ` [pve-devel] applied: " Thomas Lamprecht
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=2bf44af9-b3bd-4b25-b22f-34ea48ccc96b@proxmox.com \
--to=t.lamprecht@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