show interfaces counts what crossed a port and nothing about what it discarded #1257

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

What happens

show interfaces reports what crossed a port and nothing about what was thrown away on it. Two datagrams
dropped for want of a route read exactly like a port nothing ever touched:

Gi0
  status: up, protocol: up
  ip: 10.0.0.1/24
  peer: a/eth0
  0 packets input, 0 bytes
  0 packets output, 0 bytes        <- and the ping failed twice

Three separate silences underneath:

  1. No discard counters at all. 25 sites emit drop with a reason, and every one of them threw the reason
    away with the event log. Nothing tallied them per port, so the one question a quiet link raises - "is
    something being thrown away here?" - had no answer.
  2. An ACL deny emitted no drop event. It emits acl-deny, a different type, and nothing counted it.
    The commonest discard of all left the port looking completely idle:
    access-list 101 deny icmp any any + ip access-group 101 in + two denied pings = 0 drops, 0 of
    everything, on a port that had just thrown two packets away.
  3. An unanswered ARP produced nothing whatsoever. The packet sat in dev.pending forever: no event, no
    counter, and ping reported success: false, reason: null. Ping an address whose port is shut and the
    simulator said, in effect, "no".

Expected

  • one tally, fed from the one place every discard passes through, so a discard site added later counts itself;
  • one table saying which events mean "this frame was discarded" - by type where the type can only mean that,
    and by an explicit discard: true where the type is also used for something narrower (stp-block fires
    once per blocked candidate port during a flood; counting each would report one lost frame three times);
  • show interfaces prints the count and the reason, on the port, and nothing at all when the port is
    clean;
  • a discard with no port in scope (no route to 10.0.0.99 happens before an egress is chosen) reported once
    at the end of the table rather than invented onto a port;
  • an unresolved ARP reported as a discard - no ARP reply from 10.0.0.9 - and the failed ping given the
    same sentence instead of a null reason.

Scope

Existing events, existing counters, existing commands. No new commands.

## What happens `show interfaces` reports what crossed a port and nothing about what was thrown away on it. Two datagrams dropped for want of a route read exactly like a port nothing ever touched: ``` Gi0 status: up, protocol: up ip: 10.0.0.1/24 peer: a/eth0 0 packets input, 0 bytes 0 packets output, 0 bytes <- and the ping failed twice ``` Three separate silences underneath: 1. **No discard counters at all.** 25 sites emit `drop` with a reason, and every one of them threw the reason away with the event log. Nothing tallied them per port, so the one question a quiet link raises - "is something being thrown away here?" - had no answer. 2. **An ACL deny emitted no `drop` event.** It emits `acl-deny`, a different type, and nothing counted it. The commonest discard of all left the port looking completely idle: `access-list 101 deny icmp any any` + `ip access-group 101 in` + two denied pings = `0 drops`, `0` of everything, on a port that had just thrown two packets away. 3. **An unanswered ARP produced nothing whatsoever.** The packet sat in `dev.pending` forever: no event, no counter, and `ping` reported `success: false, reason: null`. Ping an address whose port is shut and the simulator said, in effect, "no". ## Expected * one tally, fed from the one place every discard passes through, so a discard site added later counts itself; * one table saying which events mean "this frame was discarded" - by type where the type can only mean that, and by an explicit `discard: true` where the type is also used for something narrower (`stp-block` fires once per blocked candidate port during a flood; counting each would report one lost frame three times); * `show interfaces` prints the count **and the reason**, on the port, and nothing at all when the port is clean; * a discard with no port in scope (`no route to 10.0.0.99` happens before an egress is chosen) reported once at the end of the table rather than invented onto a port; * an unresolved ARP reported as a discard - `no ARP reply from 10.0.0.9` - and the failed `ping` given the same sentence instead of a null reason. ## Scope Existing events, existing counters, existing commands. 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#1257
No description provided.