From: "Robin Christ" <robin@rchrist.io>
To: "Gabriel Goller" <g.goller@proxmox.com>,
"Robin Christ" <robin@rchrist.io>
Cc: pve-devel@lists.proxmox.com, Robin Christ <r.christ@partimus.com>
Subject: Re: [PATCH ifupdown2 4/4] bridge: Fix multiple Single VXLAN Devices in bridge not having tunnel_info applied on first run
Date: Tue, 31 Mar 2026 13:45:00 +0200 [thread overview]
Message-ID: <DHGXX6VZFRCA.BGKJERLLS628@rchrist.io> (raw)
In-Reply-To: <avw76qeb4kpbobp4i6wqw4clt2pbfnx5732ns52zjpvsfkreru@k3sgknm4ensu>
On Tue Mar 31, 2026 at 10:18 AM CEST, Gabriel Goller wrote:
> Thanks for these patches!
> If you haven't already, please sign the contribution
> agreement and send it to office@proxmox.com
> (https://pve.proxmox.com/wiki/Developer_Documentation#Software_License_and_Copyright).
On it, probably gonna send it tomorrow.
> The dry-run patches before look good, maybe @Christoph can have a look at them as well.
I noticed that in my last patch, there is a little typo in debian/patches/series as I renamed the patch file.
Should I post a new patch or can that be fixed on merge?
> About this one though: what is the use-case? we don't use SVDs and so the
> tunnel_info property is also not used AFAIK?
Not yet... ;) We (Partimus) are currently rebuilding our entire network, and we use a lot of EVPN with Proxmox.
We're probably building one of the most extreme EVPN setups you'll ever find in the wild right now, but all based on Proxmox.
We completely circumvent the existing Proxmox SDN though, as it by far doesn't fit our requirements.
TL;DR our use case for SVDs, and multiple SVDs in a single bridge: Traffic Steering.
I will drop you some details via direct e-mail.
As it seems like ifupdown2 upstream development has effectively been halted, Proxmox seemed like the best way
to file the fixes.
prev parent reply other threads:[~2026-03-31 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 21:39 [PATCH ifupdown2 0/4] Fix multiple Single VXLAN Devices in bridge and some dry-run fixes Robin Christ
2026-03-30 21:39 ` [PATCH ifupdown2 1/4] nlcache: Fix missing nodad option in addr_add_dry_run Robin Christ
2026-03-30 21:39 ` [PATCH ifupdown2 2/4] nlcache: Add missing link_set_mtu_dry_run method Robin Christ
2026-03-30 21:39 ` [PATCH ifupdown2 3/4] iproute2: Fix bridge_link_update_vni_filter for dry-run Robin Christ
2026-03-30 21:39 ` [PATCH ifupdown2 4/4] bridge: Fix multiple Single VXLAN Devices in bridge not having tunnel_info applied on first run Robin Christ
2026-03-31 8:18 ` Gabriel Goller
2026-03-31 11:45 ` Robin Christ [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=DHGXX6VZFRCA.BGKJERLLS628@rchrist.io \
--to=robin@rchrist.io \
--cc=g.goller@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=r.christ@partimus.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.