From: Chuck Anderson <cra@WPI.EDU>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] cerowrt-3.10.24-8 "North Pole" development build released
Date: Tue, 24 Dec 2013 20:43:03 -0500 [thread overview]
Message-ID: <20131225014302.GB7978@angus.ind.WPI.EDU> (raw)
In-Reply-To: <CAA93jw6+8R90ykDw49ryrtQ9RxMDVTgMNp=bMvYwcFPWMjUK7Q@mail.gmail.com>
On Tue, Dec 24, 2013 at 11:51:56AM -0800, Dave Taht wrote:
> I expect I'll get another cero out before the new year. The biggest
> problem I see
> is that I can't get ipv6 from comcast to work. As to that being cero
> (6relayd?) or this crappy cable modem, don't know. Need to setup a
> dhcpv6 server to test it.
Did you happen to see Randy Bush's problems with Comcast IPv6 &
OpenWRT on nanog recently? I don't know how much of this applies to
CeroWRT, but here was his solution:
http://rtechblog.psg.com/
I'm still waiting for native IPv6 support on my Comcast CMTS...until
them I'm using an HE tunnel.
next prev parent reply other threads:[~2013-12-25 1:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 19:51 Dave Taht
2013-12-25 1:43 ` Chuck Anderson [this message]
2013-12-25 19:25 ` Michael Richardson
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=20131225014302.GB7978@angus.ind.WPI.EDU \
--to=cra@wpi.edu \
--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