public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Daniel Poelzleithner <poelzi@poelzi.org>
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.] dynamic gateway / hna / services
Date: Wed, 25 Jul 2007 17:19:30 +0200	[thread overview]
Message-ID: <46A76A02.7040600@poelzi.org> (raw)
In-Reply-To: <46A766DC.5030509@dd19.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alexander Morlang wrote:

> Sorry, but this does not look like a decentral "all are equal" solution,
> more like a centralized service.

yes, some sort of. there is a master dns server that ensures uniquiness
of domains and at least knows how is responsible for the zones. nothing
forbids you to mirror the zones on all nodes, i just don't see any sense
in it. 4-5 slave servers should be enough even for a large city. every
zone admin can run his own masters if he wish to.
responses will be fast and redundant even if some of them die. and you
can use real dns software and can run really large zones with large
entries without wasting pressures router ram. reverse dns, dyndns, like
my notebooks is always aestas.poelzi.ff if its somewhere in freifunk...
very cool stuff. dns loc records, very nice. combined with reverse dns
allows very rfc conform routings visualisations... even can show nodes
that are offline....

> i think, something like the olsr-bmf would be more interesting, it gets
> metrics from the underlying meshrouting protocol but does its own
> message forwarding.

what does bmf have to do with dns. if you think about forwarding name
entries as broadcasts: this is just a wast of bandwidth. i don't even
start to think about renaming my node to www.google.de and see what
happens ;)

kindly regards
 daniel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: GnuPT 2.7.2
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGp2oCy/mkIQp7AD0RAstwAJ4rptMfmyEGLpFbQRVKPcLB4yIafACg3hPi
GJ7T8PzUGVpO8Cfh9A/mj9A=
=Zv8z
-----END PGP SIGNATURE-----

  reply	other threads:[~2007-07-25 15:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24 13:21 [B.A.T.M.A.N.] dynamic gateway / hna / services Freifunk Dresden
2007-07-24 18:35 ` Daniel Poelzleithner
2007-07-25 11:50   ` Alexander Morlang
2007-07-25 12:52     ` tetzlav
2007-07-25 15:06       ` Alexander Morlang
2007-07-25 15:19         ` Daniel Poelzleithner [this message]
2007-07-25 16:05           ` Alexander Morlang
2007-07-25 17:25             ` Daniel Poelzleithner
2007-07-26 12:33               ` Alexander Morlang
2007-07-25 16:21         ` clauz
2007-07-25 15:05     ` Daniel Poelzleithner
2007-07-25 14:56   ` Marek Lindner
2007-07-27 14:07 ` Marek Lindner
2007-07-27 14:43   ` Aaron Kaplan
2007-07-27 15:23     ` Marek Lindner
2007-07-27 16:03       ` Aaron Kaplan
2007-07-27 16:40         ` Marek Lindner
2007-07-27 20:41           ` Aaron Kaplan
2007-07-28  8:03             ` Axel Neumann
2007-07-27 14:59   ` Lui
2007-07-27 15:31     ` Marek Lindner
2007-08-02 14:26 ` Axel Neumann
  -- strict thread matches above, loose matches on Subject: below --
2007-08-03  9:31 Freifunk Dresden
2007-08-04  9:43 ` Axel Neumann
2007-08-04 21:38   ` Freifunk Dresden
2007-08-20 13:10   ` Alexander Morlang
2007-08-04 10:34 ` 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=46A76A02.7040600@poelzi.org \
    --to=poelzi@poelzi.org \
    --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