An at instant sticks to the console session, and the browser calls convergence packet loss #1383

Closed
opened 2026-11-10 21:00:10 +00:00 by jaylouisw · 0 comments
Owner

Three defects in the same corner:

  1. ping <address> at 0 calls sim.setRunTime(0), which persists on the simulator. Every later command in that
    console session is then answered at t=0 — the next plain ping, a later show ip route, anything — and nothing
    says so. Measured on a switch whose access ports listen 30 s:

    SW1> ping 10.9.0.2 2 at 0
    Success rate is 0 percent (0/2)
    % Still converging at t=0 ms: stp on SW1 (ready at 30000 ms)
    SW1> ping 10.9.0.2 2
    Success rate is 0 percent (0/2)          <- should be 100%: no instant was named
    % Still converging at t=null ms: ...
    
  2. That second line prints at t=null ms: the instant in the sentence comes from the command, not from the answer.

  3. The browser's Simulate dialog draws Success rate 0% (0/4) for a path that is merely still settling — the lie the
    API stopped telling in #1377 and #1381, one surface further out.

What must be true instead

  1. The answer carries its own instant (runAtMs), and null when it belongs to no particular instant (Infinity).
  2. at <ms> applies to the command that named it; the console restores the session's instant afterwards.
  3. One sentence for convergence, written once, printed once per ping, mirrored by the browser and checked for
    agreement.
  4. The dialog puts no percentage on a converging path, and still reports genuine loss as loss.
Three defects in the same corner: 1. `ping <address> at 0` calls `sim.setRunTime(0)`, which **persists** on the simulator. Every later command in that console session is then answered at t=0 — the next plain `ping`, a later `show ip route`, anything — and nothing says so. Measured on a switch whose access ports listen 30 s: ``` SW1> ping 10.9.0.2 2 at 0 Success rate is 0 percent (0/2) % Still converging at t=0 ms: stp on SW1 (ready at 30000 ms) SW1> ping 10.9.0.2 2 Success rate is 0 percent (0/2) <- should be 100%: no instant was named % Still converging at t=null ms: ... ``` 2. That second line prints `at t=null ms`: the instant in the sentence comes from the *command*, not from the answer. 3. The browser's Simulate dialog draws `Success rate 0% (0/4)` for a path that is merely still settling — the lie the API stopped telling in #1377 and #1381, one surface further out. ## What must be true instead 1. The answer carries its own instant (`runAtMs`), and `null` when it belongs to no particular instant (`Infinity`). 2. `at <ms>` applies to the command that named it; the console restores the session's instant afterwards. 3. One sentence for convergence, written once, printed once per ping, mirrored by the browser and checked for agreement. 4. The dialog puts no percentage on a converging path, and still reports genuine loss as loss.
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#1383
No description provided.