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: Thu, 2 Aug 2007 16:26:21 +0200	[thread overview]
Message-ID: <200708021626.21405.axel@open-mesh.net> (raw)
In-Reply-To: <20070724152109.yhywdc2kj6skcgck@webmail.ddmesh.de>

Hello,

On Dienstag 24 Juli 2007, Freifunk Dresden wrote:
[...]
> Question 2:
>
> 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.

Indeed, seemed something has been missed (sorry for late reply). 
Can you try something above rv489 

debul-level 3 should show (batmand -c -d 3):
Adding route to 10.20.0.222/32 via 10.20.0.2 (table 65 - eth0:bat)
and 
ip route ls table 65
10.20.0.222 via 10.20.0.2 dev eth0  proto static

> Beside of this the Idea to add/delete HNA without stopping batmand
> would be good. e.g. batmand -c -a <add-hna>
>             batmand -c -A <del-hna>

I also like the idea of dynamically changing some parameters but on the other 
hand, what are the negative side-effects of restarting a daemon ? 
 - A client connected to the daemon might temporary loose connection
 - Do you know others?

[...]

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

  parent reply	other threads:[~2007-08-02 14:26 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
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 [this message]
  -- 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=200708021626.21405.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