-----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-----