From: Andrew Lunn <andrew@lunn.ch>
To: Antonio Quartulli <antonio@meshcoding.com>
Cc: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Suggestion for routing improvement on poor links
Date: Thu, 20 Feb 2014 10:09:03 +0100 [thread overview]
Message-ID: <20140220090903.GF11878@lunn.ch> (raw)
In-Reply-To: <5305C4C5.8090504@meshcoding.com>
On Thu, Feb 20, 2014 at 10:03:01AM +0100, Antonio Quartulli wrote:
> On 20/02/14 09:54, Andrew Lunn wrote:
> > The routing protocol is known to have problems when a node suddenly
> > disappears. A received OGM is what triggers updates to the metric. If
> > you stop receiving OGMs the metric is no longer updated until the node
> > is purged as dead. This for example causes problems with
> > nomadic/mobile nodes. They can go around a corner, loss line of sight,
> > but still be considered the best route until purged as dead.
>
> But if you keep receiving OGMs via another neighbour you will have a
> route switch *before* the old nexthop is considered as dead.
Hi Antonio
That is not what i have seen in practice. Because the metric is good,
and does not degrade, it stays as the best route. That is one of the
reasons Linus developed NDP while at Ascom.
Andrew
next prev parent reply other threads:[~2014-02-20 9:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 20:56 [B.A.T.M.A.N.] Suggestion for routing improvement on poor links whangarei & opua
2014-02-19 21:27 ` Antonio Quartulli
2014-02-19 22:12 ` whangarei & opua
2014-02-19 22:30 ` Antonio Quartulli
2014-02-20 8:54 ` Andrew Lunn
2014-02-20 9:03 ` Antonio Quartulli
2014-02-20 9:09 ` Andrew Lunn [this message]
2014-02-20 9:44 ` Antonio Quartulli
2014-02-20 10:10 ` Andrew Lunn
2014-02-20 10:33 ` Marek Lindner
[not found] ` <F42F9132-14DE-4496-A715-389CF13D6C49@gmx.de>
[not found] ` <5305C654.5020605@meshcoding.com>
2014-02-20 10:20 ` whangarei & opua
2014-02-22 13:20 ` Marek Lindner
2014-02-23 10:35 ` whangarei & opua
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140220090903.GF11878@lunn.ch \
--to=andrew@lunn.ch \
--cc=antonio@meshcoding.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox