public inbox for b.a.t.m.a.n@lists.open-mesh.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.] Migration to Batman
Date: Mon, 16 Apr 2012 20:28:03 +0200	[thread overview]
Message-ID: <201204162028.03631.lindner_marek@yahoo.de> (raw)
In-Reply-To: <CAKLmikOLXsv_JmeM73cFq09LPZGrOgd_rWd158c7pXpAFKcimg@mail.gmail.com>

On Monday, April 16, 2012 15:59:11 Mitar wrote:
> But also general subnet routing so that we do not need to bridge home
> networks into the mesh, but route to them.
> 
> So, about my question from before about other routing protocols, like
> OSPF, it probably still consumes bandwidth to detect node
> availability, no?

Unless somebody shows up with real life experience regarding the routing 
daemons you consider using you have to test it yourself. 
I am sure there are mechanisms as network failures were not a new invention 
that came with wifi. ;)

Cheers,
Marek

  reply	other threads:[~2012-04-16 18:28 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
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 [this message]
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=201204162028.03631.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox