Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] ipv6 applicability to mobile handsets
Date: Thu, 13 Feb 2014 18:40:47 -0500	[thread overview]
Message-ID: <CAA93jw4w-ONcT6esowY1-y=d-ep=rpiZjCrO2ve=AD-KRd1MiA@mail.gmail.com> (raw)

I just realized that much of what we've done with dnsmasq, dhcpv6
support, naming, and source-specific routing, etc, actually also
applies to solving the ipv6 tethering problem operators like t-mobile
have. Thoroughly.

http://tools.ietf.org/html/draft-ietf-v6ops-64share-09

it is seemingly trivial to update an android to use dnsmasq as it's intermediate
dns proxy, and with the upcoming version also doing dnssec, perhaps it will
gain traction on android outside of  tethering.

-- 
Dave Täht

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

                 reply	other threads:[~2014-02-13 23:40 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='CAA93jw4w-ONcT6esowY1-y=d-ep=rpiZjCrO2ve=AD-KRd1MiA@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