public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: faycel.benhajkhalifa@eisox.com
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Problem with routing table
Date: Tue, 25 Jun 2019 10:21:40 +0200	[thread overview]
Message-ID: <22df3eaaaf123e7eb767ec7c0959cbfd@eisox.com> (raw)

Hello
I have a problem with setting up the routing table
the use case
I have 4 node with batman batctl 2018.1 [batman-adv: 2018.1] on openwrt 
18.06.1
2 nodes that serve the internet (connected directly with cable)
when a node that shares the internet is dead the other node can't ping 
the internet  unless the dead node no longer exists in its database 
neighbors (it does not appear in the results of batctl o and batctl n ) 
on average it takes a little more than 200 s to reconnect to the 
internet.
my questions are:
   Is it possible to update the routing table faster?
   Does it have anything to do with 200s to detect that a node and dead ?
thank you
cordially
faycel bhk

                 reply	other threads:[~2019-06-25  8:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=22df3eaaaf123e7eb767ec7c0959cbfd@eisox.com \
    --to=faycel.benhajkhalifa@eisox.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