From: Alexander Morlang <alx@dd19.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 / certificates
Date: Tue, 06 Jan 2009 14:57:17 +0100 [thread overview]
Message-ID: <4963633D.2020306@dd19.de> (raw)
In-Reply-To: <200812191115.20610.neumann@cgws.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Axel Neumann schrieb:
> HI,
>
> I like brainstorming like this.
> We wanted batmand (and especially its core routing algorithm) to be decentral
> and simple. So no central point of control/failure and therefore also no HNA
> server. Of course there are many potential attack vectors in a community mesh
> and probably there will always be until you completely restrict the access.
> Therefore IMHO the preferable security to be solved should be:
>
> - detect and protect against (usually accidental) misconfigurations like
> duplicate addresses.
>
sure, a duplicate address is something the routingprotocoll has to
detect and to react on, but:
duplicate HNA are very importand and widely accepted in the internet
community, they are called anycast and are a vital instrument in network
design and deployment.
as an example, anycast ist used for dns root servers, 6to4 tunnel and
many other usecases.
i am still not understanding why you are discussing about removing such
important thing as anycast.
anycast is a way to use distributed services, as you can announce an
anycast address on every node, providing a specific service and packets
will get routed to the nearest service provider.
> - find mechanisms to limit the impact of denial of service or other attacks to
> the local environment (neighborhood).
>
<removed>
Gruss, Alex
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkljYz0ACgkQhx2RbV7T5aESngCgm0gopTcK+C17sHB29nz4jfsY
5JcAmgIS2EXnvL37QfFU/mAxnBRAQDMe
=nJZR
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-01-06 13:57 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
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 ` Alexander Morlang [this message]
2009-01-15 14:24 ` [B.A.T.M.A.N.] dublicate HNAs / certificates 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=4963633D.2020306@dd19.de \
--to=alx@dd19.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