Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2017-07-13,master
commit b5220bf39b225cf0f5106e24a54cf5cc544b4a80 Author: Linus Lüssing linus.luessing@c0d3.blue Date: Sat May 28 03:47:41 2011 +0000
doc: batman-adv/T_X's_Junkyard_–_MGO
b5220bf39b225cf0f5106e24a54cf5cc544b4a80 "batman-adv/T_X's_Junkyard_\342\200\223_MGO.textile" | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git "a/batman-adv/T_X's_Junkyard_\342\200\223_MGO.textile" "b/batman-adv/T_X's_Junkyard_\342\200\223_MGO.textile" index 9b4e85b3..0ee455ca 100644 --- "a/batman-adv/T_X's_Junkyard_\342\200\223_MGO.textile" +++ "b/batman-adv/T_X's_Junkyard_\342\200\223_MGO.textile" @@ -6,7 +6,7 @@ In certain topologies the OGM (Originator Message) protocol can still have sever
The purpose of the MGO protocol is to react to (rapidly) decreasing local link qualities and to actively try to find an alternative, loop-free path, while only increasing the overhead on the currently selected and alternative paths. It shall complement the proactive OGM protocol.
-The MGO protocol is split into two parts: The Router Alert part to mark the currently selected best path(s) as 'stale' in response to a previously detected emergency event. And the Router Request part to request newer sequence numbers from alternative paths that allow nodes on the marked 'fragile' path to switch to the alternative path safely, e.g. without causing routing loops. +The MGO protocol is split into two parts: The Router Alert part to mark the currently selected best path(s) as 'stale' in response to a previously detected emergency event. And the Router Request part to request newer sequence numbers from alternative paths that allow nodes on the marked 'stale' path to switch to the alternative path safely, e.g. without causing routing loops.
h1. Definitions