From: Marek Lindner <mareklindner@neomailbox.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.] Classes and purposed classes (problem to solve)
Date: Mon, 16 Nov 2015 10:13:23 +0800 [thread overview]
Message-ID: <9732868.d8RG61WZUP@voltaire> (raw)
In-Reply-To: <CAJuY50zaR=aT6UB+Nk0T3KrQMTkGKR=nGxw_HsB2+haYCkbbMQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
On Saturday, November 14, 2015 20:04:49 3zl Trizonelabs wrote:
> With multi-gateway there it seems the general problems how to
> influence the batman-adv gateway announcement in respect of gateway
> capabilities.
Can you explain in greater detail what you are trying to achieve ?
> Additionally we encountered the problem that a gateway lost uptream
> connection(internet) without switching itself from server to client,
> so nodes with path to that gateway routes their resp.clients to a
> "black hole".
> Question is how generally control the batman-adv routing in those cases.
If you control the gateways the gateway should detect the uplink failure and
stop announcing themselves as gateway. That is how most people are doing it.
If you don't control the gateways or wish to solve this on the clients the
batman-adv module would need to get extended to influence the selected gateway
from user space.
Cheers,
Marek
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-11-16 2:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 15:35 [B.A.T.M.A.N.] Classes and purposed classes (problem to solve) cmsv
2015-11-14 18:04 ` 3zl Trizonelabs
2015-11-16 2:13 ` Marek Lindner [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-16 21:00 3zl Trizonelabs
2015-11-17 1:15 ` Marek Lindner
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=9732868.d8RG61WZUP@voltaire \
--to=mareklindner@neomailbox.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