mir/network-examples
2
0
Fork 0
mirror of https://github.com/knorrie/network-examples synced 2025-08-30 14:08:36 +00:00
Code Issues Releases Wiki Activity

OSPF intro: cosmetics

Browse Source
This commit is contained in:
Hans van Kranenburg
2015-06-07 22:25:45 +02:00
parent feec467288
commit 172e3d2122
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
ospf-intro/README.md
View File

@@ -350,7 +350,7 @@ Here's mine:
![OSPF network, reconvergence](/ospf-intro/ospf-together-hosts-linkdown.png)
When I disabled the interface on R5, BIRD on R5 got notified by netlink that the interface went down. OSPF on R5 had to change its information card immediately and send it out again. But... it was only able to send it out on the 10.0.1.0/24 network. So it did, and R1 and R6 received it. Since R1 had not seen an update on the lower side of the network, it notified routers in there of the change and R2 was able to recalculate the shortest paths to the entire network after changing its view of the complete network topology with the missing link between R5 and the 10.1.2.0/24 network. After doing so, R2 determined that the current open shortest path to 10.34.2.5 had to be via 10.1.2.7 and used the BIRD kernel protocol to retract the route to 10.34.2.0/24 via 10.1.2.56 and inserted a new route into the Linux kernel routing table which points to 10.1.2.7 as next hop for 10.34.2.0/24. And then, mtr noticed there was a change in the path.
When I disabled the interface on R5, BIRD on R5 got notified by netlink that the interface went down. OSPF on R5 had to change its information card immediately and send it out again. But... it was only able to send it out on the `10.0.1.0/24` network. So it did, and R1 and R6 received it. Since R1 had not seen an update on the lower side of the network, it notified routers in there of the change and R2 was able to recalculate the shortest paths to the entire network after changing its view of the complete network topology with the missing link between R5 and the `10.1.2.0/24` network. After doing so, R2 determined that the current open shortest path to `10.34.2.5` had to be via `10.1.2.7` and used the BIRD kernel protocol to retract the route to `10.34.2.0/24` via `10.1.2.56` and inserted a new route into the Linux kernel routing table which points to `10.1.2.7` as next hop for `10.34.2.0/24`. And then, mtr noticed there was a change in the path.
Apparently, I lost a ping while the network was busy to get into a stable converged state again. ;-(