From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Hannes Laimer <h.laimer@proxmox.com>
Subject: applied: [PATCH pve-network] sdn: zones: vxlan: set the local tunnel address explicitly
Date: Mon, 2 Nov 2026 23:51:55 +0100 [thread overview]
Message-ID: <179365989922.2007812.4485405588835907272.b4-ty@b4> (raw)
In-Reply-To: <20260925134050.754528-1-h.laimer@proxmox.com>
On Fri, 25 Sep 2026 15:40:50 +0200, Hannes Laimer wrote:
> The plugin already determines which peer address is the node's own,
> but only uses it to leave the node out of the remote list and never
> writes it as vxlan-local-tunnelip. ifupdown2 applies the first local
> tunnel address it processes in a run to every vxlan interface without
> one, so a VXLAN zone next to an EVPN zone inherits the EVPN zone's
> address, at creation and on reload as an in-place change of the live
> device. With both zones on one underlay the two addresses are the
> same. With separate underlays the zone's VTEP address lands on the
> EVPN underlay, FRR advertises the VNI with it and installs forwarding
> entries toward the peers there, and the zone's traffic moves onto the
> EVPN underlay.
>
> [...]
Applied, thanks!
[1/1] sdn: zones: vxlan: set the local tunnel address explicitly
commit: 3d14daeeb5da32ca82eb3757bbfa0a87b2ded719
prev parent reply other threads:[~2026-11-02 22:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 13:40 [PATCH pve-network] sdn: zones: vxlan: set the local tunnel address explicitly Hannes Laimer
2026-10-08 8:59 ` Gabriel Goller
2026-10-08 9:12 ` Hannes Laimer
2026-11-02 22:51 ` 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=179365989922.2007812.4485405588835907272.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=h.laimer@proxmox.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 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.