From: Marek Lindner <lindner_marek@yahoo.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Unterstanding gateway-mode - why do nodes have a "sticky" gateway
Date: Thu, 3 Jan 2013 23:14:22 +0800 [thread overview]
Message-ID: <201301032314.22606.lindner_marek@yahoo.de> (raw)
In-Reply-To: <82C77F63-2AB3-4AEB-A86A-23B3488E6C51@stephan.homeunix.net>
On Thursday, January 03, 2013 23:01:07 Jan Lühr wrote:
> > Ah! You failed to mention this part in your initial email.
> >
> > The behavior is easily explained: batman-adv does not switch gateway
> > whenever a new gateway is found (even if it is a better gateway) unless
> > the selection class is on fast or late switching.
>
> It is. - Sorry, forgot to mention:
> Freifunk-b0487acb2d58:~# batctl gw_mode
> client (selection class: 1)
>
> => 1 -> fast connection consider the gateway's advertised throughput as
> well as the link quality towards the gateway
You did mention you were using selection class 1. I was referring to your test
in which you turn on/off your best gateway. As I explained in my previous
mail: batman-adv does not switch the gateway once it has chosen a gateway
unless you select fast or late switching as selection class. Selection class 1
does not fall into this category which means a gateway reselection only
happens if the currently selected gateway disappears.
Run the foloowing test: enable both gateways before setting the gateway client
to selection class 1. The gateway announcing the higher bandwidth should be
selected.
Cheers,
Marek
next prev parent reply other threads:[~2013-01-03 15:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-31 1:16 [B.A.T.M.A.N.] Unterstanding gateway-mode - why does node have a "sticky" gateway Jan Lühr
2013-01-01 17:25 ` NicoEchániz
2013-01-02 23:28 ` [B.A.T.M.A.N.] Unterstanding gateway-mode - why do nodes " Jan Lühr
2013-01-03 1:57 ` Marek Lindner
2013-01-03 11:03 ` Jan Lühr
2013-01-03 14:58 ` Marek Lindner
2013-01-03 15:01 ` Jan Lühr
2013-01-03 15:14 ` Marek Lindner [this message]
2013-01-04 0:06 ` NicoEchániz
2013-01-04 0:39 ` Marek Lindner
2013-01-04 15:12 ` NicoEchániz
2013-01-04 17:41 ` Marek Lindner
2013-01-04 18:25 ` Jan Lühr
2013-01-04 18:38 ` Jan Lühr
2013-01-04 23:28 ` NicoEchániz
2013-01-05 4:42 ` Marek Lindner
2013-01-05 9:47 ` Jan Lühr
2013-01-07 15:26 ` Jan Lühr
2013-01-08 6:15 ` Marek Lindner
2013-01-08 16:35 ` NicoEchániz
2013-01-09 6:30 ` Marek Lindner
2013-01-09 11:49 ` Jan Lühr
2013-01-09 17:39 ` NicoEchániz
2013-01-09 22:20 ` Jan Lühr
2013-01-16 1:42 ` NicoEchániz
2013-01-16 11:38 ` Jan Lühr
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=201301032314.22606.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--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.