From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <4942F8FA.4040600@ddmesh.de>
Date: Sat, 13 Dec 2008 00:51:22 +0100
From: "Stephan Enderlein (Freifunk Dresden)" <freifunk@ddmesh.de>
MIME-Version: 1.0
References: <83b3410f8105237b1e68c92065dec7d0.squirrel@wm.ddmesh.de>	<200812111154.31726.neumann@cgws.de>
	<49411D3D.90301@ddmesh.de> <200812121146.26579.neumann@cgws.de>
In-Reply-To: <200812121146.26579.neumann@cgws.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [B.A.T.M.A.N.] dublicate HNAs
Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
List-Id: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n.open-mesh.net>
List-Unsubscribe: <https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n>,
	<mailto:b.a.t.m.a.n-request@open-mesh.net?subject=unsubscribe>
List-Archive: <http://list.open-mesh.net/pipermail/b.a.t.m.a.n>
List-Post: <mailto:b.a.t.m.a.n@open-mesh.net>
List-Help: <mailto:b.a.t.m.a.n-request@open-mesh.net?subject=help>
List-Subscribe: <https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n>,
	<mailto:b.a.t.m.a.n-request@open-mesh.net?subject=subscribe>
To: The list for a Better Approach To Mobile Ad-hoc Networking <b.a.t.m.a.n@open-mesh.net>

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?

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