From: Bruno Randolf <br1@einfach.org>
To: Antonio Quartulli <ordex@autistici.org>
Cc: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] horst and batman-adv
Date: Tue, 09 Apr 2013 09:57:17 +0100 [thread overview]
Message-ID: <5163D7ED.3030204@einfach.org> (raw)
In-Reply-To: <20130409062848.GA3624@ritirata.org>
On 04/09/2013 07:28 AM, Antonio Quartulli wrote:
> On Tue, Apr 09, 2013 at 12:28:11AM -0400, cmsv wrote:
>> I found about Horst a few years ago when i got to know olsr and it's
>> usefulness for olsr mesh networks and recently decided to check it out
>> again.
>> Although i do see an option for batman i am not sure if it refers to
>> batmand or batman-adv and as i wait for an answer from it's developer.
>>
>> My question is if there are any plans for a similar tool from open-mesh
>> side.
>> I am also curious to know if someone is using it with batman-adv or
>> anything equivalent/similar or close ?
>> What are our options.
>>
>> http://br1.einfach.org/tech/horst/
>
> Hello cmsv,
>
> I've used it once, but without any interaction with batman-adv or olsr.
> I just looked for the pollution in the channels.
>
> How is it supposed to interact with the protocol?
Hello!
I'm the author of "horst". There is not much interaction with the
protocol, except that the packets are marked as such, e.g. nodes which
send OLSR packets are marked as OLSR nodes, nodes which send batman (L3)
messages marked as batman nodes. It's quite easy to add the same for
batman-adv, but it's not there at the moment.
bruno
next prev parent reply other threads:[~2013-04-09 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 4:28 [B.A.T.M.A.N.] horst and batman-adv cmsv
2013-04-09 6:28 ` Antonio Quartulli
2013-04-09 8:57 ` Bruno Randolf [this message]
2013-04-09 9:01 ` Antonio Quartulli
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=5163D7ED.3030204@einfach.org \
--to=br1@einfach.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=ordex@autistici.org \
/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