From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: BEAL Romain <Romain.BEAL@knds.fr>
Cc: "b.a.t.m.a.n@lists.open-mesh.org" <b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: configuration for mobile nodes
Date: Sat, 29 Jun 2024 03:40:29 +0200 [thread overview]
Message-ID: <Zn9mDQQNPvq7zeBu@sellars> (raw)
In-Reply-To: <0ae0e36496504245bb8ad0fab5c054a4@knds.fr>
I'd be careful with just reducing timeouts... A 2 seconds purge
timeout together with a default 1 second OGM interval seems to me
like asking for a lot of route flapping in the best case. And
potential, temporary routing loops in the worst case.
What we typically do is decrease the batman-adv originator
interval instead, which you can do with "batctl orig_interval".
Some people seem to get confused about stale entries from
vanished nodes. They shouldn't have much impact on performance. If
that dead node was a selected router to another node but has not been
heard of for 5 sequence numbers (5x originator interval,
BATADV_TQ_GLOBAL_WINDOW_SIZE) then this other node will use an
alternative neighbor node as a router with the next OGM with a
seqno > 5 from this alternative.
Regards, Linus
On Thu, Jun 27, 2024 at 07:43:59PM +0000, BEAL Romain wrote:
> Hi,
>
> I want to use batman-adv for highly mobile nodes.
> All of my nodes are robot or radio module embedded on a human, for example.
>
> Losing a node is very common and batman-adv needs to self-reconfigure quickly in my case.
> Adding a node is very common too, maybe for only few seconds or minutes.
>
> The default configuration doesn't work very well for my use case.
> But when I use this configuration :
>
> #define BATADV_PURGE_TIMEOUT 2000
> #define BATADV_TT_LOCAL_TIMEOUT 6000
> #define BATADV_TT_CLIENT_ROAM_TIMEOUT 6000
> #define BATADV_TT_CLIENT_TEMP_TIMEOUT 6000
> #define BATADV_ORIG_WORK_PERIOD 500
> #define BATADV_DAT_ENTRY_TIMEOUT (5*600)
>
> The result is better. I have some unstable connection for only 5 seconds when I loss a node.
> Have you done any testing for this type of use ?
>
> Thanks for help
>
>
> Ce message électronique et tous les fichiers qui lui sont attachés sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci d'en avertir immédiatement son émetteur et de supprimer ce message de votre système sans en conserver de copie. La copie, la rediffusion à tout tiers et l'utilisation du contenu de ce message ou des fichiers attachés est strictement interdite sans l'accord préalable écrit de l'émetteur.
>
> Ce document est susceptible de contenir de l'information soumise à contrôle (ML22) relevant de la réglementation européenne quant aux exportations des matériels de guerre et matériels assimilés. Toute exportation ou réexportation est soumise à autorisation écrite du gouvernement français.
> --------------------------------------------------------------------------------
> This email and any attachments are confidential and intended solely for the use of the individual to whom they are addressed. If you have received this e-mail in error, please inform the sender immediately without keeping any copy thereof and delete it from your system. Copy, use or distribution of contents of this message or attachments to any other person is strictly prohibited without sender's prior written permission.
>
> This document may contains controlled data submitted to EU military lists regulations. Any export or reexport is submitted to written authorization of French Government.
>
>
prev parent reply other threads:[~2024-06-29 1:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 19:43 configuration for mobile nodes BEAL Romain
2024-06-29 1:40 ` Linus Lüssing [this message]
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=Zn9mDQQNPvq7zeBu@sellars \
--to=linus.luessing@c0d3.blue \
--cc=Romain.BEAL@knds.fr \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).