the first openFlow on a fresh topology always fails E_UNREACHABLE #1518
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1518
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?
On a freshly built topology the first
openFlowreturnsE_UNREACHABLE; runs 2 and 3 on the same topology returnok: true. The ARP resolution loses the SYN and the flow does not retry.The root cause is placement: ARP caches, MAC tables and
dev.pendinglive on the Topology rather than on the Simulator, so a check's answer depends on what ran before it.Why it matters: it is a false fail for a connectivity check and a false pass for an isolation check, and it makes any check library order-dependent - which destroys the property the whole library rests on, that the same question asked twice gets the same answer.
Where:
engine/simulator.jsopenFlow; state ownership acrossengine/topology.jsandengine/simulator.js.Suggested fix (minimal): retry the resolved flow once when the failure is
E_UNREACHABLEwith a pending ARP entry. Better: move run-state off the topology so two evaluations of the same topology cannot differ.