From: NicoEchániz <nicoechaniz@altermundi.net>
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.] Unterstanding gateway-mode - why does node have a "sticky" gateway
Date: Tue, 01 Jan 2013 14:25:52 -0300 [thread overview]
Message-ID: <50E31C20.6010604@altermundi.net> (raw)
In-Reply-To: <B9683C50-CBE6-40F6-B084-187E41B04CE4@stephan.homeunix.net>
On 12/30/2012 10:16 PM, Jan Lühr wrote:
> Hello,
>
> I started using batman-adv's gateway mode. Sadly, I ran into some trouble - A client is connected to two gateways via vpn (fastd):
> # batctl gw_mode
> client (selection class: 1)
>
> # batctl gwl
> Gateway (#/255) Nexthop [outgoingIF]: gw_class ... [B.A.T.M.A.N. adv 2012.4.0, MainIF/MAC: wlan0-1/f6:ec:38:e9:72:35 (bat0)]
> 6a:4b:93:de:00:84 (255) 6a:4b:93:de:00:84 [ mesh-vpn]: 207 - 48MBit/48MBit
> => aa:31:0e:4a:0f:1d (254) aa:31:0e:4a:0f:1d [ mesh-vpn]: 39 - 1024KBit/1024KBit
>
> # batctl o
> [B.A.T.M.A.N. adv 2012.4.0, MainIF/MAC: wlan0-1/f6:ec:38:e9:72:35 (bat0)]
> Originator last-seen (#/255) Nexthop [outgoingIF]: Potential nexthops ...
> aa:31:0e:4a:0f:1d 0.500s (255) aa:31:0e:4a:0f:1d [ mesh-vpn]: aa:31:0e:4a:0f:1d (255)
> 6a:4b:93:de:00:84 0.940s (255) 6a:4b:93:de:00:84 [ mesh-vpn]: 6a:4b:93:de:00:84 (255)
>
> The client should use 6a:4b:93:de:00:84 as a gatway, since it provides much higher data rates - however, it is stuck at aa:31:0e:4a:0f:1d.
I have observed the same behavior.
next prev parent reply other threads:[~2013-01-01 17:25 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 [this message]
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
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=50E31C20.6010604@altermundi.net \
--to=nicoechaniz@altermundi.net \
--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.