From: Gabriel Goller <g.goller@proxmox.com>
To: Lukas Sichert <l.sichert@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH perl-rs 3/4] fabrics: openfabric: enable force_forwarding for ipv6 transit traffic
Date: Tue, 2 Jun 2026 11:03:28 +0200 [thread overview]
Message-ID: <mrzug64wpqbvtmogxsdehvbyrzaq64oeguvrbeqeyt4jbcq56c@zmehlwv6njm7> (raw)
In-Reply-To: <20260601151550.118977-4-l.sichert@proxmox.com>
On 01.06.2026 17:15, Lukas Sichert wrote:
> In a non-full-mesh OpenFabric setup, nodes may need to relay traffic
> between peers that are not directly connected. This requires forwarding
> ipv6 packets between fabric bridges. With the addition of
> 'force_forwarding' to the Linux kernel, this can be done without
> enabling 'all.forwarding', which disables Router Advertisements.
>
> Configure fabric bridges with the required 'post-up'/'post-down'
> commands to enable 'force_forwarding'.
>
> Signed-off-by: Lukas Sichert <l.sichert@proxmox.com>
> ---
> pve-rs/src/bindings/sdn/fabrics.rs | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/pve-rs/src/bindings/sdn/fabrics.rs b/pve-rs/src/bindings/sdn/fabrics.rs
> index f96b6b1..785b537 100644
> --- a/pve-rs/src/bindings/sdn/fabrics.rs
> +++ b/pve-rs/src/bindings/sdn/fabrics.rs
> @@ -596,6 +596,16 @@ pub mod pve_rs_sdn_fabrics {
> 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"
> + )?;
> + writeln!(
> + interface,
> + "\tpost-down echo 0 > /proc/sys/net/ipv6/conf/{name}/force_forwarding"
> + )?;
> + }
>
> Ok(interface)
> }
The bgp fabric also needs force_forwarding AFAIK. @Hannes?
Also I just noticed on the bgp fabric we put ipv6 addresses in ifupdown2 inet
blocks (instead of inet6) -- shouldn't cause any problems though.
next prev parent reply other threads:[~2026-06-02 9:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 15:15 [PATCH docs/network/perl-rs 0/4] sdn: enable force_forwarding for ipv6 forwarding Lukas Sichert
2026-06-01 15:15 ` [PATCH network 1/4] sdn: evpn: enable force_forwarding for ipv6 forwarding to subnets Lukas Sichert
2026-06-01 15:15 ` [PATCH network 2/4] sdn: simple: " Lukas Sichert
2026-06-01 15:15 ` [PATCH perl-rs 3/4] fabrics: openfabric: enable force_forwarding for ipv6 transit traffic Lukas Sichert
2026-06-02 9:03 ` Gabriel Goller [this message]
2026-06-02 9:11 ` Hannes Laimer
2026-06-01 15:15 ` [PATCH docs 4/4] sdn: drop global IPv6 forwarding workaround from OpenFabric docs Lukas Sichert
2026-06-02 9:01 ` Gabriel Goller
2026-06-03 15:25 ` superseded: [PATCH docs/network/perl-rs 0/4] sdn: enable force_forwarding for ipv6 forwarding Lukas Sichert
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=mrzug64wpqbvtmogxsdehvbyrzaq64oeguvrbeqeyt4jbcq56c@zmehlwv6njm7 \
--to=g.goller@proxmox.com \
--cc=l.sichert@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.