Netdev List
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: [ANNOUCE] iproute2 7.3 release
Date: Tue, 20 Oct 2026 19:48:20 -0700	[thread overview]
Message-ID: <20261020194820.5c9fbfb8@phoenix.local> (raw)

This is the regular release of iproute2 corresponding to the 7.3 kernel.

Highlights this cycle:
 * ip link details now show DPLL pin information
 * ip supports OVPN device mode
 * bonding gained lacp_strict support and fixes LACP partner port
   state display
 * SRv6 encap routes support the lookup attribute
 * nexthop supports fdb destination port
 * devlink param show/set supports u64-array values
 * rdma displays resource limits in curr/max format
 * ss no longer displays dccp sockets and fixes vsock port filter
 * ipmaddr uses RTM_GETMULTICAST to list multicast addresses
 * build fixes for Gcc-17 warnings and several memory leak fixes

Expected in next cycle:
 * Bug fixes for Anthropic Open Source Scanner
 

Download:
    https://www.kernel.org/pub/linux/utils/net/iproute2/iproute2-7.3.0.tar.gz

Repository for current release:
    https://github.com/shemminger/iproute2.git
    git://git.kernel.org/pub/scm/network/iproute2/iproute2.git

And future release (net-next):
    git://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git

Aman Sharma (1):
      man: ip-route: document uid parameter for route get

Andrea Mayer (2):
      seg6: add support for lookup attribute in SRv6 encap routes
      seg6: man: document the lookup attribute for SRv6 encap routes

Dave Seddon (3):
      iplink_bond_slave: read ad_partner_oper_port_state as u16
      testsuite: fix test_on_not on multi-line output
      testsuite: add bond slave LACP port state test

David Ahern (3):
      Update kernel headers
      Update kernel headers
      Update kernel headers

Ivan Vecera (1):
      ip: display DPLL pin information in link details

Jack Ma (1):
      ip nexthop: support fdb destination port

Louis Scalbert (1):
      ip/bond: add lacp_strict support

Luigi Leonardi (2):
      ss: widen sockstat lport/rport to long
      ss: fix vsock port filter

Marco Baffo (1):
      ip: add OVPN device mode support

Mohammad abu saleh (2):
      ip: remove redundant human-readable option match
      lib: fix memory leak in getcmdline()

Prabhakar Pujeri (1):
      u32: fix IPv6 port match pretty printing

Prijesh Patel (1):
      man: ip-route: document tcp_usec_ts route feature

Ratheesh Kannoth (2):
      devlink: use DEVLINK_VAR_ATTR_TYPE_* in param show/set
      devlink: support u64-array values in devlink param show/set

Stephen Hemminger (8):
      uapi: update from 7.3 merge
      json_print: fix Gcc-17 warnings
      lib: fix warning from ll_addr_a2n
      tc/f_u32: fix const strchr() warning
      iplink/can: fix format string warnings
      uapi: update magic.h
      lib: fix leak on realloc() failure
      v7.3.0

Tao Cui (2):
      rdma: update uapi headers
      rdma: display resource limits in curr/max format

Yafang Shao (1):
      ss: stop displaying dccp sockets

Yuyang Huang (1):
      ipmaddr: use RTM_GETMULTICAST to list multicast addresses

                 reply	other threads:[~2026-10-21  2:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261020194820.5c9fbfb8@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=netdev@vger.kernel.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