Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Richard Brown <richard.e.brown@dartware.com>
Cc: "<cerowrt-devel@lists.bufferbloat.net>"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] CeroWrt 3.6.11-2 is out with ipv6-support package, bleeding edge dnsmasq, upnp,
Date: Wed, 26 Dec 2012 17:34:04 +0100	[thread overview]
Message-ID: <CAA93jw7VQqPwtDQ9uZ-fsobQ7qY4wdc2uzPjV9YeAYUvp8ckdw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7HYkFRwd_Z0QZkrn5FsFCfDWfFYFsyt1JnF+c4Oi7asQ@mail.gmail.com>

I note that the bufferbloat.net domain filters out ip addresses in
message bodies, so richard's original message probably didn't make the
list. I have to find a fix for that - so 172 dot X dot Y dot Z goes
through.

...

Thx for the complete report!

Configuration name problem noted and fixed. (hopefully). Have to automate
that, I keep doing it...

An update to the luci upnp gui landed a day or two ago for upnp, it's my
hope that addresses the bug there, but as I am still 3000 miles away from
the nearest router I dare reflash I won't be in a position to test til
saturday. I did do a build with that fix in it:

http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.6.11-3/

Which is so trivial as you can do a sysupgrade to it without harming your
existing config. Unless I broke something else.

The default configuration defaults to generating ULAs which are local ipv6
addresses in the fd:: range. While this is useful for bringing up a ipv6
network, it's not so useful for connecting to the outside world with it, as
you've discovered. My hope is with the linux 3.7 release to be able to
enable npt66 by default in this case, (which was the source of some
controversy earlier this month), but using 3.7 as a base is a bit of a long
way out. I'm trying to get on top of the 3.7 issue (and some other gui
stuff) by doing an x86 virtual build (which so far, doesn't boot)

As for not distributing the 2001:: (and disabling the ula entirely) I don't
know - that package is so bleeding edge as yet! Happy hacking.




-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

  reply	other threads:[~2012-12-26 16:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2.1356379202.14075.cerowrt-devel@lists.bufferbloat.net>
2012-12-26 15:50 ` Richard Brown
     [not found]   ` <CAA93jw4X_=6O2Pnwk1wX+bKXGQHeUXrE3DGj1sAtPL_dUMQO1A@mail.gmail.com>
2012-12-26 16:26     ` Dave Taht
2012-12-26 16:34       ` Dave Taht [this message]
2012-12-26 21:19     ` [Cerowrt-devel] CeroWrt 3.6.11-3 Richard Brown
2012-12-27  7:09       ` Chris Lawrence
2012-12-23 20:08 [Cerowrt-devel] CeroWrt 3.6.11-2 is out with ipv6-support package, bleeding edge dnsmasq, upnp, Dave Taht
2012-12-23 20:09 ` Dave Taht
2012-12-23 20:29   ` Dave Taht
2012-12-23 20:41 ` Maciej Soltysiak
2012-12-23 22:31   ` 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=CAA93jw7VQqPwtDQ9uZ-fsobQ7qY4wdc2uzPjV9YeAYUvp8ckdw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=richard.e.brown@dartware.com \
    /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