On Mon, Nov 17, 2014 at 5:08 PM, Juliusz Chroboczek <[email protected]> wrote: >> Something of an aside to this conversation, but there is a similar >> problem in dealing with an external gateway that does not speak the >> routing protocol either. > > Aye. > >> The ¨babel-pinger¨ mechanism >> >> http://lists.alioth.debian.org/pipermail/babel-users/2008-September/000160.html >> >> would have been a cure for this... > > I had forgotten this hack. > >> A Nest-pinger (or responder - ) might be a way to keep a route alive.... > > You're completely right, Dave. This would solve the issue with minimal fuss.
Isn't the "Nest pinger" just a shortcut for reducing the intervals and validity times of the information transfer between the Nest-node and the true-Homenet-node? If you want to discover a link loss quickly, just exchange data more often to make sure the other side is still there. Doesn't matter if its a ping, a HNCP packet, a BABEL packet or a layer2-beacon. Henning Rogge _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
