From: "DERUMIER, Alexandre" <Alexandre.DERUMIER@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-common 0/1] network: tap_plug: fix mtu bugs
Date: Sat, 26 Feb 2022 15:42:43 +0000 [thread overview]
Message-ID: <e46d7cd75fd2531052ee2f1c63f6e45df9855063.camel@groupe-cyllene.com> (raw)
In-Reply-To: <20220218162501.3423501-1-aderumier@odiso.com>
Any comment about this patch ?
Forum user have tested it, and it's correctly fixing his mtu problem.
Le vendredi 18 février 2022 à 17:25 +0100, Alexandre Derumier a écrit :
> a forum user have reported strange bug with ovs + mtu9000 when
> switching between 2 ovs bridge with different mtu. (1500 vs 9000)
> https://antiphishing.cetsi.fr/proxy/v3?i=cWdzUmRSM0ZiRHpoUDkxTSw3-
> 90dQgKDkqmWWemZ6js&r=WXNQOUY5VXRSNUlTdlVTThI4PzxOoz24vDyX_lRDxWFQYQjk
> Hq27xgjw3hQLoamBbuCSKIqia8FUio_zgv2Z4g&f=R0pWUVNEaUFuMTBCTlptbqOdxRIa
> EmX54Uku9_K8PFys74qKNMDYadHFvaTbTNhXBQ48X7FG7vbeJb39p0LVEQ&u=https%3A
> //forum.proxmox.com/threads/ovs-problem-with-mtu-9000-on-vms-
> assigned-to-vmbr0.105172/&k=8YLU
>
> I have found 2 bugs:
>
> 1) ovsint port mtu need to be set with ""ovs-vsctl set mtu-request"
>
> (ip link set mtu 9000 don't seem to do nothing on ovs-int port, maybe
> this have change with last ovs version.)
>
>
> fresh start of a vm 100 + firewall on ovs with mtu 9000:
>
> 153: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 9000
> qdisc pfifo_fast master fwbr100i0 state UNKNOWN group default qlen
> 1000
> link/ether 62:42:32:cc:a2:24 brd ff:ff:ff:ff:ff:ff
> 154: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
> noqueue state UP group default qlen 1000
> link/ether 46:f6:b7:95:23:86 brd ff:ff:ff:ff:ff:ff
> 155: fwln100o0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
> noqueue master fwbr100i0 state UNKNOWN group default qlen 1000
>
>
> 2) when switching between 2 bridges or ovs with differents mtu, mtu
> are not updated on existing interfaces (veth,tap, fwbr, fwnl)
>
>
> vm start : vmbr0 mtu=1500 + firewall
> -----------------------------
> 200: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500
> qdisc pfifo_fast master fwbr100i0 state UNKNOWN group default qlen
> 1000
> link/ether 62:42:32:cc:a2:24 brd ff:ff:ff:ff:ff:ff
> 206: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
> noqueue state UP group default qlen 1000
> link/ether 46:f6:b7:95:23:86 brd ff:ff:ff:ff:ff:ff
> 207: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500
> qdisc noqueue master vmbr0 state UP group default qlen 1000
> link/ether 0a:2e:f5:f4:22:e3 brd ff:ff:ff:ff:ff:ff
> 208: fwln100i0@fwpr100p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500
> qdisc noqueue master fwbr100i0 state UP group default qlen 1000
> link/ether 96:0e:94:11:c1:45 brd ff:ff:ff:ff:ff:ff
>
>
> switch to vmbr1 mtu=9000 + firewall
> --------------------------------------
>
> 200: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500
> qdisc pfifo_fast master fwbr100i0 state UNKNOWN group default qlen
> 1000
> link/ether 62:42:32:cc:a2:24 brd ff:ff:ff:ff:ff:ff
> 209: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
> noqueue state UP group default qlen 1000
> link/ether 46:f6:b7:95:23:86 brd ff:ff:ff:ff:ff:ff
> 210: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000
> qdisc noqueue master vmbr3 state UP group default qlen 1000
> link/ether 0a:2e:f5:f4:22:e3 brd ff:ff:ff:ff:ff:ff
> 211: fwln100i0@fwpr100p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000
> qdisc noqueue master fwbr100i0 state UP group default qlen 1000
> link/ether 96:0e:94:11:c1:45 brd ff:ff:ff:ff:ff:ff
>
>
>
>
> Alexandre Derumier (1):
> network: tap_plug: fix mtu
>
> src/PVE/Network.pm | 30 ++++++++++++++++++++----------
> 1 file changed, 20 insertions(+), 10 deletions(-)
>
prev parent reply other threads:[~2022-02-26 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 16:25 Alexandre Derumier
2022-02-18 16:25 ` [pve-devel] [PATCH pve-common 1/1] network: tap_plug: fix mtu Alexandre Derumier
2022-02-26 15:42 ` 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=e46d7cd75fd2531052ee2f1c63f6e45df9855063.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.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