public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Gioacchino Mazzurco <gmazzurco89@gmail.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.] mesh: received packet with own address as source address
Date: Mon, 20 Feb 2012 11:41:17 +0100	[thread overview]
Message-ID: <4F42234D.4010703@gmail.com> (raw)
In-Reply-To: <CAFevQmM12dq09+FPtwedGAXnJxw8rsCwphLAa-qfmaQFifErNg@mail.gmail.com>

Maybe related to the problem we had in Mistretta!

We upgraded just ONE node and it seems that bridge loop avoidance didn't
worked anymore

that node was attached to another node via lan and both nodes had bat0
and eth0 bridged, the 2 nodes started flooding the network with
rebroadcasted broadcast packet and every link was overloaded

the solution was to turn off the new node ( i have to go and disable the
bridging manually )

But I think that in my case the problem was triggered by the fact that
the two nodes has different batman-adv version one 2012.0.0 and the
other 2011.4.0 ( and i supposed that the two version have incompatible
loop avoidance )

Both node use batman-adv from openwrt repository

On 02/20/12 00:45, Filippo Sallemi wrote:
> Hi all,
> after upgrade of batman package on my nodes I see a very decerase of
> performance of my mesh network. When I connect to some node i see
> every time this message:
> 
> mesh: received packet with  own address as source address
> 
> now in a gateway mode my network config is:
> config 'interface' 'lan'
> 	option 'macaddr' '02:15:6d:7c:f0:88'
> 	option 'type' 'bridge'
> 	option 'ifname' 'mesh'
> 	option 'proto' 'static'
> 	option 'ipaddr' '10.240.136.1'
> 	option 'netmask' '255.0.0.0'
> 
> config 'interface' 'wan'
> 	option 'ifname' 'eth0'
> 	option 'proto' 'dhcp'
> 
> config 'interface' 'msh0'
> 	option 'proto' 'none'
> 	option 'mtu' '1528'
> 
> in client mode nodes the network config is:
> 
> config 'interface' 'loopback'
> 	option 'ifname' 'lo'
> 	option 'proto' 'static'
> 	option 'ipaddr' '127.0.0.1'
> 	option 'netmask' '255.0.0.0'
> 
> config 'interface' 'lan'
> 	option 'macaddr' '02:15:6d:b0:19:48'
> 	option 'type' 'bridge'
> 	option 'ifname' 'eth0 mesh'
> 	option 'proto' 'dhcp'
> 
> config 'interface' 'msh0'
> 	option 'proto' 'none'
> 	option 'mtu' '1528'
> 
> 
> Someone can help me? I've 20 nodes crazy
> 

  parent reply	other threads:[~2012-02-20 10:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-19 23:45 [B.A.T.M.A.N.] mesh: received packet with own address as source address Filippo Sallemi
2012-02-19 23:55 ` Sven Eckelmann
     [not found]   ` <CAFevQmP3bduvABV2EvDYXdWbbVsRjak=uqVfAfK3UVswWM5gSg@mail.gmail.com>
2012-02-20 10:36     ` [B.A.T.M.A.N.] Fwd: " Filippo Sallemi
2012-02-20 10:41 ` Gioacchino Mazzurco [this message]
2012-02-24 13:14   ` [B.A.T.M.A.N.] " 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=4F42234D.4010703@gmail.com \
    --to=gmazzurco89@gmail.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