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 network v3 1/5] sdn: evpn: enable force_forwarding for ipv6 forwarding to subnets
Date: Mon, 27 Jul 2026 10:33:30 +0200	[thread overview]
Message-ID: <DK97QUP9PLZE.2V260QNGEKVN5@proxmox.com> (raw)
In-Reply-To: <f7dbcb5b-0965-4198-9547-a86d662a4f14@proxmox.com>

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

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

>> @@ -333,6 +347,15 @@ sub generate_sdn_config {
>>              push @iface_config, "bridge_fd 0";
>>              push @iface_config, "mtu $mtu" if $mtu;
>>              push @iface_config, "vrf $vrf_iface";
>> +
>> +            if ($enable_forward_v6) {
>> +                push @iface_config, 'ip6-forward on';
>
> Is there a reason why there's now an ip6-forward statement on the vrfbr
> as well? Is this to get router-behavior on the vrfbr as well (which was
> previously the case because of the global setting?). Would be good to
> have a clearer explanation for why this is needed in the commit message.

You are right, it is unnecessary. I will remove it in a v4.

>> +
>> +                push @iface_config,
>> +                    "post-up echo 1 > /proc/sys/net/ipv6/conf/$brvrf/force_forwarding";
>> +                push @iface_config,
>> +                    "post-down echo 0 > /proc/sys/net/ipv6/conf/$brvrf/force_forwarding";
>> +            }
>>              push(@{ $config->{$brvrf} }, @iface_config) if !$config->{$brvrf};
>>          }
>>  





  reply	other threads:[~2026-07-27  8:33 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 [this message]
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
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=DK97QUP9PLZE.2V260QNGEKVN5@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