From: Antonio Quartulli <ordex@autistici.org>
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.] Very strange behaviour
Date: Sat, 19 Nov 2011 20:31:08 +0100 [thread overview]
Message-ID: <20111119193108.GI30187@ritirata.org> (raw)
In-Reply-To: <CAFevQmM1zCU9k7LJYjMDosjNCEJhrnZ-4krWnX2MiYC9+-SBTA@mail.gmail.com>
Hello Filippo,
On Sat, Nov 19, 2011 at 08:22:41 +0100, Filippo Sallemi wrote:
> Hi,
> I'm just working on script that try to autorecover the node in case of
> failure and I noticed something very strange.
> Ii have 3 node setted to channel 3. Well when I change the channel of
> one of these nodes for example from 3 to 5 after some time I can see
> however the entirely topology of my network.
>
> How it is possible? My script is not ready and iwconfig output show
> the changed channel!!!!
>
> apparently do not have the same behavior if channel is far from other
> nodes (es 6)
>
> This is very very strange for me!
>
I know you are testing batman-adv on your network, but this particular issue is
not strictly related to batman anymore..
However I'd say that, since channels overlap (yes they do), it is possible that some
devices overhear packets (not all of course) from near channels too. If you want
to be sure that overlapping is not happening, you should choose channel 1, 7 and
13.
By the way this is just my explanation. Could be not correct.
Cheers,
--
Antonio Quartulli
..each of us alone is worth nothing..
Ernesto "Che" Guevara
next prev parent reply other threads:[~2011-11-19 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 19:22 [B.A.T.M.A.N.] Very strange behaviour Filippo Sallemi
2011-11-19 19:31 ` Antonio Quartulli [this message]
2011-11-19 19:42 ` Daniele Furlan
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=20111119193108.GI30187@ritirata.org \
--to=ordex@autistici.org \
--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 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.