From: "Lukas Sichert" <l.sichert@proxmox.com>
To: "Hannes Laimer" <h.laimer@proxmox.com>,
"Lukas Sichert" <l.sichert@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH perl-rs v4 3/6] fabrics: openfabric: enable force_forwarding for ipv6 transit traffic
Date: Fri, 16 Oct 2026 17:38:35 +0200 [thread overview]
Message-ID: <DM6DIG3FPYS6.I5M2777SP04X@proxmox.com> (raw)
In-Reply-To: <aovyQKZ_X5Wh3XcQ@nana.intra.proxmox.com>
Thanks for the response comments inline:
On 2026-08-24 09:27, Hannes Laimer <h.laimer@proxmox.com> wrote:
> On 2026-07-27 15:55, Lukas Sichert wrote:
>> writeln!(interface, "\tlink-type {link_type}")?;
>> }
>> writeln!(interface, "\tip-forward 1")?;
>> + if cidr.is_ipv6() {
>> + writeln!(
>> + interface,
>> + "\tpost-up echo 1 > /proc/sys/net/ipv6/conf/{name}/force_forwarding"
>> + )?;
>
> this ends up on the dummy interfaces, but that never actually get
> traffic, this should be on the underlaying interfaces the fabric is
> configured on
get_interfaces_etc_network_config() calls render_dummy_interfaces() for
the dummies, and render_interface() directly for each interface listed
in the fabric node section of /etc/pve/sdn/fabrics.cfg. The underlying
bridge is listed there, e.g.:
openfabric_node: openfab_pve1-cluster
interfaces name=vmbr12,ip6=fd10:12::2/64
ip6 fd44::1
So I think the underlying bridge does receive the stanza, but please
correct me if I'm wrong.
You are right that render_dummy_interfaces() also goes through
render_interface(), which is pointless there. I will guard it with
"link_type != Some("dummy")" in the next version.
>> + writeln!(
>> + interface,
>> + "\tpost-down echo 0 > /proc/sys/net/ipv6/conf/{name}/force_forwarding"
>> + )?;
>> + }
next prev parent reply other threads:[~2026-10-16 15:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 13:55 [PATCH docs/manager/network/perl-rs v4 0/6] sdn: enable force_forwarding for ipv6 forwarding Lukas Sichert
2026-07-27 13:55 ` [PATCH network v4 1/6] sdn: evpn: enable force_forwarding for ipv6 forwarding to subnets Lukas Sichert
2026-08-24 7:23 ` Hannes Laimer
2026-10-16 16:33 ` Lukas Sichert
2026-07-27 13:55 ` [PATCH network v4 2/6] sdn: simple: " Lukas Sichert
2026-07-27 13:55 ` [PATCH perl-rs v4 3/6] fabrics: openfabric: enable force_forwarding for ipv6 transit traffic Lukas Sichert
2026-08-24 7:27 ` Hannes Laimer
2026-10-16 15:38 ` Lukas Sichert [this message]
2026-07-27 13:55 ` [PATCH perl-rs v4 4/6] fabrics: bgp: " Lukas Sichert
2026-07-27 13:55 ` [PATCH manager v4 5/6] ui: sdn: remove IPv6 forwarding hint from fabric edit window Lukas Sichert
2026-07-27 13:55 ` [PATCH docs v4 6/6] sdn: drop global ipv6 forwarding workaround from OpenFabric docs Lukas Sichert
2026-08-24 7:33 ` [PATCH docs/manager/network/perl-rs v4 0/6] sdn: enable force_forwarding for ipv6 forwarding Hannes Laimer
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=DM6DIG3FPYS6.I5M2777SP04X@proxmox.com \
--to=l.sichert@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.