public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Lukas Sichert" <l.sichert@proxmox.com>
To: "Stefan Hanreich" <s.hanreich@proxmox.com>,
	<pve-devel@lists.proxmox.com>
Subject: Re: [PATCH perl-rs v3 3/5] fabrics: openfabric: enable force_forwarding for ipv6 transit traffic
Date: Mon, 27 Jul 2026 10:21:19 +0200	[thread overview]
Message-ID: <DK97HJ4VM8U0.1VCD7RAK79WKI@proxmox.com> (raw)
In-Reply-To: <81850371-dab2-4ac3-85a0-43478d2b020c@proxmox.com>

On 2026-06-25 11:53, Stefan Hanreich <s.hanreich@proxmox.com> wrote:

> On 6/19/26 5:40 PM, Lukas Sichert wrote:

>> 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")?;
>
> Do we need to set ip6-forward here as well? It does get set for the BGP
> fabric.

The forwarding flag is not necessary if force_forwarding is enabled to
forward packages. But the forwarding flag is currently set by ifupdown2
anyways in ifupdown2/addons/address.py:892, inside _set_bridge_forwarding().

>
>> +        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)
>>      }





  reply	other threads:[~2026-07-27  8:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-19 15:40 [PATCH docs/network/perl-rs v3 0/5] sdn: enable force_forwarding for ipv6 forwarding Lukas Sichert
2026-06-19 15:40 ` [PATCH network v3 1/5] sdn: evpn: enable force_forwarding for ipv6 forwarding to subnets Lukas Sichert
2026-06-25  9:47   ` Stefan Hanreich
2026-07-27  8:33     ` Lukas Sichert
2026-06-19 15:40 ` [PATCH network v3 2/5] sdn: simple: " Lukas Sichert
2026-06-25  9:51   ` Stefan Hanreich
2026-06-19 15:40 ` [PATCH perl-rs v3 3/5] fabrics: openfabric: enable force_forwarding for ipv6 transit traffic Lukas Sichert
2026-06-25  9:53   ` Stefan Hanreich
2026-07-27  8:21     ` Lukas Sichert [this message]
2026-06-19 15:40 ` [PATCH perl-rs v3 4/5] fabrics: bgp: " Lukas Sichert
2026-06-19 15:40 ` [PATCH docs v3 5/5] sdn: drop global ipv6 forwarding workaround from OpenFabric docs Lukas Sichert
2026-07-27 13:57 ` superseded: [PATCH docs/network/perl-rs v3 0/5] 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=DK97HJ4VM8U0.1VCD7RAK79WKI@proxmox.com \
    --to=l.sichert@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=s.hanreich@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal