From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe001.messaging.microsoft.com [213.199.154.204]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.global.frontbridge.com", Issuer "Microsoft Secure Server Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 67ABE21F130 for ; Tue, 28 Aug 2012 18:28:37 -0700 (PDT) Received: from mail16-am1-R.bigfish.com (10.3.201.244) by AM1EHSOBE010.bigfish.com (10.3.204.30) with Microsoft SMTP Server id 14.1.225.23; Wed, 29 Aug 2012 01:28:33 +0000 Received: from mail16-am1 (localhost [127.0.0.1]) by mail16-am1-R.bigfish.com (Postfix) with ESMTP id C704744032C for ; Wed, 29 Aug 2012 01:28:33 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.244.213; KIP:(null); UIP:(null); IPV:NLI; H:CH1PRD0510HT004.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: 0 X-BigFish: VPS0(z21eIz98dIc89bhc85dh111aIzz1202hzz8275bhz31h2a8h668h839hd25he5bhf0ah107ahbe3k1155h) Received-SPF: softfail (mail16-am1: transitioning domain of dartware.com does not designate 157.56.244.213 as permitted sender) client-ip=157.56.244.213; envelope-from=richard.e.brown@dartware.com; helo=CH1PRD0510HT004.namprd05.prod.outlook.com ; .outlook.com ; Received: from mail16-am1 (localhost.localdomain [127.0.0.1]) by mail16-am1 (MessageSwitch) id 1346203712388850_13467; Wed, 29 Aug 2012 01:28:32 +0000 (UTC) Received: from AM1EHSMHS002.bigfish.com (unknown [10.3.201.229]) by mail16-am1.bigfish.com (Postfix) with ESMTP id 53B9E3600A5 for ; Wed, 29 Aug 2012 01:28:32 +0000 (UTC) Received: from CH1PRD0510HT004.namprd05.prod.outlook.com (157.56.244.213) by AM1EHSMHS002.bigfish.com (10.3.207.102) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 29 Aug 2012 01:28:26 +0000 Received: from CH1PRD0510MB381.namprd05.prod.outlook.com ([169.254.11.146]) by CH1PRD0510HT004.namprd05.prod.outlook.com ([10.255.150.39]) with mapi id 14.16.0190.008; Wed, 29 Aug 2012 01:28:26 +0000 From: Richard Brown To: "" Thread-Topic: development snapshot of cerowrt-3.3.8-21 released Thread-Index: AQHNhYWVBNyq3u582EezpS5s3KuV3w== Date: Wed, 29 Aug 2012 01:28:25 +0000 Message-ID: <78BC1794-317B-43E5-9E49-44D34AA0BF17@intermapper.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.255.150.4] Content-Type: multipart/alternative; boundary="_000_78BC1794317B43E59E4944D34AA0BF17intermappercom_" MIME-Version: 1.0 X-OriginatorOrg: dartware.com Subject: Re: [Cerowrt-devel] development snapshot of cerowrt-3.3.8-21 released 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: Wed, 29 Aug 2012 01:28:37 -0000 --_000_78BC1794317B43E59E4944D34AA0BF17intermappercom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dave, Dave T=E4ht wrote: I spent the last two weeks hunting down memory related issues and trying to fold in some development work I'd had going already. As best as I can tell, the core memory issues are killed dead; whether this is due to freeing up tons of memory or by the various other stuff remains to be determined. Great work and excellent news! But: Under *no circumstances* install this release on your default router. Yeah. A few short comments on 3.3.8-21: 1) I cannot connect to gw.home.lan via DNS. Dig gives no answers. I can lo= g in just fine on 172.30.42.1, etc. and config the router, etc. 2) More on the Hurricane Electric tunnel. After adding these lines to the c= onfig script on the wiki page: uci set network.henet.adv_subnet=3D1 # added for 3.3.8-17 uci set network.henet.adv_interface=3Dse00 uci set network.henet.adv_interface=3Dsw10 I still cannot connect/get an IPv6 address on se00, *but* I can get address= es on all four wireless channels. (In retrospect, I believe this was true f= or 3.3.8-17 as well.) 3) Is it possible that DNS come back earlier in the boot sequence? It seeme= d that CeroWrt began responding within a minute (or so) to DNS queries, ins= tead of the 2-5 minutes that I've seen with earlier builds. Thanks again. Rich Brown Hanover, NH USA --_000_78BC1794317B43E59E4944D34AA0BF17intermappercom_ Content-Type: text/html; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable Dave,

Dave T=E4ht wrote:

I spent the last two weeks hunting down memory related
issues and trying to fold in some development work I'd had
going already.

As best as I can tell, the core memory issues are killed dead; whether
this is due to freeing up tons of memory or by the various other stuff
remains to be determined.

Great work and excellent news!

But:

Under *no circumstances* install this release on your default router.

Yeah. A few short comments on 3.3.8-21:

1)  I cannot connect to gw.home.lan via DNS. Dig gives no answers= . I can log in just fine on 172.30.42.1, etc. and config the router, etc.

2) More on the Hurricane Electric tunnel. After adding these lines to = the config script on the wiki page:

uci set network.henet.adv_subnet=3D1        # adde= d for 3.3.8-17
uci set network.henet.adv_interface=3Dse00
uci set network.henet.adv_interface=3Dsw10

I still cannot connect/get an IPv6 address on se00, *but* I can get ad= dresses on all four wireless channels. (In retrospect, I believe this was t= rue for 3.3.8-17 as well.)

3) Is it possible that DNS come back earlier in the boot sequence? It = seemed that CeroWrt began responding within a minute (or so) to DNS queries= , instead of the 2-5 minutes that I've seen with earlier builds.

Thanks again.

Rich Brown
Hanover, NH USA
--_000_78BC1794317B43E59E4944D34AA0BF17intermappercom_--