public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Antonio Quartulli <antonio@meshcoding.com>
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.] mad mad batman ...
Date: Tue, 12 Nov 2013 22:54:42 +0100	[thread overview]
Message-ID: <20131112215442.GN3713@neomailbox.net> (raw)
In-Reply-To: <5282A184.1020704@altermundi.net>

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

Hi Nico,

I have no real clue, but is it possible that there is a loop somewhere? I
imagine you have checked already..but I can't come with something more useful at
the moment..

Cheers,

On Tue, Nov 12, 2013 at 06:45:40PM -0300, Nicolás Echániz wrote:
> 
> back in Quintana... this problem is still showing in every node. The network is unstable and so it's difficult to debug. If anyone has a clue as to where to look for the origin I'll be glad to read your thoughts.
> 
> cheers,
> Nico
> 
> 
> El 13/10/13 18:34, Nicolás Echániz escribió:
> > While I'm still in Europe I've observed that the network in Quintana has
> > started performing very poorly today. It was working perfectly fine
> > until yesterday.
> > 
> > The logs on every router have started showing entries like these:
> > 
> > Oct 13 18:09:43 frigorifico kern.warn kernel: [12018.150000] br-lan:
> > received packet on bat0 with own address as source address
> > Oct 13 18:09:45 frigorifico kern.warn kernel: [12020.040000] br-lan:
> > received packet on bat0 with own address as source address
> > Oct 13 18:09:45 frigorifico kern.warn kernel: [12020.040000] br-lan:
> > received packet on bat0 with own address as source address
> > Oct 13 18:09:45 frigorifico kern.warn kernel: [12020.550000] br-lan:
> > received packet on bat0 with own address as source address
> > Oct 13 18:09:45 frigorifico kern.warn kernel: [12020.550000] br-lan:
> > received packet on bat0 with own address as source address
> > Oct 13 18:09:45 frigorifico kern.warn kernel: [12020.570000] br-lan:
> > received packet on bat0 with own address as source address
> > Oct 13 18:09:45 frigorifico kern.warn kernel: [12020.580000] br-lan:
> > received packet on bat0 with own address as source address
> > Oct 13 18:09:46 frigorifico kern.warn kernel: [12021.040000] br-lan:
> > received packet on bat0 with own address as source address
> > 
> > As you can see there are many per second.
> > 
> > 
> > I've pasted a bit of batctl ll batman; batctl log here:
> > 
> > http://pastebin.com/HX1LBPK4
> > 
> > 
> > ...it's only showing the "originator packet from myself" lines and one
> > line before. (the sample is less than 5 secs of logs)
> > 
> > Every node I checked is showing the same.
> > 
> > 
> > Last time this happened it was due to a router that had been affected by
> > a nearby lightning bolt. The switch went crazy.
> > It took a while to detect it and the network was 15 nodes big. Now it's
> > 40 and we are quite far away :)
> > 
> > 
> > If anyone has an idea of how to better test where the problem is
> > originated, I'll be glad to hear it. Also if any batman devel wishes to
> > log in to the net to check first hand, just let me know.
> > 
> > 
> > Cheers!
> > Nico
> > 
> > 
> > PS: batman version is 2012.4
> > 
> 

-- 
Antonio Quartulli

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

  reply	other threads:[~2013-11-12 21:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-13 21:34 [B.A.T.M.A.N.] mad mad batman Nicolás Echániz
2013-11-12 21:45 ` Nicolás Echániz
2013-11-12 21:54   ` Antonio Quartulli [this message]
2013-11-13  0:56     ` Nicolás Echániz
2013-11-13  8:04       ` Bastian Bittorf
2013-11-13  8:01         ` Antonio Quartulli
2013-11-26  3:56           ` Nicolás Echániz
2013-11-26  4:48             ` Linus Lüssing

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=20131112215442.GN3713@neomailbox.net \
    --to=antonio@meshcoding.com \
    --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