From: Gui Iribarren <gui@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.] lost connection to a client / Q: transglobal-table
Date: Sun, 03 Nov 2013 10:42:30 +0100 [thread overview]
Message-ID: <52761A86.5080106@altermundi.net> (raw)
In-Reply-To: <20131103091832.GR6252@medion.lan>
On 11/03/2013 10:18 AM, Bastian Bittorf wrote:
> * Gui Iribarren <gui@altermundi.net> [03.11.2013 09:52]:
>>> Each node has a macvlan called 'gateway0' which has the IP 192.168.0.1/32
>>> This is just an IP which every DHCP-Client gets for "default-gateway".
>>> (so the gateway is the node itself and not the internet-offering-node).
>>> This looks like this:
>>>
>>> root@node222hybrid:~ ip address show dev gateway0
>>> 15: gateway0@br-mybridge: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500
>>> qdisc noqueue state UNKNOWN group default
>>> link/ether 02:00:c0:ca:c0:1a brd ff:ff:ff:ff:ff:ff
>>
>> if this mac (02:00:c0:ca:c0:1a) exists on several different nodes
>> that are not connected by a real ethernet backbone (and BLA2 enabled)
>> then batman goes mushroom tripping, since it 'sees' that MAC as a
>> non-mesh-client that is everywhere at the same time, and tries to
>> roam it around, creating funny symptoms (like DUPs and such)
>
> BINGO! thank you Gui - if i read the old mails, i can even see it
> i the transglobal table. if i look into the mesh, it pop's up on
> random nodes with random originators. yes: mushroom tripping 8-)
>
> i will try the ebtables approach, but i dont like it.
> IMHO it's more elegant to just 'ignore' this mac by the
> daemon itself:
According to the (misleading, by definition :P) docs
http://www.open-mesh.org/projects/open-mesh/wiki/Connecting-Batman-adv-clouds
it shouldn't quite ignore it, but instead properly support this
"anycast" MAC, taking advantage of the "Bridge Loop Avoidance II
component" even when there's no physical backbone between nodes.
meanwhile, at the batcave... (2013/10/14)
d0tslash: guii: we don't have anycast support
d0tslash: yet
guii: ...?
d0tslash: if you have the same mac address on multiple nodes
(without bla), it will roam
guii: oh!
d0tslash: hm, it might work if you have bla enabled and the nodes
are connected via the same ethernet
d0tslash: but otherweise it won't work
d0tslash: because it is supposed to roam :)
d0tslash: so you won't have that feature for now, i'm afraid
d0tslash: it is still on our "feature todo" list
so, given there will be MACs that roam (laptops, phones...) and MACs
that don't (anycast), i can imagine some kind of regexp matching that
will say "don't roam these kind of MACs, instead, consider them anycast
macs and use bla2 magic"
# batctl anycast EE:C4:57:00:00:00/32
...until then, ebtables WORKSFORME :D
and all this doesn't make batman-adv any less awesome than what it was
already ;)
btw, even with the ebtables rule, we had to turn off DAT in a scenario
equivalent to yours, because the DAT cache was also acting funny (DUP
arp replies from each node in the cloud)
haven't got around to properly debug it / report it, but still, be warned :)
>
> To the devs: is this possible?
>
> bye, bastian
>
next prev parent reply other threads:[~2013-11-03 9:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 7:55 [B.A.T.M.A.N.] lost connection to a client / Q: transglobal-table Bastian Bittorf
2013-11-01 12:36 ` Antonio Quartulli
2013-11-01 14:33 ` Bastian Bittorf
2013-11-01 14:39 ` Antonio Quartulli
2013-11-01 15:16 ` Bastian Bittorf
2013-11-03 7:10 ` Gui Iribarren
2013-11-03 9:18 ` Bastian Bittorf
2013-11-03 9:42 ` Gui Iribarren [this message]
2013-11-23 9:24 ` Bastian Bittorf
2013-11-23 16:15 ` Antonio Quartulli
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=52761A86.5080106@altermundi.net \
--to=gui@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox