b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] basic B.A.T.M.A.N-adv setup
Date: Tue, 20 Oct 2009 22:22:31 +0200	[thread overview]
Message-ID: <200910202222.36928.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <45f642440910201259j63a37a7bi58ea8b97a094a82f@mail.gmail.com>

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

Francesco wrote:
> Hi Sven,now I see what was wrong, I'm really feeling so stupid.. :)
> It was misleading that I reached the batman-adv download page (
> http://downloads.open-mesh.net/batman/stable/sources/batman-adv-kernelland/
>  ) browsing batman 0.3.2 download page (
> http://www.open-mesh.org/wiki/2009-06-13-batman-0-3-2-release ) and I got
> confused.

No reason to feel stupid. You aren't the first person which got confused by
the different implementations of the B.A.T.M.A.N. algorithm.

> I didn't read enough about batctl and its use against most recent
>  batman-adv version.
> My fault.
> 
> As soon as i get back to the lab I'll try latetest version of both
> batman-adv and batctl and see what comes out.

There is currently nothing like a stable branch. So if you want to have 0.1
with some backported stabilization patches you should look at the Debian
package of batman-adv-kernelland[1] and batman-adv-battool[2]. The source
packages of both packages include the separated patches[3].

But if you are currently in lab testing I would recommend to use both from svn
as batctl has some nice new features and changes in batman-adv-kernelland are
also looking quite interesting.

Best regards,
	Sven

[1] http://packages.debian.org/sid/batman-adv-source
[2] http://packages.debian.org/sid/batman-adv-battool
[3] http://git.debian.org/?p=collab-maint/batman-adv-kernelland.git;a=tree;f=debian/patches;hb=master

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

  reply	other threads:[~2009-10-20 20:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20 15:02 [B.A.T.M.A.N.] basic B.A.T.M.A.N-adv setup Francesco
2009-10-20 15:17 ` Sven Eckelmann
2009-10-20 15:23   ` Sven Eckelmann
2009-10-20 16:02   ` Francesco
2009-10-20 17:10     ` Sven Eckelmann
2009-10-20 17:17       ` Sven Eckelmann
2009-10-20 19:59         ` Francesco
2009-10-20 20:22           ` Sven Eckelmann [this message]
2009-10-21  6:54             ` Francesco
2009-10-21  7:05               ` Andrew Lunn
2009-10-21  7:35                 ` Francesco
2009-10-21 10:00                   ` Sven Eckelmann
2009-10-21 12:00                     ` Sven Eckelmann
2009-10-21 15:26                       ` [B.A.T.M.A.N.] [PATCH] Start to send originator messages when interface gets active Sven Eckelmann
2009-10-21 17:21                         ` [B.A.T.M.A.N.] [batman-adv] " Marek Lindner
2009-10-21 12:11                     ` [B.A.T.M.A.N.] basic B.A.T.M.A.N-adv setup Francesco
2009-10-20 15:33 ` 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=200910202222.36928.sven.eckelmann@gmx.de \
    --to=sven.eckelmann@gmx.de \
    --cc=b.a.t.m.a.n@lists.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;
as well as URLs for NNTP newsgroup(s).