public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
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.] batman majareta? I can batctl ping but not ping
Date: Sat, 21 Jul 2012 23:40:26 +0200	[thread overview]
Message-ID: <20120721214026.GC3610@ritirata.org> (raw)
In-Reply-To: <500AFACD.7070207@eigenlab.org>

[-- Attachment #1: Type: text/plain, Size: 3664 bytes --]

Hello Gioacchino,

On Sat, Jul 21, 2012 at 08:54:05PM +0200, Gioacchino Mazzurco wrote:
> Same bug today in ninux pisa after a node was turned off the entire
> network became crazy for 2 hours, to solve i had to restart a lot of
> nodes... :|
> 

Which version are you using? The lastest openwrt package version (so with all
the new patches?)

Could you provide the log of the involved nodes whenever you get this problems?
I wrote something about the desired logs to Guido, you could follow the same
instruction. It would really be appreciated!

Thank you!


Cheers,

> On 07/02/12 15:30, Guido Iribarren wrote:
> > (which roughly translates as "batman gone nuts?")
> > Hey great devs!
> > we've been having a particular issue in deltalibre and quintanalibre
> > (local WCN) with batman-adv, but so far we haven't found a precise way
> > to reproduce it.
> > The symptom is that (after some reboots or physical displacements?)
> > one batman-adv host becomes unreachable on layer3, although it is seen
> > on originators table, and can be batctl ping'ed or batctl tracerout'ed
> > with no problem whatsoever.
> > 
> > Even more, it not unreachable from the whole network, but instead from
> > just a few other nodes. So, let's say that the nearer nodes can layer3
> > ping it , but some others farther away cannot (although i can't assure
> > it depends on the hop distance)
> > All of them can batctl ping it (layer2)
> > A hard reboot of all the nodes solves it, connectivity is restored in
> > all directions.
> > 
> > Thing is, I've just came across it again, and managed to do some tests
> > to aid in description / debugging
> > As an aid in understanding network topology,
> > I'm attaching the wonderful output of "batctl vd dot |grep -v TT" for
> > your viewing delight
> > 
> > problem node is ana
> > it can be reached from ruth and hquilla (direct neighbours)
> > but arping behaves erratically from colmena or charly
> > and normal ping (v4 or v6) doesn't receive any reply at all when run
> > from colmena or charly
> > 
> > I used arping, with and without -b , and seemed like i could narrow
> > the problem down to incoming broadcast packet handling, but further
> > tests just left me more puzzled!
> > 
> > all nodes are tl-mr3220 running openwrt trunk r31316 with batman-adv
> > 2012.2.0 , driver ath9k
> > secondary interfaces named _wlan1 are all tl-wn722n which uses driver ath9k_htc
> > nodes are around 100meters (+/-50mts) apart from each other
> > 
> > this behaviour has been observed (but not reported) in dissimilar
> > setups, using ubnt bullet2 mixed with mr3220, running r29936 with
> > batman-adv 2011.4.0 , with nodes 1 or 2km apart from each other.
> > 
> > Tests are the combined crude output of batctl td and arping, so to
> > make this email ease on the eye, i'm publishing them elsewhere:
> > http://pastebin.com/6PPwN3PS
> > 
> > The live openwrt configuration can be analysed in detail at
> > https://bitbucket.org/guidoi/deltalibre-configs/src
> > (it's a free, open network after all! :D )
> > in particular:
> > ana -> https://bitbucket.org/guidoi/deltalibre-configs/src/6de4ce970fe2/mac/54_E6_FC_BE_26_12
> > hquilla -> https://bitbucket.org/guidoi/deltalibre-configs/src/6de4ce970fe2/mac/54_E6_FC_BE_28_34
> > colmena -> https://bitbucket.org/guidoi/deltalibre-configs/src/6de4ce970fe2/mac/54_E6_FC_BE_29_D2
> > 
> > Thanks a lot for the attention,
> > Hope that you are having fun, and that I'm not spoiling it :)
> > 
> > Cheers!
> > 
> > Gui

-- 
Antonio Quartulli

..each of us alone is worth nothing..
Ernesto "Che" Guevara

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-07-21 21:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-02 13:30 [B.A.T.M.A.N.] batman majareta? I can batctl ping but not ping Guido Iribarren
2012-07-02 13:57 ` Guido Iribarren
2012-07-02 14:36   ` Antonio Quartulli
2012-07-02 14:47     ` Guido Iribarren
2012-07-02 15:52     ` Marek Lindner
2012-07-02 16:11       ` Guido Iribarren
2012-07-02 16:26         ` Marek Lindner
2012-07-20 20:25     ` Guido Iribarren
2012-07-21 21:38       ` Antonio Quartulli
2012-07-22 10:57         ` Guido Iribarren
2012-07-22 11:20           ` Guido Iribarren
2012-07-23 17:28             ` Antonio Quartulli
2012-08-05  5:34               ` Gui Iribarren
2012-08-05  7:58                 ` Antonio Quartulli
2012-07-02 16:39 ` Gioacchino Mazzurco
2012-07-02 16:42   ` Antonio Quartulli
2012-07-03  7:34     ` Nicolás Echániz
2012-07-03  7:52       ` Wayne Abroue
2012-07-03  8:07         ` Marek Lindner
2012-07-03  8:27           ` Wayne Abroue
2012-07-03  8:37             ` Marek Lindner
2012-07-21 18:54 ` Gioacchino Mazzurco
2012-07-21 21:40   ` Antonio Quartulli [this message]
2012-07-22 10:54     ` Gioacchino Mazzurco

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=20120721214026.GC3610@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox