All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
To: 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.] routing code re-organization / the road ahead
Date: Thu, 4 Aug 2011 10:29:32 +0200	[thread overview]
Message-ID: <201108041029.32930.lindner_marek@yahoo.de> (raw)
In-Reply-To: <20110803165018.GF9901@lunn.ch>

On Wednesday, August 03, 2011 18:50:18 Andrew Lunn wrote:
> > we discussed various options but at the end decided to move forward with
> > the  compile time option. Personally, I doubt many people will want the
> > new routing algorithm until it has been stabilized (we will provide a
> > 'default' option that enables B.A.T.M.A.N. IV).
> 
> So it is maybe not needed now, but once the code does start reaching
> stability, run time selection becomes more interesting.

Agreed.


> Interoperability has many meanings. I've seen it mean the protocol
> does not actively destroy the operation of another protocol. I've seen
> this in powerline networks. Company X proprietary powerline protocol
> is interoperable with HomePlug in that it will not destroy the
> HomePlug network if run in parallel with it. It won't talk to it
> either...

There is no difference between compile time and run time option - both won't 
destroy the other.


> By making it a runtime option, i don't need to recompile my kernel to
> swap from one to the other. I just need "batctl algo V" or "batctl
> algo IV". My kernel is interoperable, i just need to configure the
> mesh correctly for it to work.
> 
> What might also be interesting is
> batctl algo IV bat0
> batctl algo V bat1
> brctl addif br0 bat0
> brctl addif br0 bat1
> 
> It won't give optimal routes, but it at least gets the two meshs
> talking to each other.

True. That is an interesting point you are making here.


> > However, we are planing on integrating an extensible header format which 
> > allows to add features that will be backward compatible.
> 
> Ah, good. Is there any documentation about this?

I'll post a follow-up once it is available.

Regards,
Marek

  reply	other threads:[~2011-08-04  8:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03  7:52 [B.A.T.M.A.N.] routing code re-organization / the road ahead Marek Lindner
2011-08-03  7:52 ` [B.A.T.M.A.N.] [PATCH 1/4] batman-adv: rename all instances of batman_packet to batman_ogm_packet Marek Lindner
2011-08-03  7:53   ` [B.A.T.M.A.N.] [PATCH 2/4] batman-adv: agglomerate all batman iv ogm processing functions in a single file Marek Lindner
2011-08-18 10:34     ` Marek Lindner
2011-08-03  7:53   ` [B.A.T.M.A.N.] [PATCH 3/4] batman-adv: move routing packet initialization into corresponding file Marek Lindner
2011-08-18 10:35     ` Marek Lindner
2011-08-03  7:53   ` [B.A.T.M.A.N.] [PATCH 4/4] batman-adv agglomerate all batman iv ogm senbding functions in the batman iv file Marek Lindner
2011-08-18 10:36     ` Marek Lindner
2011-08-18 10:33   ` [B.A.T.M.A.N.] [PATCH 1/4] batman-adv: rename all instances of batman_packet to batman_ogm_packet Marek Lindner
2011-08-03  8:30 ` [B.A.T.M.A.N.] routing code re-organization / the road ahead Andrew Lunn
2011-08-03 14:39   ` Marek Lindner
2011-08-03 16:50     ` Andrew Lunn
2011-08-04  8:29       ` Marek Lindner [this message]
2011-08-12 13:15       ` Simon Wunderlich

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=201108041029.32930.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.