From: Gioacchino Mazzurco <gmazzurco89@gmail.com>
To: Antonio Quartulli <ordex@autistici.org>
Cc: b.a.t.m.a.n@lists.open-mesh.org, babel-users@lists.alioth.debian.org
Subject: Re: [B.A.T.M.A.N.] multicast packet loss
Date: Mon, 06 Aug 2012 17:48:01 +0200 [thread overview]
Message-ID: <501FE731.6050306@gmail.com> (raw)
In-Reply-To: <20120806134309.GK12879@ritirata.org>
The problem was that babeld assumed bat0 as a wired interface so when 2
or 3 packet was lost it marked the route as unreachable, now the problem
is fixed thanks to a patch from julius
by the way it is not normal that batman loss packet on wired links and I
think we should do some debug to understand what is happening...
I am going to do some test as ordex said trying to make things clear
On 08/06/2012 03:43 PM, Antonio Quartulli wrote:
> On Mon, Aug 06, 2012 at 03:05:49PM +0200, Gioacchino Mazzurco wrote:
>> Hi all!
>>
>> I am experiencing a multicast packet loss on batman-adv mesh, this can
>> appear normal but it is not because the mesh is on top of wired Ethernet
>> link!
>>
>> the host fe80::c8e0:2cff:fe9b:6d1f is sending a multicast hello message
>> every 4 seconds on bat0 interface, but as you can see from the dump
>> timing on a machine attached on the same switch they are not arriving
>> regurarly so what is happening? Is this normal?
>
> Hello Gioacchino,
>
> I'd say that losing packets is not normal :-)
> Have you tried to use batctl td on the wired interface? You should see the
> "broadcast" packets going around. It would be interesting to understand if on
> batctl you had more packets than what you are receiving on the node.
>
> Cheers,
>
>
> p.s. what kind of hello messages are they? Their size is changing over time..
>
prev parent reply other threads:[~2012-08-06 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 13:05 [B.A.T.M.A.N.] multicast packet loss Gioacchino Mazzurco
2012-08-06 13:43 ` Antonio Quartulli
2012-08-06 15:48 ` Gioacchino Mazzurco [this message]
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=501FE731.6050306@gmail.com \
--to=gmazzurco89@gmail.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=babel-users@lists.alioth.debian.org \
--cc=ordex@autistici.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