A port with no address has no method, so show ip interface brief says unset #1557

Merged
jaylouisw merged 1 commit from rev/1115-2231 into main 2026-11-15 23:14:44 +00:00
Owner

Question

What does the Method column of show ip interface brief say for a port that has no IP address?

Evidence

Verdict

unset. The table printed manual for every non-DHCP port, including ports with no address, which claimed a method nobody configured. manual now belongs only beside a static address; a DHCP client keeps DHCP while its lease is outstanding; no address means unset.

Changed

  • engine/cli.js: the Method cell is derived from the port state instead of the binary DHCP/not-DHCP choice.
  • docs/CLI.md: the Method column and the three states, with Cisco's field definition.
  • test/brief-method-unset.test.js: 8 assertions - factory port, static, DHCP before a lease, no ip address, and every factory port of a switch.

Gates

  • node scripts/syntax-check.js: 326 files, all OK
  • npm test: 256 suites, 9305 assertions, 0 failed

Unresolved

A static address loaded from startup-config prints NVRAM on a real box and manual when configured in the running session. PacketForge has no startup/running distinction, so it says manual for any static address; modelling the NVRAM/manual split would need a persisted startup config first.

## Question What does the **Method** column of `show ip interface brief` say for a port that has no IP address? ## Evidence - Cisco, *Using Cisco IOS Software* command reference, `show ip interface`: `Serial1 unassigned YES unset administratively down down` - https://www.cisco.com/E-Learning/bulk/public/tac/cim/cib/using_cisco_ios_software/cmdrefs/show_ip_interface.htm - Cisco Catalyst 9500 17.18 command reference, `show ip interface`: Method values include `unset: Unset` - http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst9500/software/release/17-18/command_reference/b_1718_9500_cr/interface_and_hardware_commands.pdf - Cisco 8100 configuration guide: factory ports print `unassigned YES unset up up` - http://www.cisco.com/c/en/us/td/docs/routers/secure-routers/sec-8100-series/software-config-guide/cisco-8100-series-secure-routers-software-configuration-guide/m-interface-configuration.html ## Verdict `unset`. The table printed `manual` for every non-DHCP port, including ports with no address, which claimed a method nobody configured. `manual` now belongs only beside a static address; a DHCP client keeps `DHCP` while its lease is outstanding; no address means `unset`. ## Changed - `engine/cli.js`: the Method cell is derived from the port state instead of the binary DHCP/not-DHCP choice. - `docs/CLI.md`: the Method column and the three states, with Cisco's field definition. - `test/brief-method-unset.test.js`: 8 assertions - factory port, static, DHCP before a lease, `no ip address`, and every factory port of a switch. ## Gates - `node scripts/syntax-check.js`: 326 files, all OK - `npm test`: 256 suites, 9305 assertions, 0 failed ## Unresolved A static address loaded from startup-config prints `NVRAM` on a real box and `manual` when configured in the running session. PacketForge has no startup/running distinction, so it says `manual` for any static address; modelling the NVRAM/manual split would need a persisted startup config first.
A port with no address has no method, so show ip interface brief says unset
All checks were successful
CI / Classify the change (pull_request) Successful in 15s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 22s
CI / Test (Node 18) (pull_request) Successful in 3m44s
CI / Test (Node 20) (pull_request) Successful in 3m15s
CI / Test (Node 22) (pull_request) Successful in 3m6s
CI / Server smoke test (pull_request) Successful in 29s
CI / Docker build (pull_request) Successful in 24s
1b2ddc1dd1
Cisco's field list defines `unset` as Unset, and its sample output pairs `unassigned  YES unset` on a factory port. The table printed `manual` for every port that was not a DHCP client, including ports with no address - claiming a configuration nobody typed. The method now follows the port: DHCP while a client asks, manual beside a static address, unset when there is none.
jaylouisw scheduled this pull request to auto merge when all checks succeed 2026-11-15 23:14:30 +00:00
jaylouisw force-pushed rev/1115-2231 from 1b2ddc1dd1
All checks were successful
CI / Classify the change (pull_request) Successful in 15s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 22s
CI / Test (Node 18) (pull_request) Successful in 3m44s
CI / Test (Node 20) (pull_request) Successful in 3m15s
CI / Test (Node 22) (pull_request) Successful in 3m6s
CI / Server smoke test (pull_request) Successful in 29s
CI / Docker build (pull_request) Successful in 24s
to 805cc36809
All checks were successful
CI / Classify the change (pull_request) Successful in 21s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 20s
CI / Test (Node 18) (pull_request) Successful in 3m33s
CI / Test (Node 20) (pull_request) Successful in 3m15s
CI / Server smoke test (pull_request) Successful in 27s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 22) (pull_request) Successful in 3m7s
2026-11-15 23:14:34 +00:00
Compare
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!1557
No description provided.