From: Axel Neumann <neumann@cgws.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] dublicate HNAs
Date: Thu, 11 Dec 2008 11:54:31 +0100 [thread overview]
Message-ID: <200812111154.31726.neumann@cgws.de> (raw)
In-Reply-To: <3ca03f2b6ae1c3c84704f2ce5e8fd89a.squirrel@wm.ddmesh.de>
Hi,
On Dienstag 09 Dezember 2008, Stephan Enderlein (Freifunk Dresden) wrote:
> -----------
> Another question: in previous versions I have seen that if two batmand
> announce the same HNA ip (-a) one of the batmand are ignored and complete
> ignored any batmand traffic. As result the node was removed from any
> batmand list and was not reachable anymore.
> -----------
And it should be also the current behavior of bmx. The background is:
BMX currently does NOT support anycast routing.
Therefore in practical terms, if two nodes are announcing the same IP it is
effectively an IP doubler. Such a scenario triggers the dublicate-address
detection which results in ignoring the younger of the two nodes announcing
this IP.
With the batman routing algorithm it is indeed difficult to do a consistent
anycast routing. Therefore I've decided to protect against casual duplicate
address announcements with the described behavior.
Older versions (2007 and before) tended to have chaotic routing entries due to
duplicated entries or removals of HNA routing entries.
When dynamically adding an HNA (using e.g. bmxd -ca 1.2.3.4/32) the daemon
checks if other nodes are already announcing this specific HNA. If this is
the case the announcement is rejected and a warning should be given in
debuglevel 3. You can always inspect current announcements from other nodes
using debug-level 9.
This debug-level also differentiates between announced interfaces (e.g.
1.2.3.4/IF) and networks (e.g. 1.2.3.4/32). ( the idea for the future was,
that network announcements should become anycast announcements )
Indeed it is a problem when a daemon is started from the beginning with a
duplicate HNA announcement. In this situation the daemon can hardly check if
the network is already announced. Then, only his neighboring nodes are aware
of the IP doubler. They will ignore everything from this node and cause a
warning in debug level 0.
hope this clarifies a bit.
/axel
next prev parent reply other threads:[~2008-12-11 10:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 11:30 [B.A.T.M.A.N.] batman-exp rev.1154 still using 94% CPU load Stephan Enderlein (Freifunk Dresden)
2008-12-02 12:06 ` Axel Neumann
2008-12-02 13:59 ` Stephan Enderlein (Freifunk Dresden)
2008-12-09 9:28 ` Stephan Enderlein (Freifunk Dresden)
2008-12-09 10:22 ` Stephan Enderlein (Freifunk Dresden)
2008-12-11 10:54 ` Axel Neumann [this message]
2008-12-11 14:01 ` [B.A.T.M.A.N.] dublicate HNAs Freifunk
2008-12-12 10:46 ` Axel Neumann
2008-12-12 23:51 ` Stephan Enderlein (Freifunk Dresden)
2008-12-17 20:14 ` Axel Neumann
2008-12-18 11:11 ` [B.A.T.M.A.N.] dublicate HNAs / batmand / certificates Stephan Enderlein (Freifunk Dresden)
2008-12-19 10:15 ` [B.A.T.M.A.N.] dublicate HNAs " Axel Neumann
2008-12-19 11:06 ` Stephan Enderlein (Freifunk Dresden)
2008-12-19 11:19 ` Stephan Enderlein (Freifunk Dresden)
2008-12-24 18:24 ` [B.A.T.M.A.N.] Testing Batman Resul Cetin
2009-01-06 13:57 ` [B.A.T.M.A.N.] dublicate HNAs / certificates Alexander Morlang
2009-01-15 14:24 ` Axel Neumann
2008-12-17 12:19 ` [B.A.T.M.A.N.] Can't build a mesh network Resul Cetin
2008-12-17 13:57 ` Resul Cetin
2008-12-17 17:46 ` elektra
2008-12-18 6:32 ` 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=200812111154.31726.neumann@cgws.de \
--to=neumann@cgws.de \
--cc=b.a.t.m.a.n@open-mesh.net \
/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