public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: micheldegeofroy@gmail.com
Cc: b.a.t.m.a.n@lists.open-mesh.org, Marek Lindner <lindner_marek@yahoo.de>
Subject: [B.A.T.M.A.N.] customize batman-adv for a new dashboard (was: Marek Linder)
Date: Tue, 7 Jun 2011 18:06:53 +0200	[thread overview]
Message-ID: <201106071806.54498.sven@narfation.org> (raw)
In-Reply-To: <BANLkTimEcKsGF7-2sn6NL=cEByrfWQUUZw@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 2422 bytes --]

Michel de Geofroy wrote:
> Hi Sven, Marek, All
> 
> First thanks for the feedback really appreciated,  I  actually dont know if
> it is Batman or the Robin script that we would need to customize or both
> not being a programmer its hard for me to tell...

I try to help. batman-adv can be understood as layer above the data link layer 
and below the network layer. When you don't need to get the discovery or 
routing/path finding algorithms to be changed then your actual target isn't 
batman-adv.

> At present the dashboard we have developed supports Olsr Robin and we would
> like to also support Batman Robin unfortunately Antonio is very occupied
> developing another firmware called Mesh Root and as far as I understand the
> development of Batman Robin is at a standstill.
> 
> To answer your comment:
> 
> "Why should batman-adv be customized for a dashboard? Shouldn't be the
> dashboard customized for batman-adv?"
> 
> Maybe Batman already has it all and it is just a question of updating the
> robin script I have no idea :( but I know I need someone who dose
> understand and is able to provide the right kind of support for the
> firmware.

I don't see any kind of requirement for batman-adv in this mail - so I can't 
tell.

> We are NOT looking for proprietary firmware even though we are ready
> to finance a firmware that would function with our dashboard but would stay
> open source.

batman-adv and batmand are not some kind of firmware, but daemons/kernel-
modules for neighbor discovery/path finding in already established link layer 
connections.

> I am not even sure we are knocking on the right door since as far as I
> understand Robin is more like a script.

Never touched it - so I can't exactly specify what ROBIN is.

> Being new to Batman any help appreciated
> 
> Some Features needed
> 
> 1. Connect to Alien AP as Client.
> 2. Enable to test connection speed from the gateway to the dashboard
> (similar to repeaters)
> 3. Support for N and 5ghz
> 4. Branding
> 5. Robin Batman Adv Firmware Update

All those topics aren't batman-adv related topics, but related to the 
firmware/helper scripts. I know that Marek is working on a complete 
environment (hw, firmware, helper utilities, dashboard, ...). But I would 
guess that you will only get some promo material for the open-mesh.com ng 
firmware....

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

           reply	other threads:[~2011-06-07 16:06 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <BANLkTimEcKsGF7-2sn6NL=cEByrfWQUUZw@mail.gmail.com>]

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=201106071806.54498.sven@narfation.org \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=lindner_marek@yahoo.de \
    --cc=micheldegeofroy@gmail.com \
    /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