An OSPF adjacency forms across a cable that is not there, and show ip route cannot say a next hop is unreachable #1271
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1271
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?
What happens
Two routers, OSPF on the shared segment, one LAN behind
r1. With the cable in,r2installs the LAN as anOroute. Pull the cable:The route survives, pointing at a next hop that answers nothing, and a ping to the LAN fails with
no ARP reply from 10.0.0.1— the data plane knowing the path is gone while the control plane went onbelieving it.
computeOspf()collected interfaces that wereenabledand addressed and then formed an adjacency for everytopology link between two such interfaces. A topology link exists while its state is
down, and nothingasked. Hellos need a wire that can carry them: a pulled cable, a down link, or a shut far port forms no
adjacency. BGP had exactly this defect one iteration earlier (#1269); OSPF had no link-state check at all.
A second, wider symptom
show ip routecannot say that any installed route's next hop is unreachable. A static route or a connectedroute over a port with no cable reads exactly like a working path:
Expected
withdraws the route — a learned route is withdrawn, not annotated;
why its egress cannot be used, in the same words
show arpandshow mac address-tablealready use forthe same port;
Scope
The existing OSPF adjacency computation and the existing
show ip routeoutput. No new commands, no newconfig surface.
show ip route(#1301) #1302