From: Richard Brown <richard.e.brown@dartware.com>
To: "<cerowrt-devel@lists.bufferbloat.net>"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] development snapshot of cerowrt-3.3.8-21 released
Date: Wed, 29 Aug 2012 01:28:25 +0000 [thread overview]
Message-ID: <78BC1794-317B-43E5-9E49-44D34AA0BF17@intermapper.com> (raw)
In-Reply-To: <mailman.2.1346180401.6345.cerowrt-devel@lists.bufferbloat.net>
[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]
Dave,
Dave Täht 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=1 # added for 3.3.8-17
uci set network.henet.adv_interface=se00
uci set network.henet.adv_interface=sw10
I still cannot connect/get an IPv6 address on se00, *but* I can get addresses on all four wireless channels. (In retrospect, I believe this was true 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
[-- Attachment #2: Type: text/html, Size: 3144 bytes --]
next parent reply other threads:[~2012-08-29 1:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2.1346180401.6345.cerowrt-devel@lists.bufferbloat.net>
2012-08-29 1:28 ` Richard Brown [this message]
[not found] ` <CAA=Zby6UqJfyP34siWkMbAqSWMay10TzhQRz0Bsvq-_MwxcEyw@mail.gmail.com>
[not found] ` <CAA=Zby48DBrOZpWbMuGGrP9-aVMyEe-xuo2ER830PV+Ek6US0g@mail.gmail.com>
2012-08-29 12:18 ` Robert Bradley
2012-08-29 15:53 ` Robert Bradley
2012-08-29 14:10 ` [Cerowrt-devel] Fwd: " Robert Bradley
2012-08-27 23:15 [Cerowrt-devel] " Dave Taht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=78BC1794-317B-43E5-9E49-44D34AA0BF17@intermapper.com \
--to=richard.e.brown@dartware.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox