From: Andrew Lunn <andrew@lunn.ch>
To: 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.] network down timeout
Date: Thu, 14 Jan 2010 21:03:59 +0100 [thread overview]
Message-ID: <20100114200359.GB24649@lunn.ch> (raw)
In-Reply-To: <5522db2e1001140540p7af82ba9gd52b375d54a2441d@mail.gmail.com>
On Thu, Jan 14, 2010 at 08:40:25AM -0500, ecfu wrote:
> Is there a configuration setting for batman-adv to timeout on a connection?
> i.e. if I lose a node in my network, I noticed it took a long time for that
> node to leave the originators list. What is this based on or in other words
> when does batman-adv declare the lost originator gone?
An originator is purged when it has not been heard from in
#define PURGE_TIMEOUT 200000 /* purge originators after time in ms if no
* valid packet comes in.
is 200s = 3.3 minutes.
Andrew
next prev parent reply other threads:[~2010-01-14 20:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 13:40 [B.A.T.M.A.N.] network down timeout ecfu
2010-01-14 20:03 ` Andrew Lunn [this message]
2010-01-15 2:32 ` ecfu
2010-01-15 2:39 ` Marek Lindner
2010-01-15 14:34 ` ecfu
2010-01-15 15:57 ` Andrew Lunn
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=20100114200359.GB24649@lunn.ch \
--to=andrew@lunn.ch \
--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