From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] notes on going for a stable release
Date: Wed, 15 Jan 2014 10:31:54 -0700 [thread overview]
Message-ID: <CAK-n8j6Nf3Wr3j5W4Tma99cOzYKjNyHZ3UBxdz-jiKj_+c87zw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6PZk_5FZbgq0U_K9CL=xE9ZP+-U09HwkwNaDREjj4fOw@mail.gmail.com>
On Mon, Jan 13, 2014 at 11:07 PM, Dave Taht wrote:
> ** Native IPv6 and dhcpv6-pd support
> I am very happy with comcast's huge rollout of ipv6 across their
> network. (over 25% of their base now) http://www.comcast6.net .
>
> Hearing that cero isn't working on comcast anymore bugs me. I don't
> seem to have ipv6 on my directly controlled comcast nodes. Yet.
>
> Setting up a dhcpv6-pd server and some testing is required to make
> sure it isn't cerowrt that's busted. I'd like to not go another year
> without ipv6.
If you want help testing/debugging this, let me know. I could give
you access to my router if you want to experiment (as long as the
Internet connectivity isn't down for more than a couple of minutes at
a time).
- Jim
--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us
next prev parent reply other threads:[~2014-01-15 17:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 6:07 Dave Taht
2014-01-14 8:37 ` Christopher Robin
2014-01-14 9:44 ` Toke Høiland-Jørgensen
2014-01-14 12:51 ` David Personette
2014-01-14 13:20 ` Rich Brown
2014-01-14 15:30 ` Dave Taht
2014-01-16 3:20 ` Theodore Ts'o
2014-01-15 15:18 ` Dave Taht
2014-01-14 12:10 ` Juergen Botz
2014-01-14 15:10 ` Dave Taht
2014-01-14 12:36 ` David Personette
2014-01-15 4:11 ` Dave Taht
[not found] ` <CAMybZqzs9ES9G23ke-PjU759wxbQNMytYa4EHmv0H8HqpPwwPQ@mail.gmail.com>
2014-01-15 14:47 ` Dave Taht
2014-01-15 0:30 ` David Lang
2014-01-15 17:31 ` Jim Reisert AD1C [this message]
2014-01-20 15:00 ` Maciej Soltysiak
2014-01-20 15:15 ` [Cerowrt-devel] notes on going for a stable release/replacement router Rich Brown
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=CAK-n8j6Nf3Wr3j5W4Tma99cOzYKjNyHZ3UBxdz-jiKj_+c87zw@mail.gmail.com \
--to=jjreisert@alum.mit.edu \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.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