From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] ipv6 nat
Date: Mon, 21 Oct 2013 11:53:30 -0700 [thread overview]
Message-ID: <CAA93jw6HWeSAV+Gd4zP+qx9JqZgLyAr_UxS+kGQQjJvn-U7jqQ@mail.gmail.com> (raw)
there has been ipv6 nat support in cero for a while, if anyone wants to try it.
Rumor has it that comcast is only handing out a /60 address, which,
while enough for 2.5 cero routers is kind of annoying compared to the
address cornucopia that is ipv6.
I'm not happy with the state of AHCP, but as it's possible to get by
on a single /64 with that + babel, perhaps more will fiddle with that,
too.
Similarly I kind of foresee ipv6 nat happening for tethered phones, too,
Anyway, ipv6 nat. in the same sentence. I wish it didn't have to have
come to this...
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
reply other threads:[~2013-10-21 18:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAA93jw6HWeSAV+Gd4zP+qx9JqZgLyAr_UxS+kGQQjJvn-U7jqQ@mail.gmail.com \
--to=dave.taht@gmail.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