From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Alexandre Derumier <aderumier@odiso.com>
Subject: [pve-devel] applied: [PATCH V3 pve-common 1/1] network: tap_plug: fix mtu
Date: Wed, 31 Aug 2022 10:13:30 +0200 [thread overview]
Message-ID: <99ff55a8-babf-c8b1-1c2a-7fc42ce90ddf@proxmox.com> (raw)
In-Reply-To: <20220825092753.4014178-2-aderumier@odiso.com>
Am 25/08/2022 um 11:27 schrieb Alexandre Derumier:
> - ovsint port mtu need to be set with ""ovs-vsctl set mtu-request"
> - update mtu on already existing interfaces (fwbr,fwln,tap,veth)
> if existing tap|veth interface is replugged on a different mtu bridge
>
> Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
> ---
> src/PVE/Network.pm | 31 +++++++++++++++++++++----------
> 1 file changed, 21 insertions(+), 10 deletions(-)
>
>
applied, thanks!
prev parent reply other threads:[~2022-08-31 8:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 9:27 [pve-devel] [PATCH V3 pve-common 0/1] network: tap_plug: fix mtu bugs Alexandre Derumier
2022-08-25 9:27 ` [pve-devel] [PATCH V3 pve-common 1/1] network: tap_plug: fix mtu Alexandre Derumier
2022-08-31 8:13 ` Thomas Lamprecht [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=99ff55a8-babf-c8b1-1c2a-7fc42ce90ddf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox