> Op 17 nov. 2014, om 01:34 heeft Lorenzo Colitti <[email protected]> het > volgende geschreven: > > On Sun, Nov 16, 2014 at 8:54 AM, Juliusz Chroboczek > <[email protected]> wrote: > A and B are both announcing the LLN route. L crashes. A and B both > notice that L is no longer reachable, so each of them attempts to route > through the other one. You have a transient routing loop that lasts until > A and B agree on the fact that L is unreachable. > > No, you have a loop that lasts for as long as it takes A to tell B that L is > no longer reachable, which isn't very long.
It could be long enough to get in trouble. There could be more than two neighbors, loaded wireless links and jitter (for collision avoidance) or loss for routing packets. Teco > > Specifically: for as long as A thinks that L is reachable via direct > connection, it tries to send packets to it directly and not through B, which > means there is no loop. As soon as it decides that L is not reachable via > direct connection, it stops forwarding and withdraws the route. Now there's a > loop, but as soon as B hears the withdrawal, it stops forwarding to A, and > the loop goes away. > > This is no different to how most routing protocols work. > _______________________________________________ > homenet mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/homenet _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
