All of lore.kernel.org
 help / color / mirror / Atom feed
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>
Cc: "Bonn und Umgebung Allgemeine Mailingliste zum Freifunk Köln"
	<freifunk-bonn@lists.bonn.freifunk.net>
Subject: Re: [B.A.T.M.A.N.] Packet-Loss-Peaks in a Freifunk-Network
Date: Thu, 3 Jan 2013 23:00:04 +0800	[thread overview]
Message-ID: <201301032300.04942.lindner_marek@yahoo.de> (raw)

On Thursday, January 03, 2013 22:16:32 Jan Lühr wrote:
> We noticed a few, unusual things:
> -> regardless of the link tested (kif or fastd3) and regardless of the node
> (node1, node2) small interruptions (loss-peaks) are appearing. -> These
> peaks appear almost synchronous, a few "noise" comes from different
> vpn-links and node-wan-uplinks. -> Since all links are wired, radio-noise
> won't have an impact
> -> The losses appear in batman-adv 2011.2.0 as well as in batman-adv
> 2012.4.0. Thus I suspect that batman-adv is triggering theses
> interruptions.

If you believe batman-adv is the culprit, please remove batman-adv from your 
test setup and repeat the exact same test. Otherwise we move into the realm of 
speculation.

Haven't heard of any "peak loss" due to batman-adv.

Cheers,
Marek


PS: Forgot to click "reply to all", sorry for that.

             reply	other threads:[~2013-01-03 15:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 15:00 Marek Lindner [this message]
2013-01-03 15:52 ` [B.A.T.M.A.N.] Packet-Loss-Peaks in a Freifunk-Network Jan Lühr
2013-01-03 16:05   ` Marek Lindner
2013-01-03 16:17     ` Jan Lühr
2013-01-04  5:34       ` "Linus Lüssing"
2013-01-04 10:18         ` Jan Lühr
  -- strict thread matches above, loose matches on Subject: below --
2013-01-03 14:16 Jan Lühr
2013-01-03 14:46 ` 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=201301032300.04942.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=freifunk-bonn@lists.bonn.freifunk.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.