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 19:25:25 +0200	[thread overview]
Message-ID: <46A78785.9040501@poelzi.org> (raw)
In-Reply-To: <46A774DA.4070702@dd19.de>

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

Alexander Morlang wrote:


> with the small sideeffect of a small group controlling the a-server.

yes. i prefer a group of people i can trust controlling the a-server
then trusting every packet someone, somewhere in the network is sending.
hello, i'm www.google.de, how are you :)
by the way, ok, with hna annoucements faking some site is still easy,
but just because one instance of the network has problems, there is no
need to repeat ourself. i.e. dnssec for example.


> in opposite of the name plugin wich uses olsr for flooding informations,
> bmf does its own flooding. as batman does not support flooding custom
> payload, this would be the only way of distributing information
> efficient and decentral as long there is a way to get the metrics from
> the routing protocol.

by the way, is see it comming. packetstorms through circular broadcast
packets. i have SEEN links that have 1.5 seconds delay, god knows why.
two of those and you crack the duplicate lookup buffer...

i'm not against broadcast in general. but everything i get which i'm
actually not interested in, or is duplicated information (something i
already know), is simply a wast of bandwidth. It's easy to say, ohh,
some bytes here, some bytes there. if you look at a real mesh, you
simply see to much useless traffic. there are nodes in freifunk leipzig,
that have 80kb/s olsr traffic. 80kb/s, some people would dream about
this speed, but just wasted away....

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

iD8DBQFGp4dyy/mkIQp7AD0RAnf8AKCMSfalwb81SOoq2DTvntK4c8nhqQCggAQo
CzV7Nu+t2wdCx6V3tKpaImk=
=/JIy
-----END PGP SIGNATURE-----

  reply	other threads:[~2007-07-25 17:25 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
2007-07-25 16:05           ` Alexander Morlang
2007-07-25 17:25             ` Daniel Poelzleithner [this message]
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=46A78785.9040501@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