Netdev List
 help / color / mirror / Atom feed
From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Fernando Fernandez Mancera <fmancera@suse.de>, netdev@vger.kernel.org
Cc: dsahern@kernel.org, stephen@networkplumber.org,
	davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH iproute2-next] iplink: add support for setting IPv4 devconf parameters
Date: Wed, 3 Jun 2026 14:50:19 +0200	[thread overview]
Message-ID: <6365ef1e-d62d-4b2d-8e41-526881bbbe37@6wind.com> (raw)
In-Reply-To: <20260601143242.6729-1-fmancera@suse.de>

Le 01/06/2026 à 16:32, Fernando Fernandez Mancera a écrit :
> Currently, modifying IPv4 interface configuration parameters requires
> interacting with sysctl (/proc/sys/net/ipv4/conf/*). While
> ip-netconf exists for monitoring these values, there has been no native
> way to set them directly through iproute2.
> 
> This patch introduces the support for that via 'inet' at the 'ip link
> set'. It uses IFLA_INET_CONF netlink attribute to set the parameter.
> 
> Example to enable forwarding on an interface:
> 
> ip link set dev enp8s0 inet forwarding on
> 
> Signed-off-by: Fernando Fernandez Mancera <fmancera@suse.de>
Reviewed-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>

Do you plan to add the ipv6 part also?

  parent reply	other threads:[~2026-06-03 12:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01 14:32 [PATCH iproute2-next] iplink: add support for setting IPv4 devconf parameters Fernando Fernandez Mancera
2026-06-02 19:36 ` David Ahern
2026-06-02 19:46   ` Fernando Fernandez Mancera
2026-06-02 21:11     ` David Ahern
2026-06-03 12:50 ` Nicolas Dichtel [this message]
2026-06-03 13:24   ` Fernando Fernandez Mancera
2026-06-03 15:18     ` David Ahern
2026-06-03 15:22       ` Fernando Fernandez Mancera
2026-06-03 15:30         ` Fernando Fernandez Mancera

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=6365ef1e-d62d-4b2d-8e41-526881bbbe37@6wind.com \
    --to=nicolas.dichtel@6wind.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=fmancera@suse.de \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stephen@networkplumber.org \
    /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