tldr-pages/tldr

Let's document: iproute2

Open

#15,594 opened on Jan 24, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Shell (2,507 forks)batch import
help wantedlet's documentnew command

Repository metrics

Stars
 (30,937 stars)
PR merge metrics
 (Avg merge 7d 5h) (321 merged PRs in 30d)

Description

Command description

Linux networking tools

Documentation

http://www.policyrouting.org/iproute2.doc.html#ss9.1

Platform

Linux

VCS repository link (e.g. GitHub, GitLab)

https://git.kernel.org/pub/scm/network/iproute2/iproute2.git

Additional information

Remember that at least the ip command accepts any shortened form of a parameter as long as it's unique. Always write the full form even if you're used to running ip a or ip addr

Commands

  • arpd
  • bridge #15821
    • link
    • fdb
    • mdb
    • vlan
    • monitor
  • ctstat
  • dcb
  • devlink
  • genl
  • ifstat #14013
  • ip #114
    • address #3930
    • arrdlabel
    • fou
    • help
    • ila
    • iom
    • l2tp
    • link #5651
    • macsec
    • maddress #15595
    • monitor #18396
    • mptcp
    • mroute
    • mrule
    • neighbour #5697
    • netconf #18939
    • netns
    • nexthop
    • ntable
    • ntbl
    • route #5696
      • add #15994
      • get #14333
      • list #9311
      • show #9311
    • rule #6504
    • sr
    • stats #18796
    • tap
    • tcpmetrocs
    • token
    • tunnel
    • tuntap #18858
    • vrf
  • lnstat
  • nstat #15822
  • rdma
  • routel #18389
  • rtacct
  • rtmon #18396
  • rtstat
  • ss #119
  • tc #8795
    • qdisc
    • class
    • filter
    • chain
    • action
    • monitor
    • exec
  • tipc
  • vdpa

Contributor guide

Research direction
Pick an unchecked subcommand from the checklist (e.g., 'arpd' or 'dcb'), read its man page and official documentation, and create a tldr page following the tldr pages contribution guidelines. Submit a pull request with the new page.
Tech stack
shell
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65