public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Axel Neumann <axel@open-mesh.net>
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: Sat, 4 Aug 2007 11:43:36 +0200	[thread overview]
Message-ID: <200708041143.37165.axel@open-mesh.net> (raw)
In-Reply-To: <20070803113132.f7ij8uf21xwsog8o@webmail.ddmesh.de>

Hello!

On Freitag 03 August 2007, Freifunk Dresden wrote:
> Hello,
> I didn't get the email for this request, so the mailling list thread
> my be brocken.
strange, anybody else experienced problems?

[...]

> > > I'm currently checking how the HNA is working, but until now I can not
[...]
> I have checked out the rv491 and it seems working. In my test environment I
> use a laptop (i386) and two wrt54gl. The wrt shows at "-d3" that the
> announced HNA is added/deleted every 1-5 seconds. The wrt that has a
> greater distance (5meter 2 walls between) adds and deletes the HNA in a
> highe frequency than the
> wrt that is about 50cm away.
> I think that HNA should not be deleted to fast because someone that is
> using this "bad" connection will get often error messages during
> surfing that the rout e is not found. It would be better if just the
> connection slow because of transmistion errors.

that should not be the case! You say even with the stable connection to your 
near-by WRT that the HNA is added/deleted every 1 - 5 SECONDS ! And even more 
often at the distant WRT (so added/deleted every SECOND ?).
Can you describe the setup and parametrization in more detail? 

> > [...]
> >
> > > Another Idea of the "-m" is to differenciate this parameter to -M
> > > <"message"> and -m <send-script>. by calling batmand -c -m send-script,
> > > batmand can setup stdin/stdou as binary file handle and fill a user-OGM
> > > with binary data that is then send.
> >
> > Even if such message-flooding ist not implemented I just thought of
> > whether there exist some standardized formats to announce such
> > services (maybe the community network markup language CNML idea) ?
> > ciao, axel
>
> I have looked through the code and have seen that the HNA is simply
> appended to
> the end of a message. if we want to send other information a TLV structure
> is needed (Tag-length-value). Batmand can ignore unknown Tags and is
> still working in the network. At moment the whole network needs an
> update at same time, because old batmand will interpret any data as HNA.
> I hope I'm not wrong :)

Do you really think of a human-readable ascii string that you want to flood 
with an arbitrary length over the mesh with content like: "Hello take a cool 
beer and see my fancy cool movie torrent-server at 105.10.bla.bub". Iam not 
against such communication but...

default OGM size: 10 bytes
OGM + HNA size: 15 bytes
OGM + example-TLV-ascii message: 95 bytes

... I am a bit scared about the amount of data which would be flooded over the 
mesh (at every originator interval) with no means for stopping the sources.

Therefore i asked if anybody knows a decent forman for describing such 
services (preferably in a short and machine readable notation). 
Perhaps another approach is to just have a kind of key-to-service list 
(similar to /etc/services with a 16bit key) just roughly indicating the type 
of offered service together with another port/ip  where further information 
(of arbitrary length) about the indicated service can be retrieved.
This would also allow to outsource part of the service-discovery to another 
daemon.


greetings,
axel

  reply	other threads:[~2007-08-04  9:43 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-03  9:31 [B.A.T.M.A.N.] dynamic gateway / hna / services Freifunk Dresden
2007-08-04  9:43 ` Axel Neumann [this message]
2007-08-04 21:38   ` Freifunk Dresden
2007-08-20 13:10   ` Alexander Morlang
2007-08-04 10:34 ` Marek Lindner
  -- strict thread matches above, loose matches on Subject: below --
2007-07-24 13:21 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
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

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=200708041143.37165.axel@open-mesh.net \
    --to=axel@open-mesh.net \
    --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