Timers are validated and never counted: a lab can only show the converged answer #1049
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1049
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Every timer in this engine is parsed, range-checked, and then thrown away.
forward-delay 15,hello 10,dead 40,advertise 1are all validated —engine/ospf.js:137even rejects
dead < hello— and none of them count for anything, becausecomputeStp()blocks itsports and
computeOspf()installs its routes at t=0.The consequence is that a lab can only ever show the converged answer. Power on a switch with a
looped topology and it has already converged. Ask for a ping and the network is already up. The
interval every technician actually watches — link light green, nothing passing — cannot be
demonstrated, which is half of what Packet Tracer is for.
What is needed
in a special simulation state: STP ports Listening/Learning and dropping traffic, OSPF without
learned routes, no DHCP lease, no VRRP mastership.
mean opposite things.
Timers that need to be counted
converge at <ms>— the formhelpprints — answers "converged" instead of refusing #1726converge at <ms>answers the question it prints (#1726) #1728