From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id A72F0201B88 for ; Thu, 30 Jan 2014 10:46:31 -0800 (PST) Received: from hms-beagle.home.lan ([217.86.112.208]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0MLfH9-1W8fW31FeV-000qbS for ; Thu, 30 Jan 2014 19:46:28 +0100 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Sebastian Moeller In-Reply-To: Date: Thu, 30 Jan 2014 19:46:28 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <975EDBAB-4792-4AEE-B79F-32ABB717EC5E@gmx.de> References: <1CB745C6-5334-4CF8-8535-BB97E9B37A1D@gmx.de> To: Dave Taht X-Mailer: Apple Mail (2.1510) X-Provags-ID: V03:K0:YxW+dN0s7PvHvhFaqi2S080gqJfSGw/6W8RUlgKyYGHf8mL2l8S UO5a/yg2L0BNMNG7K+kwSDDweVftXTviVdNohhPoSSv6QcVhtPPX1uCKpzgeiFcI1fsjDrT UpjvgtKSb05YvNmHGJqiG2Pc3eP8/Qx2othwieSVweukoEsUHD5yJmVI40b0ZcYmEPu3Bto TQ0gPnb0KNIoyl9idgCSQ== 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 18:46:32 -0000 Hi Dave, hi list, On Jan 30, 2014, at 17:21 , Dave Taht wrote: > On Wed, Jan 29, 2014 at 11:55 AM, Sebastian Moeller = wrote: >> Hi Steve, >>=20 >>=20 >> On Jan 29, 2014, at 19:24 , Steve Jenson = wrote: >>=20 >>> On Wed, Jan 29, 2014 at 9:44 AM, Sebastian Moeller = wrote: >>> On January 29, 2014 5:10:18 PM CET, Dave Taht = wrote: >>>> On Wed, Jan 29, 2014 at 4:45 AM, Sebastian Moeller = >>>> wrote: >>>>> Hi Dave, >>>>>=20 >>>>> 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? >>>>=20 >>>> seems so. >>>=20 >>> Okay, I guess I will try that then... >>>=20 >>> Here's the directive I'm using in /etc/babeld.conf >>>=20 >>> log-file /dev/null >>>=20 >>> and then you can restart either via the web gui or = `/etc/rc.d/S70babeld restart` >>=20 >> Ah, thanks. Since I am on 3.10.28-1 this was = /etc/init.d/babeld restart. 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... >=20 >=20 > I stuck it in /etc/config/babeld. >=20 >> Babeld runs again, and no /var/log/babeld.log appeared, but = whether it works I do not know (and I doubt it given that babeld.log was = growing due to nasty repeating error messages...) >=20 > It's working. It is just not making an optimal routing decision > between AP-managed networks and meshy ones. Ah, if babel can work around this issue than there is no good = reason to spam the log with repeats (at least not at the frequency it = currently does, once per day might be more reasonable...) >=20 > 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... >=20 > http://www.pps.univ-paris-diderot.fr/~jch/software/babel/wbmv4.pdf Interesting, thanks for the pointer. >=20 > Notably this feature is also in batman, but it's called something else > that I forget. >=20 > In an example with two radios on a cerowrt AP: >=20 > 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. >=20 > So right now babel is incorrectly distinquishing between the AP > managed SSIDs (sw00, sw10, gw10, gw00), > so the routing decisions there are sub-optimal. Is it really hard to get the radio and frequency for each = interface from linux? > 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. Okay, that does not justify the log spam ;) >=20 > 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%" I agree (and then I would be happier if openwrt would have a = preemptive mechanism to avoid this situation, be it log rotation and = deletion or similar methods.) Best Regards & mangy thanks for the explanation. Sebastian >=20 >=20 >=20 >>=20 >> Best Regards >> Sebastian >>=20 >>>=20 >>=20 >=20 >=20 >=20 > --=20 > Dave T=E4ht >=20 > Fixing bufferbloat with cerowrt: = http://www.teklibre.com/cerowrt/subscribe.html