From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com [IPv6:2607:f8b0:400d:c01::22f]) (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 39FBB21F1BE for ; Fri, 7 Feb 2014 09:57:58 -0800 (PST) Received: by mail-qc0-f175.google.com with SMTP id x13so6448755qcv.6 for ; Fri, 07 Feb 2014 09:57:57 -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=Whm3TU25PN7qWuVPL3wPiHMZnzs6vr3SboJ1I5dSPpk=; b=eJFAch0ST8tBGrrCYWnAWrkjFDI8TC+v88zlVjq6CoI/8u83z9GQ6Mn22iy/BRrpda C5kub+PoMlcK1kz6797aT1C4EUbCMb/VJtTeQYkodzmmes2aXrKGK0Ae+UnaoBdwrqAS 4o2o4zfbrhniQQt30USXdJDaDvyqKjdCSg2GLlq48vc9w4I1KFrB31l/5y9AxBqEucWl aB29GGsN8QKt4WX0H4nuHVUM9Rdcs2O+fK//U7ch2d6zUYLD7KpTqw9LrRtbOwSIgM8q 6AGTHjxGLr6kbba3qd7b8OQ8z9jH4IypuEYZZbkLhruLOlUH0ZXLnrkk7TF4s4IHnocu nzqA== MIME-Version: 1.0 X-Received: by 10.224.115.78 with SMTP id h14mr24758418qaq.94.1391795873923; Fri, 07 Feb 2014 09:57:53 -0800 (PST) Received: by 10.224.27.133 with HTTP; Fri, 7 Feb 2014 09:57:53 -0800 (PST) In-Reply-To: <20140207100146.5ba027c3@samsung-9> References: <20140207100146.5ba027c3@samsung-9> Date: Fri, 7 Feb 2014 12:57:53 -0500 Message-ID: From: Dave Taht To: Stephen Hemminger Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] Will there ever be a stable version of cerowrt? 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: Fri, 07 Feb 2014 17:57:58 -0000 On Fri, Feb 7, 2014 at 12:01 PM, Stephen Hemminger wrote: > Any progress on getting a stable version? Recent versions seem to be targ= eted > at IPv6 and other things which do not impact me for home use. What does m= atter > is fixing the wireless hanging issue on 2.4Ghz. Do I detect a plainative note? I share it... I'm not aware of any problems on 2.4ghz in the last specific release I did for comcast. It's been in day-to-day use here since I put it out. http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/comcast/3.10.28-4/ Feel free to give it a shot. The stuff that made it comcast specific (co-existence with HE tunnels) is solved, so the next gen will be generic. I AM painfully aware that ht40+ at 5ghz appears to have broken on several channels (Seems to work on 36 and fail on 44) There was a fresh merge from wireless-testing recently, that I hope fixes it. I DO plan a stable release this month if possible, and at the very least a code freeze fairly soon. in cerowrt head are fixes for ipv6 tunnel co-existence, mostly everything now using procd, fixed upnp support (think that landed in the release above), cleanups of the SQM code for eventual submittal to mainline landed also. *Please note* that a source of hangs in the last several cero releases was an oopsy in turning off logging for ahcp and babeld, which filled up available memory rapidly. EVERYBODY: Do turn send those logs to /dev/null if you haven't already in the relevant /etc/config/ files and look for other sources of memory growth from logs. the remaining problems are: got competing work requirements terribly pressing, final pie release needs to be added, (kind of wanted sch_fq and the other new qdisc from 3.13, too) a bunch of ietf drafts are in the nascent stage and stuck there, a build server crashed and a whole string of openwrt builds failed to build, still need /etc/init.d/babeld support for source specific routing and babel to run out of procd, package signing is broken, and worst of the cerowrt build broke last week due to some changes in the openwrt build process I still don't understand. There is still one unaligned_instruction trap left to beat that appears to be triggered by odhcpd. root@comcast-gw:~# cat /sys/kernel/debug/mips/unaligned_instructions 18000 One of the things that scares me is that a bunch of openwrt targets are migrating to 3.13 and if I miss a window the very stable 3.10.28 release is going to get replaced upstream with 3.13 and resultant headaches. (and benefits) As my own deadlines slip everywhere, I made a big push earlier this week to appeal to many folk to get dnsmasq + dnssec more widely tested on other platforms in the hope that whenever I got unburied it would be stable enough to toss into cero. (that's going along swimmingly on x86 and arm so far) I hope to replace the failed server this tonight and burn sunday on trying to resolve the problems above. The currently borked srcs are on github. --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.= html