From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marek Lindner Date: Thu, 3 Jan 2013 22:46:29 +0800 References: <5ACA4F0A-BD9A-4CE5-AAF6-1F259DAA2B55@stephan.homeunix.net> In-Reply-To: <5ACA4F0A-BD9A-4CE5-AAF6-1F259DAA2B55@stephan.homeunix.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <201301032246.29635.lindner_marek@yahoo.de> Subject: Re: [B.A.T.M.A.N.] Packet-Loss-Peaks in a Freifunk-Network Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: The list for a Better Approach To Mobile Ad-hoc Networking On Thursday, January 03, 2013 22:16:32 Jan L=FChr wrote: > We noticed a few, unusual things: > -> regardless of the link tested (kif or fastd3) and regardless of the no= de > (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 you= r=20 test setup and repeat the exact same test. Otherwise we move into the realm= of=20 speculation. Haven't heard of any "peak loss" due to batman-adv. Cheers, Marek