From: Dave Taht <dave.taht@gmail.com>
To: Colin Dearborn <Colin.Dearborn@sjrb.ca>
Cc: "David P. Reed" <dpreed@deepplum.com>,
Rich Brown <richb.hanover@gmail.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel] OT: Netflix vs 6in4 from HE.net
Date: Tue, 24 Mar 2020 10:47:07 -0700 [thread overview]
Message-ID: <CAA93jw5ROA9mGtSbQ5WPkpmT_dvYopWzuQpsMsEZ_+Q5s3FAXQ@mail.gmail.com> (raw)
In-Reply-To: <MWHPR04MB06718C00021A4561606ACD8895F10@MWHPR04MB0671.namprd04.prod.outlook.com>
It is easy to use a nearby linode server as an ipv6 vpn. Back when I was still
doing it (I too went native ipv6), I used wireguard and babel and
source specific routing to bring ipv6 anywhere I felt I needed it.
Linode will give you your own ipv6/64 if asked. If asked especially
nicely you can get a /56....
whether or not they meet netflix's requirements for geolocation i don't know.
next prev parent reply other threads:[~2020-03-24 17:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 20:20 [Bloat] " Rich Brown
2020-03-21 20:27 ` [Bloat] [Cerowrt-devel] " Dave Taht
2020-03-21 22:06 ` Michael Richardson
2020-03-21 22:14 ` [Bloat] " Sebastian Moeller
2020-03-21 22:41 ` [Bloat] [Cerowrt-devel] " Dave Taht
2020-03-22 0:47 ` [Bloat] " Rich Brown
2020-03-22 21:31 ` [Bloat] [Cerowrt-devel] " David P. Reed
2020-03-24 15:11 ` Colin Dearborn
2020-03-24 17:47 ` Dave Taht [this message]
2020-03-24 22:19 ` David P. Reed
[not found] ` <MWHPR04MB06718C00021A4561606ACD8895F10@MWHPR04MB0671.namprd04.prod.outloo k.com>
[not found] ` <MWHPR04MB06718C00021A4561606ACD8895F10@MWHPR04MB0671.namprd04.prod.outlook.c om>
2020-03-24 22:28 ` David P. Reed
2020-03-24 22:47 ` Mark Andrews
2020-03-26 20:29 ` Michael Richardson
2020-03-25 8:56 ` Toke Høiland-Jørgensen
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw5ROA9mGtSbQ5WPkpmT_dvYopWzuQpsMsEZ_+Q5s3FAXQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=Colin.Dearborn@sjrb.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dpreed@deepplum.com \
--cc=richb.hanover@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