Repository : ssh://git@open-mesh.org/doc

On branches: backup-redmine/2017-07-13,master

commit e427bea1087e7661931b70fadb6863792928b5d6 Author: Marek Lindner mareklindner@neomailbox.ch Date: Wed Dec 1 13:56:19 2010 +0000

doc: open-mesh/Routing_scenarios

e427bea1087e7661931b70fadb6863792928b5d6 open-mesh/Routing_scenarios.textile | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/open-mesh/Routing_scenarios.textile b/open-mesh/Routing_scenarios.textile index d37a8a79..a42d5c02 100644 --- a/open-mesh/Routing_scenarios.textile +++ b/open-mesh/Routing_scenarios.textile @@ -11,7 +11,16 @@ This page contains a collection of routing scenarios which all routing protocol

In this scenario A and B have 2 possible paths to communicate with each other. One of the nodes that is part of the currently used path dies and the protocol needs to detect the unavailability of the path to switch as fast as possible to the other one.

-[[Image(wiki:routing_scenarios:alternativ_path.png, 100%25)]] +[[Image(wiki:routing_scenarios:alternative_path.png, 100%25)]] + + +=== Mobility === + +==== New neighbor ==== + +While A is moving through the mesh the route between A and B shall recover as fast as possible. + +[[Image(wiki:routing_scenarios:new_neigh.png, 100%25)]]

}}}