From: Alexandre Derumier <aderumier@odiso.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH frr 0/2] bump to frr 8.2.2 + netlink fix
Date: Wed, 27 Apr 2022 17:04:54 +0200 [thread overview]
Message-ID: <20220427150456.1707292-1-aderumier@odiso.com> (raw)
Hi,
2 users have reported problems when vlan-aware bridge are presents.
Seem that frr is not parsing correctly netlink message because
currently frr use static buffer size, and netlink message can be
too big when a lot of vlan are defined.
https://forum.proxmox.com/threads/implementations-of-sdn-networking.99628/
https://github.com/FRRouting/frr/issues/10404
This is fixed with:
https://github.com/FRRouting/frr/pull/10482
only available in master.
This patches serie update frr to 8.2.2 + this PR.
I'm running it in production since 1 week, works fine.
This need to update the proxmox frr mirror to frr-8.2.2 tag:
https://github.com/FRRouting/frr/tree/frr-8.2.2
Alexandre Derumier (2):
add frr zebra buffering patches
bump frr to 8.2.2
debian/changelog | 6 +
debian/patches/frr/0001-zebra-buffering.patch | 92 ++++
debian/patches/frr/0002-zebra-buffering.patch | 420 ++++++++++++++++++
debian/patches/frr/0003-zebra-buffering.patch | 283 ++++++++++++
debian/patches/series | 3 +
5 files changed, 804 insertions(+)
create mode 100644 debian/patches/frr/0001-zebra-buffering.patch
create mode 100644 debian/patches/frr/0002-zebra-buffering.patch
create mode 100644 debian/patches/frr/0003-zebra-buffering.patch
--
2.30.2
next reply other threads:[~2022-04-27 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 15:04 Alexandre Derumier [this message]
2022-04-27 15:04 ` [pve-devel] [PATCH frr 1/2] add frr zebra buffering patches Alexandre Derumier
2022-04-27 15:04 ` [pve-devel] [PATCH frr 2/2] bump frr to 8.2.2 Alexandre Derumier
2022-04-27 18:16 ` [pve-devel] applied: [PATCH frr 0/2] bump to frr 8.2.2 + netlink fix 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=20220427150456.1707292-1-aderumier@odiso.com \
--to=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