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.] batman-adv 2011.2.0 hop somtimes does not work
Date: Tue, 6 Sep 2011 20:33:17 +0200 [thread overview]
Message-ID: <201109062033.17427.lindner_marek@yahoo.de> (raw)
In-Reply-To: <4E65E286.7080600@robotech.de>
Hi,
> i needed to get this working so i switched to 2011.2 last weekend and
> the problems are gone.
ok.
> I have some similar devices as spare parts. I'll try to set them up and
> reproduce the problems - but that can take a while.
Understood. We hopefully come up with a patch soon that will need to be
tested.
> - every node has only one wlan-network on which batman runs and only the
> node itself uses the bat0 interface - no bridging, no routing
> - at the end, most of the time only the directly connected nodes were
> reachable via a normal ping - the "hopping" was not working
> - i had the *feeling* that the problems got bigger the more nodes we added
> - also i *think* the problems began when we mixed Fonera- and
> TP-Link-devices (sightly different architecture i think)
Can you tell us what TP-Link model you are using (name, hardware revision,
etc). Or post the output of /proc/cpuinfo ?
> - the log was always spammed with messages - because of the tiny devices
> i use it's not easy to save the log and inspect it when the connection
> is working again - which can take an hour...
It is somewhat troublesome that the problem went away after a while. If we
have a bug in the architecture handling you would expect it to be a permanent
problem. But who knows ...
Regards,
Marek
next prev parent reply other threads:[~2011-09-06 18:33 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 22:53 [B.A.T.M.A.N.] batman-adv 2011.2.0 hop somtimes does not work Tobias
2011-08-30 23:07 ` clownix
2011-08-31 9:55 ` Marek Lindner
2011-08-31 15:57 ` wayne abroue
2011-08-31 16:07 ` Antonio Quartulli
2011-08-31 16:16 ` Marek Lindner
2011-08-31 16:18 ` Antonio Quartulli
2011-08-31 17:05 ` Tobias
2011-08-31 21:55 ` Antonio Quartulli
2011-08-31 22:14 ` Javier Cardona
2011-09-01 8:15 ` Tobias
2011-09-01 15:55 ` Antonio Quartulli
2011-09-01 21:11 ` Tobias
2011-09-01 21:35 ` Antonio Quartulli
2011-09-01 22:45 ` Tobias
2011-09-05 8:06 ` Marek Lindner
2011-09-06 9:06 ` Tobias
2011-09-06 18:33 ` Marek Lindner [this message]
2011-09-07 8:00 ` Tobias
2011-09-13 11:18 ` Marek Lindner
2011-09-13 12:09 ` Andrew Lunn
2011-09-14 20:54 ` Tobias
2011-09-19 22:45 ` Antonio Quartulli
[not found] ` <4E7ED5D3.2000600@wifibot.com>
[not found] ` <20110925073942.GA2993@ritirata.org>
[not found] ` <4E7EE7A9.7010309@wifibot.com>
2011-09-25 16:05 ` Antonio Quartulli
2011-09-25 16:06 ` [B.A.T.M.A.N.] [PATCH] batman-adv: Chichek hunt started! Verbose patch Antonio Quartulli
2011-08-31 16:44 ` [B.A.T.M.A.N.] batman-adv 2011.2.0 hop somtimes does not work Tobias
2011-08-31 16:54 ` wayne abroue
2011-08-31 16:36 ` Tobias
2011-10-19 13:36 ` Antonio Quartulli
2011-09-26 21:07 laurent
2011-09-26 21:14 ` laurent
2011-09-26 22:48 ` Antonio Quartulli
2011-10-10 12:08 ` Antonio Quartulli
2011-09-27 6:01 ` Andrew Lunn
2011-09-27 6:39 ` laurent
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=201109062033.17427.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;
as well as URLs for NNTP newsgroup(s).