From: Mitar <mitar@tnode.com>
To: Battle of the Mesh Mailing List <battlemesh@ml.ninux.org>
Cc: Juliusz Chroboczek <jch@pps.jussieu.fr>,
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.] [Battlemesh] Battlemesh v5 tests
Date: Sat, 10 Mar 2012 08:20:20 -0800 [thread overview]
Message-ID: <4F5B7F44.3000803@tnode.com> (raw)
In-Reply-To: <7ilin9voj9.fsf@lanthane.pps.jussieu.fr>
Hi!
> (In a pure mesh protocol, routers with multiple interfaces should
> probably appear as multiple nodes;
Why? I think it is good that the routing protocol knows that something
(some interfaces) belongs together (node).
Mitar
next prev parent reply other threads:[~2012-03-10 16:20 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F4F6D18.3070403@ninux.org>
[not found] ` <201203070156.51341.lindner_marek@yahoo.de>
[not found] ` <20120306193643.GM12778@kerneis.info>
[not found] ` <201203070552.33850.lindner_marek@yahoo.de>
[not found] ` <7i62egijym.fsf@lanthane.pps.jussieu.fr>
[not found] ` <20120307144709.GA19891@ritirata.org>
[not found] ` <7ieht4mnnp.fsf@lanthane.pps.jussieu.fr>
[not found] ` <20120307171751.GC1389@ritirata.org>
2012-03-07 22:18 ` [B.A.T.M.A.N.] [Battlemesh] Battlemesh v5 tests Gabriel Kerneis
2012-03-09 8:56 ` Simon Wunderlich
2012-03-09 9:17 ` Benjamin Henrion
2012-03-09 9:42 ` Marek Lindner
2012-03-09 9:56 ` Benjamin Henrion
2012-03-09 10:02 ` Marek Lindner
2012-03-09 10:26 ` Juliusz Chroboczek
2012-03-09 10:36 ` Roger Baig Viñas
2012-03-09 10:55 ` Mitar
2012-03-09 10:59 ` Gabriel Kerneis
2012-03-09 11:39 ` [B.A.T.M.A.N.] Diversity in BATMAN [was: Battlemesh v5 tests] Juliusz Chroboczek
2012-03-09 12:44 ` [B.A.T.M.A.N.] [Battlemesh] " andrew.lunn
2012-03-09 13:10 ` [B.A.T.M.A.N.] [Battlemesh] Diversity in BATMAN Juliusz Chroboczek
2012-03-09 13:25 ` Antonio Quartulli
2012-03-09 13:36 ` andrew.lunn
2012-03-09 14:07 ` Benjamin Henrion
2012-03-09 14:36 ` Marek Lindner
2012-03-09 15:25 ` Benjamin Henrion
2012-03-09 15:40 ` Marek Lindner
2012-03-09 15:43 ` Andrew Lunn
2012-03-09 16:07 ` Benjamin Henrion
2012-03-09 16:21 ` Andrew Lunn
2012-03-09 16:38 ` Gabriel Kerneis
2012-03-09 16:57 ` Andrew Lunn
2012-03-09 18:17 ` Andrew Lunn
2012-03-11 1:22 ` Juliusz Chroboczek
2012-03-11 1:37 ` Mitar
2012-03-11 8:53 ` Antonio Quartulli
2012-03-11 15:53 ` Juliusz Chroboczek
2012-03-11 16:02 ` Mitar
2012-03-11 20:39 ` Simon Wunderlich
2012-03-13 3:37 ` Mitar
2012-03-11 1:21 ` Juliusz Chroboczek
2012-03-09 11:12 ` [B.A.T.M.A.N.] [Battlemesh] Battlemesh v5 tests Gabriel Kerneis
2012-03-09 11:26 ` Marek Lindner
2012-03-09 12:04 ` Gabriel Kerneis
2012-03-09 12:39 ` Antonio Quartulli
2012-03-09 12:57 ` Gabriel Kerneis
2012-03-09 13:03 ` Antonio Quartulli
2012-03-09 13:09 ` andrew.lunn
2012-03-09 13:46 ` Gabriel Kerneis
2012-03-09 14:26 ` Juliusz Chroboczek
2012-03-10 16:20 ` Mitar [this message]
2012-03-11 8:45 ` Henning Rogge
2012-03-11 15:32 ` [B.A.T.M.A.N.] Network models [was: Battlemesh v5 tests] Juliusz Chroboczek
2012-03-11 16:15 ` Mitar
2012-03-09 13:49 ` [B.A.T.M.A.N.] [Battlemesh] Battlemesh v5 tests Gabriel Kerneis
2012-03-09 14:15 ` Andrew Lunn
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=4F5B7F44.3000803@tnode.com \
--to=mitar@tnode.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=battlemesh@ml.ninux.org \
--cc=jch@pps.jussieu.fr \
/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