cli: show interface, layered presentation on IEEE 802.3.2-2025

[troglobit]

Description

Rebuilt bottom-up by protocol layer, sourced from the standard IEEE pmd-type identityref in ieee802-ethernet-interface@2025-09-10.yang and ieee802-ethernet-phy-type@2025-09-10.yang from IEEE 802.3.2-2025:

• pmd-type (identityref) is the discriminator we render — names map cleanly to ethtool's link mode strings (100baseTX, 1000baseT, 2.5GbaseT, 10GbaseLR,
  25GbaseCR, etc.).
• eth:speed is now status obsolete in the IEEE model; speed moves to ietf-interfaces:speed (gauge64 bits/s, RFC 8343).
• infix-ethernet-interface deviations re-evaluated against the new base (no surface changes beyond import revision pinning)
• infix-interfaces revision bumped to track the upgrade

Second commit catches up on a long-overdue show interfaces → show interface rename in docs and the landing page (the plural form was removed from klish years ago; user-facing examples were missed).

Example

Operational raw data, new YANG format

      {
        "name": "wan",
        "type": "infix-if-type:ethernet",
        "admin-status": "up",
        "oper-status": "up",
        "if-index": 3,
        "phys-address": "72:1c:0b:97:a4:9b",
        "speed": "1000000000",
        "statistics": {
          "in-octets": "3999404",
          "out-octets": "450585"
        },
        "ieee802-ethernet-interface:ethernet": {
          "auto-negotiation": {
            "enable": true
          },
          "pmd-type": "ieee802-ethernet-phy-type:pmd-type-1000BASE-T",
          "duplex": "full"
        },
        "ietf-ip:ipv4": {
          "mtu": 1500,
          "address": [
            {
              "ip": "192.168.0.240",
              "prefix-length": 24,
              "origin": "dhcp"
            }
          ],
          "neighbor": [
            {
              "ip": "192.168.0.1",
              "link-layer-address": "06:5b:a4:43:14:e9",
              "origin": "dynamic"
            }
          ]
        },
        "ietf-ip:ipv6": {
          "mtu": 1500,
          "address": [
            {
              "ip": "fdc2:e5c2:ef3:4a6c:701c:bff:fe97:a49b",
              "prefix-length": 64,
              "origin": "link-layer"
            },
            {
              "ip": "fe80::701c:bff:fe97:a49b",
              "prefix-length": 64,
              "origin": "link-layer"
            }
          ],
          "neighbor": [
            {
              "ip": "fe80::1407:4e04:f3f6:9cc8",
              "link-layer-address": "1c:b3:c9:0e:ea:95",
              "origin": "dynamic",
              "state": "stale"
            },
            {
              "ip": "fe80::1c0d:61d5:bdd1:bdca",
              "link-layer-address": "1c:b3:c9:0e:ea:95",
              "origin": "dynamic",
              "state": "stale"
            }
          ]
        },
        "infix-interfaces:ptp-capabilities": {
          "capabilities": [
            "software-receive",
            "software-system-clock"
          ]
        }
      }

  admin@bpi-76-8f-c2:/> show interface
  ⚑ INTERFACE       PROTOCOL      STATE       DATA
  ⇅ lo              loopback      UP
                    ipv4                      127.0.0.1/8 (static)
                    ipv6                      ::1/128 (static)
  ⇅ br0             bridge        DOWN
    │               ethernet                  32:2e:3f:76:8f:c2
    │               ipv4                      192.168.0.1/24 (static)
  ⇅ ├ lan0          bridge        LOWER-DOWN
  ⇅ ├ lan1          bridge        LOWER-DOWN
  ⇅ ├ lan2          bridge        LOWER-DOWN
  ⇅ └ lan3          bridge        LOWER-DOWN
  ⇅ gre0            gre           UP          remote: 198.51.100.7
                    ipv4                      10.255.0.1/30 (static)
  ⇅ sfp1            ethernet      DOWN        ca:59:f0:77:80:5b
  ⇅ wan             1000baseT     UP          duplex: full
                    ethernet                  32:2e:3f:76:8f:c2
                    ipv4                      192.168.0.235/24 (dhcp)
                    ipv6                      fdc2:e5c2:ef3:4a6c:302e:3fff:fe76:8fc2/64 (link-layer)
                    ipv6                      fe80::302e:3fff:fe76:8fc2/64 (link-layer)
  ⇅ wan.10          vlan          UP          vid: 10
    │               ipv4                      10.0.10.1/24 (static)
    └ wan
  ⇅ wan.10.20       vlan          UP          vid: 20
    │               ipv4                      10.0.10.20/28 (static)
    └ wan.10
  ⇅ wifi0           wifi          UP          station ssid: corp-net signal: good
                    ethernet                  dc:a6:32:00:11:22
                    ipv4                      192.168.7.42/24 (dhcp)

Checklist

Tick relevant boxes, this PR is-a or has-a:

• Bugfix
  • Regression tests
  • ChangeLog updates (for next release)
• Feature
  • YANG model change => revision updated?
  • Regression tests added/updated?
  • ChangeLog updates (for next release)
  • Documentation added?
• Test changes
  • Checked in changed Readme.adoc (make test-spec)
  • Added new test to group Readme.adoc and yaml file
• Code style update (formatting, renaming)
• Refactoring (please detail in commit messages)
• Build related changes
• Documentation content changes
  • ChangeLog updated (for major changes)
• Other (please describe):

[jovatn]

I have reviewed documentation part (i.e., all by the cli_pretty.py code).
Providing additional info in the overview command is very useful!
In short: LGTM!

Some general comments:

• Using colon as separator may cause some confusion in mac address lines, but users will get used to it (and I have no improvement to suggest).
• (key:value format is not applied to IPv4 and IPv6 addresses, but the choice is wise.)

Specific comment on VLAN example (scripting-prod.md) interleaved below.

[troglobit]

CCB review comments:

• This is quickly becoming unreadable, we want 'show interface' to remain friendly & useful
• We're mixing data that does not always match the protocol
• Drop the mac: prefix to mac addresses, the data should be stand-alone, like IP addresses
• Data should be in protocol layer order: wifi -> ethernet -> ip, gre -> ethernet -> ip, etc.
• General comment: the wifi Station, ssid: ... should be station ssid: ...
• We could also indent protocols and add line drawing characters
• A "speed line" protocol row: 1000-baseTX with DATA duplex: full, i.e., before the 'ethernet' protocol line, a '1000-baseTX' protocol type line, which would be useful for various types of SFP's as well
• ... more was said, passionate and interesting discussion!