show arp names no interface, and calls a stale neighbour reachable #1253

Closed
opened 2026-11-09 19:06:33 +00:00 by jaylouisw · 0 comments
Owner

What happens

show arp is the table you read when a neighbour answers but traffic still dies. It has five columns and
prints three:

Protocol  Address          Age (min)  Hardware Addr   Interface
Internet  10.0.0.9         -          02:00:00:00:02:00

The Interface column is a header over nothing — every row stops at the MAC — so the one table that
could tell you which port a neighbour lives on cannot tell you. The engine had the same gap: Device.arp is
Map(ip -> mac), and nothing recorded which port the frame arrived on, even though the ARP handler has
inIface in scope at all three learning sites.

Every entry is also presented identically whether its port is up, shut, or has no cable. A stale cache
entry therefore reads as evidence that the address is reachable — which is exactly the belief someone is
checking when they run the command.

Expected

  • record the port a neighbour was learned on, at every learning site, through one entry point (so a new
    call site cannot forget it);
  • show arp prints it, and appends the reason when that port can no longer carry a frame —
    (administratively down), (down: no cable), (down: link down), (down: peer shut down);
  • do not delete the entry when the port goes down: a real ARP cache does not empty when a cable is
    pulled, and the state is what marks it stale;
  • an entry with no recorded port (a topology restored from an older file) prints - rather than a guess; a
    port that no longer exists prints its name and (gone);
  • Age (min) stays -: the simulator counts steps, not minutes, and a step count in a minutes column is a
    number with the wrong unit.

Scope

The existing ARP table and the existing learning path. No new commands.

## What happens `show arp` is the table you read when a neighbour answers but traffic still dies. It has five columns and prints three: ``` Protocol Address Age (min) Hardware Addr Interface Internet 10.0.0.9 - 02:00:00:00:02:00 ``` The **Interface** column is a header over nothing — every row stops at the MAC — so the one table that could tell you which port a neighbour lives on cannot tell you. The engine had the same gap: `Device.arp` is `Map(ip -> mac)`, and nothing recorded which port the frame arrived on, even though the ARP handler has `inIface` in scope at all three learning sites. Every entry is also presented identically whether its port is up, shut, or has no cable. A stale cache entry therefore reads as evidence that the address is reachable — which is exactly the belief someone is checking when they run the command. ## Expected * record the port a neighbour was learned on, at every learning site, through one entry point (so a new call site cannot forget it); * `show arp` prints it, and appends the reason when that port can no longer carry a frame — `(administratively down)`, `(down: no cable)`, `(down: link down)`, `(down: peer shut down)`; * **do not** delete the entry when the port goes down: a real ARP cache does not empty when a cable is pulled, and the state is what marks it stale; * an entry with no recorded port (a topology restored from an older file) prints `-` rather than a guess; a port that no longer exists prints its name and `(gone)`; * `Age (min)` stays `-`: the simulator counts steps, not minutes, and a step count in a minutes column is a number with the wrong unit. ## Scope The existing ARP table and the existing learning path. No new commands.
Sign in to join this conversation.
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#1253
No description provided.