Thread (10 messages) flat view 10 messages, 3 authors, 2026-06-04

Re: [PATCH iproute2-next] iplink: add support for setting IPv4 devconf parameters

From: David Ahern <dsahern@kernel.org>
Date: 2026-06-03 15:18:41

On 6/3/26 7:24 AM, Fernando Fernandez Mancera wrote:
On 6/3/26 2:50 PM, Nicolas Dichtel wrote:
quoted
Le 01/06/2026 à 16:32, Fernando Fernandez Mancera a écrit :
quoted
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 <redacted>
Reviewed-by: Nicolas Dichtel <redacted>

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?).
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help