From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 5632C1FF13B for ; Wed, 03 Jun 2026 16:30:15 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D1F93DFF3; Wed, 3 Jun 2026 16:30:07 +0200 (CEST) From: Lukas Sichert To: pve-devel@lists.proxmox.com Subject: [PATCH perl-rs v2 4/5] fabrics: bgp: enable force_forwardgin for ipv6 transit traffic Date: Wed, 3 Jun 2026 16:29:12 +0200 Message-ID: <20260603142921.91174-5-l.sichert@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260603142921.91174-1-l.sichert@proxmox.com> References: <20260603142921.91174-1-l.sichert@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1780496933253 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.328 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: JUGE2QMLX6XXJNIJ2WJAFEQIRKRSZN4V X-Message-ID-Hash: JUGE2QMLX6XXJNIJ2WJAFEQIRKRSZN4V X-MailFrom: l.sichert@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Lukas Sichert X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: In a non-full-mesh BGP-fabric 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 --- pve-rs/src/bindings/sdn/fabrics.rs | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/pve-rs/src/bindings/sdn/fabrics.rs b/pve-rs/src/bindings/sdn/fabrics.rs index 785b537..000ecb7 100644 --- a/pve-rs/src/bindings/sdn/fabrics.rs +++ b/pve-rs/src/bindings/sdn/fabrics.rs @@ -774,6 +774,14 @@ pub mod pve_rs_sdn_fabrics { writeln!(interfaces, "iface {name} inet manual")?; writeln!(interfaces, "\tip-forward 1")?; writeln!(interfaces, "\tip6-forward 1")?; + writeln!( + interfaces, + "\tpost-up echo 1 > /proc/sys/net/ipv6/conf/{name}/force_forwarding" + )?; + writeln!( + interfaces, + "\tpost-down echo 0 > /proc/sys/net/ipv6/conf/{name}/force_forwarding" + )?; // BGP unnumbered uses RAs to discover peer link-local // addresses. frr listens for them itself, but the kernel // would otherwise install RA-derived routes we don't want. -- 2.47.3