From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 6CB1F202102 for ; Thu, 30 Jan 2014 08:21:02 -0800 (PST) Received: by mail-qc0-f170.google.com with SMTP id e9so5354998qcy.1 for ; Thu, 30 Jan 2014 08:21:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=ZTVwsai4PCEhLn0HaKzdYeqj1JhpvZh9mJ0fL5vDJrQ=; b=GG5IAVR9lNODPFj5JZhl++c5tl3zjTSrIIMV8yXXbCBG6z9nhqFYjIQhSOEmgzTT1E fv6n2SzYpNCOs4dkM2+9Js9qfulVI4eubvAGlMhlL2XyBysj2SW/KpM62O06ZbVa3By0 6zCqgHjMH1ej7wziGqsVj63yhXMw03OywAtE1LaE24OkqL08hKLK+zBNY64/IYyP6sKY 5wuOMs62bRmmvYC/UvruxW9Y+cACDAFlIyX06KsCCu5DPbRalrUzjSx4JvSwJ4xXKiv3 7WkSCcPuiUnFF3VNhnN2OZEm0Y+iwC8T9hQ+qL4BnOSG6K4xtUk4bjdlOrKrCNlAUozh Uhew== MIME-Version: 1.0 X-Received: by 10.224.28.197 with SMTP id n5mr20265970qac.43.1391098861274; Thu, 30 Jan 2014 08:21:01 -0800 (PST) Received: by 10.224.42.70 with HTTP; Thu, 30 Jan 2014 08:21:01 -0800 (PST) In-Reply-To: <1CB745C6-5334-4CF8-8535-BB97E9B37A1D@gmx.de> References: <1CB745C6-5334-4CF8-8535-BB97E9B37A1D@gmx.de> Date: Thu, 30 Jan 2014 08:21:01 -0800 Message-ID: From: Dave Taht To: Sebastian Moeller Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] cerowrt issues (3.10.24-8) X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 16:21:02 -0000 On Wed, Jan 29, 2014 at 11:55 AM, Sebastian Moeller wrote= : > Hi Steve, > > > On Jan 29, 2014, at 19:24 , Steve Jenson wrote: > >> On Wed, Jan 29, 2014 at 9:44 AM, Sebastian Moeller wro= te: >> On January 29, 2014 5:10:18 PM CET, Dave Taht wrot= e: >> >On Wed, Jan 29, 2014 at 4:45 AM, Sebastian Moeller >> >wrote: >> >> Hi Dave, >> >> >> >> quick question, how does one turn of logging for babeld? It seems >> >that if daemonized it defaults to logging to /var/log/babeld.log (or >> >similar). Is setting the log file to /dev/null really the answer? >> > >> >seems so. >> >> Okay, I guess I will try that then... >> >> Here's the directive I'm using in /etc/babeld.conf >> >> log-file /dev/null >> >> and then you can restart either via the web gui or `/etc/rc.d/S70babeld = restart` > > Ah, thanks. Since I am on 3.10.28-1 this was /etc/init.d/babeld r= estart. And I opted for putting: > option 'log-file' '/dev/null' > into /etc/config/babeld, since that seemed the more openwork way of doing= things; I wonder whether it really is wise to carry both files... I stuck it in /etc/config/babeld. > Babeld runs again, and no /var/log/babeld.log appeared, but wheth= er it works I do not know (and I doubt it given that babeld.log was growing= due to nasty repeating error messages...) It's working. It is just not making an optimal routing decision between AP-managed networks and meshy ones. The feature is called diversity routing, and it is key to making wireless networks scale better. There are (now), quite a few papers on it, but I like Juliusz's best... http://www.pps.univ-paris-diderot.fr/~jch/software/babel/wbmv4.pdf Notably this feature is also in batman, but it's called something else that I forget. In an example with two radios on a cerowrt AP: If you have a packet come in from channel 36, it's best that it goes out via ethernet if possible, channel 11 if not, and not channel 36. Even if the number of hops seems less, don't go back out 36, if at all possible, use a different route. So right now babel is incorrectly distinquishing between the AP managed SSIDs (sw00, sw10, gw10, gw00), so the routing decisions there are sub-optimal. As in most cases you are going to go out ethernet or one of the more meshy interfaces, or you have no choice but to send stuff along on one SSID... it's not very sub-optimal. still, annoying. rule 22 in embedded design is "never write infinitely long files as the probability of running out of memory or flash always hits 100%" > > Best Regards > Sebastian > >> > --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.= html