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: Tue, 24 Jul 2007 20:35:21 +0200	[thread overview]
Message-ID: <46A64669.5050604@poelzi.org> (raw)
In-Reply-To: <20070724152109.yhywdc2kj6skcgck@webmail.ddmesh.de>

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

Freifunk Dresden wrote:

> I'm currently checking how the HNA is working, but until now I can not
> see any HNA on a second node. Firewall is enabled completely for both
> nodes and each node sees the other nodes. I call batmand as follow:
> Node1: batmand -t 63 -a 141.56.0.0/16 wlan0 bbs /t 2 bbc /t 2
> Node2: batmand -t 63 eth1 bbs /t 2 bbc /t 2

> 
> But batmand -c -d 4 does not show any HNA messages and no HNA entry is
> stored in   routing table.

mmhh, the hna announcments are written into another routing table, have
you checked that ?

> If a node offers a ftp server (portforwarding) I like to offer this
> "service" via batmand like olsrd.
> A generic solution would be good to just allow to send user text
> messages with the OGM.

This is a bad idea in my opinion. A routing protocol has one purpose
which is routing, not flooding 99% useless information just because it
COULD.

i think the right approch for service discovery is using something like
dns for example. dns is very small overheaded, allows great redundancy,
works on demand...

using TXT and SRV records, a good dns infrastructure and user frontend,
it should be easy to publish services.

here in leipzig we already layed the ground stones for a widespanning,
redundant dns network using anycast ips for redundancy.

http://wiki.freifunk.net/FF-Zone

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

iD8DBQFGpkZpy/mkIQp7AD0RAhrlAKCVDRFsf+6+909tsAxtCFM3oZSxugCfdKsT
sGLdwUFF9ckhxfLHikdfwP8=
=DW4D
-----END PGP SIGNATURE-----

  reply	other threads:[~2007-07-24 18:35 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 [this message]
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
  -- 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=46A64669.5050604@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