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: Wed, 17 Dec 2008 21:14:43 +0100 [thread overview]
Message-ID: <200812172114.43427.neumann@cgws.de> (raw)
In-Reply-To: <4942F8FA.4040600@ddmesh.de>
Hi,
On Samstag 13 Dezember 2008, Stephan Enderlein (Freifunk Dresden) wrote:
> Hi,
>
> I'm not so deep involved in batman routing to find a solution. I hope
> you can find a way. But for now it is not so important.
> But if one node announces a HNA and a different node that just has fun to
> "turn off" this node can simply send the same HNA. If you say the first
> HNA is the right one, then what happens when this node gets the forced
> disconnection after 24 hours by its internet provider?
Theoretically, if the node can reestablish a new connection after its forced
disconnection within the dad timeout (100secs by default) then it should not
be kicked out. But, the preliminary for this is that: the node must re-appear
using the same primary IP for its primary interface and continuing with the
foreseen sequence-number range.
best,
axel
>
> I think it is difficult to find a solution for this. The best is to keep
> all nodes active but kill the HNA if not reachable?
>
> /Stephan
>
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
next prev parent reply other threads:[~2008-12-17 20:14 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 ` [B.A.T.M.A.N.] dublicate HNAs Axel Neumann
2008-12-11 14:01 ` Freifunk
2008-12-12 10:46 ` Axel Neumann
2008-12-12 23:51 ` Stephan Enderlein (Freifunk Dresden)
2008-12-17 20:14 ` Axel Neumann [this message]
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=200812172114.43427.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