From: "Christoph Heiss" <c.heiss@proxmox.com>
To: "Gabriel Goller" <g.goller@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] applied: [PATCH perl-rs v2] fix: sdn: fabrics: always add node-ip to all fabric interfaces
Date: Wed, 29 Oct 2025 14:30:14 +0100 [thread overview]
Message-ID: <DDUUCEPONE08.3C3AADE2E7FJR@proxmox.com> (raw)
In-Reply-To: <f5pl7zgqynac5iuar36zl4o7tldytgk4t4wxpq4reuysj3ohb2@4f7r2jfxgg4j>
On Tue Oct 28, 2025 at 5:38 PM CET, Gabriel Goller wrote:
> On 28.10.2025 16:11, Thomas Lamprecht wrote:
>> On Tue, 16 Sep 2025 14:40:54 +0200, Gabriel Goller wrote:
>> > OpenFabric can handle completely unnumbered interfaces, so interfaces
>> > which don't have an ip configured. This works great in many setups, but
>> > can cause some intricate ARP issues in some specific setups.
>> >
>> > The problem
>> > ===========
>> >
>> > [...]
>>
>> Applied, thanks!
>>
>> Some unit and/or snapshot tests would be great for these things though.
>>
>> [1/1] fix: sdn: fabrics: always add node-ip to all fabric interfaces
>> commit: 80d69d9674e5527c8b96a7ca13824978270d8def
>
> Yes that's already on my todo-list. I think we need to cleanup the whole
> ifupdown2-config generation though, right now we're just throwing
> strings at it. I think @Christoph did some cleanup in his wireguard
> series IIRC?
FWIW; not anything specific with the ifupdown2 config generation, no.
(Other then some quick, generic cleanups w.r.t better handling non-FRR
fabrics.)
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-10-29 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 12:40 [pve-devel] " Gabriel Goller
2025-10-01 15:00 ` Stefan Hanreich
2025-10-02 17:04 ` Gabriel Goller
2025-10-28 12:33 ` Gabriel Goller
2025-10-28 15:11 ` [pve-devel] applied: " Thomas Lamprecht
[not found] ` <f5pl7zgqynac5iuar36zl4o7tldytgk4t4wxpq4reuysj3ohb2@4f7r2jfxgg4j>
2025-10-29 13:30 ` Christoph Heiss [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=DDUUCEPONE08.3C3AADE2E7FJR@proxmox.com \
--to=c.heiss@proxmox.com \
--cc=g.goller@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.