From: David Ahern <dsahern@kernel.org>
To: Fernando Fernandez Mancera <fmancera@suse.de>,
nicolas.dichtel@6wind.com, netdev@vger.kernel.org,
Stephen Hemminger <stephen@networkplumber.org>
Cc: 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 09:18:40 -0600 [thread overview]
Message-ID: <0bc2dcd4-b29e-4a82-8d1b-5170e78c2d74@kernel.org> (raw)
In-Reply-To: <491689b6-95f9-4e32-ae70-fdae464af353@suse.de>
On 6/3/26 7:24 AM, Fernando Fernandez Mancera wrote:
> On 6/3/26 2:50 PM, Nicolas Dichtel wrote:
>> 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?
>
> Yes, it is cooking but I want to get merged IPv4 first.
>
If I merge the ipv4 patch today that means you are signing up to send
patches for ipv6 set and then ipv4 and ipv6 show in detailed device
dump. All of that in the next 2 weeks before 7.1 is released. Just want
to make sure we are clear on expectations.
With respect to this patch, the usage is getting long and wading through
all of the inet and then inet6 options is going to be a challenge.
Stephen: opinions on location and details? Should the list even be in
the usage vs only the man page? ie., usage just has `[ inet <devconf
options> ]` (and similar for inet6)? If the all of the options stay
listed in the usage they should be in alphabetical order (and added
after the existing gro_max_size line?).
next prev parent reply other threads:[~2026-06-03 15:18 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
2026-06-03 13:24 ` Fernando Fernandez Mancera
2026-06-03 15:18 ` David Ahern [this message]
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=0bc2dcd4-b29e-4a82-8d1b-5170e78c2d74@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--cc=fmancera@suse.de \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--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