From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] BATMAN routing (via gate0)
Date: Sun, 23 Nov 2008 13:16:27 +0100 [thread overview]
Message-ID: <20081123121627.GA15419@pandem0nium> (raw)
In-Reply-To: <200811231137.11082.lindner_marek@yahoo.de>
[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]
Hey,
On Sun, Nov 23, 2008 at 11:37:10AM +0800, Marek Lindner wrote:
> On Sunday 23 November 2008 05:05:36 Derek C wrote:
> > Does this mean that the mesh nodes cannot ping all the other nodes? This
> > is if there is no routing to allow the nodes talk to "far-away" nodes not
> > within their own AdHoc single-hop network?
>
> May be I was not clear enough:
> * You can ping every batman node in range.
> * Too far away nodes (out of range) obviously can't be pinged.
> * If you have multiple subnetworks which could ping each other but are routed
> differently you just have to make sure the routing is ok. Using HNA is one
> possible solution.
just a note so we don't confuse the terms:
Marek means with "range" where the communication can practically succeed, even
over multiple hops. As you have some probablity to lose packets on each
hop, the communication becomes "practically" unusable over very long
distances, e.g. >10 hops (depending on your network setup and
environment ...).
Note that this range is not the single-hop range.
regards,
Simon
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-11-23 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 16:20 [B.A.T.M.A.N.] BATMAN routing (via gate0) Derek C
2008-11-22 16:35 ` Marek Lindner
2008-11-22 21:05 ` Derek C
2008-11-23 3:37 ` Marek Lindner
2008-11-23 12:16 ` Simon Wunderlich [this message]
2008-11-23 19:50 ` Derek C
2008-11-24 2:24 ` Marek Lindner
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=20081123121627.GA15419@pandem0nium \
--to=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=b.a.t.m.a.n@open-mesh.net \
/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