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: Tue, 17 Nov 2015 09:15:30 +0800 [thread overview]
Message-ID: <2931985.8ZHTxnqmTu@voltaire> (raw)
In-Reply-To: <CAJuY50zf45s0Tst+2R4NtciE22kRqONJUUJAADA_7TvMH47XdQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
On Monday, November 16, 2015 23:00:59 3zl Trizonelabs wrote:
> in cases of gateway-router instabilites (short brownouts / blackouts )
> which we have alot with thunderstorms, it would be helpful if some
> other control instance could block the gateway to be used inside the
> batman-adv routing aside from the gateway anouncing itself.
Why does it matter how long the gateway is out ? What is the advantage of
doing long blackouts via the gateway announcement and short blackouts on the
client ? The clients have to switch their gateway either way.
> Is there any idea how to implement some kind of 'control instance'
> for the batman-adv routing ?
That depends on your definition of 'control instance'. From a high level
perspective how should it work ?
> That also would help to achive some dynamic routing to gateways by
> adjusting the qualtiy of those in respect L3 parameters.
This sentence does not compile. Do you mind explaining what you have in mind ?
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-17 1:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 21:00 [B.A.T.M.A.N.] Classes and purposed classes (problem to solve) 3zl Trizonelabs
2015-11-17 1:15 ` Marek Lindner [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-15 15:35 cmsv
2015-11-14 18:04 ` 3zl Trizonelabs
2015-11-16 2:13 ` 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=2931985.8ZHTxnqmTu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.