public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Cc: Jernej Kos <kostko@unimatrix-one.org>
Subject: Re: [B.A.T.M.A.N.] Migration to Batman
Date: Thu, 12 Apr 2012 20:12:13 +0200	[thread overview]
Message-ID: <20120412181213.GF7664@lunn.ch> (raw)
In-Reply-To: <CAKLmikNQoxEDG-GSN-CG5Ox-=BE0DeL8uOYq_P-e5kA5FfzbDQ@mail.gmail.com>

On Thu, Apr 12, 2012 at 07:12:08PM +0200, Mitar wrote:
> Hi!
> 
> On Thu, Apr 12, 2012 at 5:36 PM, Andrew Lunn <andrew@lunn.ch> wrote:
> > Or, if you are in a transition phase, and don't mind your head
> > exploding, run olsr, babel, etc, on top of BATMAN to gateway between
> > the L2 meshes!
> 
> Can you please explain a bit more what are you thinking here?

Well, your infrastructure already speaks olsr, babel, or what every L3
mesh protocol you have. It knows how to advertise additional
routes. So make one or more of your BATMAN nodes L2 mesh also a L3
mesh node. These L3 mesh nodes will see each other over the mesh, and
they will see other L3 mesh nodes over what every network technology
you have between L2 meshes. These L3 mesh nodes should also be the
default router for the devices in the L2 mesh. The L2 mesh devices
will send there packets to a L3 mesh node. It will then route it,
maybe back over the mesh, or maybe over an inter mesh links, to where
ever it needs to go. If ICMP redirect works on your L2 and L3 nodes,
it should add host routes to the L2 nodes when they use the wrong
gateway out of the L2 mesh.

	Andrew

  reply	other threads:[~2012-04-12 18:12 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12 10:26 [B.A.T.M.A.N.] Migration to Batman Mitar
2012-04-12 10:36 ` Gioacchino Mazzurco
2012-04-12 12:00   ` Antonio Quartulli
2012-04-12 15:13     ` Mitar
2012-04-12 15:36       ` Andrew Lunn
2012-04-12 17:12         ` Mitar
2012-04-12 18:12           ` Andrew Lunn [this message]
2012-04-12 19:49             ` 3zl Trizonelabs
     [not found]       ` <CAOaDhSRTgejL5tzAnAx6wBso1sjWn_7bVuT6P1_C1qcVu25McQ@mail.gmail.com>
2012-04-12 15:37         ` Jernej Kos
2012-04-12 17:19           ` Mitar
2012-04-12 21:08           ` Mitar
2012-04-12 21:15             ` Gioacchino Mazzurco
2012-04-13  5:59             ` Andrew Lunn
2012-04-13  7:58               ` Mitar
2012-04-13  8:15                 ` Andrew Lunn
2012-04-13  8:41                   ` Mitar
2012-04-13  9:24                     ` Andrew Lunn
2012-04-13 13:24                       ` Mitar
2012-04-14  2:26                     ` Nicolás Echániz
2012-04-14  9:06                       ` Mitar
2012-04-16 10:25               ` Mitar
2012-04-16 10:37                 ` Marek Lindner
2012-04-16 10:46                   ` Mitar
2012-04-16 10:58                     ` Marek Lindner
2012-04-16 12:32                       ` Mitar
2012-04-16 12:40                         ` Antonio Quartulli
2012-04-16 13:59                           ` Mitar
2012-04-16 18:28                             ` Marek Lindner
2012-04-16 18:30                         ` Marek Lindner
2012-04-16 11:03                     ` Antonio Quartulli
2012-04-16 12:37                       ` Mitar
2012-04-12 17:10     ` Mitar
2012-04-12 22:13       ` Marek Lindner
2012-04-12 17:05   ` Mitar
2012-04-12 22:17     ` Marek Lindner
2012-04-13  6:22       ` Antonio Quartulli
2012-04-13  7:29         ` Mitar
2012-04-13  7:43           ` Andrew Lunn
2012-04-13  7:51             ` Mitar
2012-04-13  8:26               ` Andrew Lunn
2012-04-13  8:35                 ` Mitar
2012-04-13  8:52           ` Christian Huldt
2012-04-13 13:32             ` Mitar
2012-04-13 13:50               ` Andrew Lunn
2012-04-13 13:53                 ` Mitar

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=20120412181213.GF7664@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=kostko@unimatrix-one.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