From: David Ahern <dsahern@kernel.org>
To: Fernando Fernandez Mancera <fmancera@suse.de>, netdev@vger.kernel.org
Cc: stephen@networkplumber.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, Nicolas Dichtel <nicolas.dichtel@6wind.com>
Subject: Re: [PATCH iproute2-next] iplink: add support for setting IPv4 devconf parameters
Date: Tue, 2 Jun 2026 15:11:01 -0600 [thread overview]
Message-ID: <32c20500-8a76-419a-ab79-5ec68d2de6df@kernel.org> (raw)
In-Reply-To: <bc71f624-e4ce-47b7-9dae-13ad0db76ad1@suse.de>
On 6/2/26 1:46 PM, Fernando Fernandez Mancera wrote:
> On 6/2/26 9:36 PM, David Ahern wrote:
>> On 6/1/26 8:32 AM, Fernando Fernandez Mancera wrote:
>>> 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
>>
>> If an attribute can be set this way, then ip link show needs to show the
>> values. What's the plan on that front?
>>
>
> I could introduce it in a follow-up patch. I guess it makes sense to
> introduce it for ip -d link show only, right? I am happy to work on it
> anyway.
yes, -d only.
Will give Nicolas a chance to review.
next prev parent reply other threads:[~2026-06-02 21:11 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 [this message]
2026-06-03 12:50 ` Nicolas Dichtel
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=32c20500-8a76-419a-ab79-5ec68d2de6df@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