From: Mitar <mmitar@gmail.com>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Jernej Kos <kostko@unimatrix-one.org>
Subject: [B.A.T.M.A.N.] Migration to Batman
Date: Thu, 12 Apr 2012 12:26:52 +0200 [thread overview]
Message-ID: <CAKLmikNxzz_zNwui4xejaAgvXXsHrTUGCPG+UT-cSH5iP3cEJw@mail.gmail.com> (raw)
Hi!
I really liked your client roaming support presented at Battlemesh.
But I am still afraid to deploy Batman in the network. As I
understand, we should be migrating the whole network at same time each
time a new version of Batman (or Linux kernel) is released, because
you do not keep things backwards compatible? How serious is this
limitation in practice?
I am also a bit afraid of L2 meshing. How problematic are floods in
the network in practice? Like people broadcasting stuff and so on? Are
there any filters possible for this?
We have a setup where nodes have WiFi connections and VPN links to
central server. We are thinking of migration OpenVPN to L2TP tunnels,
so on the central server there will be many tunnels dynamically
created as nodes connect and disconnect. Is Batman able to add
interfaces it operates during run-time? Probably we should not just
bridge all tunnels and run Batman on top of that? This would probably
hide that there are different links bellow from Batman? Or not? (For
example, on OLSR we should not do this, because then nodes would
discover each other over server as one hop/direct neighbors.)
Mitar
next reply other threads:[~2012-04-12 10:26 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 10:26 Mitar [this message]
2012-04-12 10:36 ` [B.A.T.M.A.N.] Migration to Batman 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
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=CAKLmikNxzz_zNwui4xejaAgvXXsHrTUGCPG+UT-cSH5iP3cEJw@mail.gmail.com \
--to=mmitar@gmail.com \
--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 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.