From: Dave Taht <dave.taht@gmail.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel] OT: Netflix vs 6in4 from HE.net
Date: Sat, 21 Mar 2020 13:27:13 -0700 [thread overview]
Message-ID: <CAA93jw50YqOEXdpOcT-5EViC3J=WCQKRJ37TkRDdaq+svbxAWQ@mail.gmail.com> (raw)
In-Reply-To: <EB01ADF9-3C04-4381-BF60-8DE795935FDA@gmail.com>
On Sat, Mar 21, 2020 at 1:20 PM Rich Brown <richb.hanover@gmail.com> wrote:
>
> to Bloat & CeroWrt folks: This is a little OT for either of these lists, but I figured there are plenty of experts here, and I would be delighted to get your thoughts.
>
> I just tried to view a Netflix movie and got a F7111-5059 error message. This prevented the video from playing. (As recently as a month or two ago, it worked fine.)
>
> Googling the error message gets to this page https://help.netflix.com/en/node/54085 that singles out use of an IPv6 Proxy Tunnel.
>
> Sure enough, I'm have a 6in4 tunnel through Hurricane Electric on WAN6. Stopping that WAN6 interface caused Netflix to work.
>
> What advice could you offer? (I could, of course, turn off WAN6 to watch movies. But that's a drag, and other family members couldn't do this.) Many thanks.
This happened to me over a year back.
http://www.peachyphotos.com/blog/posts/netflix-and-hurricane-electrics-ipv6-service/
Briefly I swtched to just blackholing netflix's ipv6 range, then I
tunnled my linode connection, then I switched to just universally
using comcast native ipv6 (with source specific routing and static
assignments on the key routers).
I was VERY reluctant to do this as comcast reserves the right to
change your ipv6 addressing at any point, and it changes if you change
routers, but having to manually reconfigure a dozen routers and
several servers if it ever changes seemed easiest. I dread
renumbering...
The vast majority of my traffic in the evenings is ipv6 now.
> Rich
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Make Music, Not War
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729
next prev parent reply other threads:[~2020-03-21 20:27 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 ` Dave Taht [this message]
2020-03-21 22:06 ` [Bloat] [Cerowrt-devel] " 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
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='CAA93jw50YqOEXdpOcT-5EViC3J=WCQKRJ37TkRDdaq+svbxAWQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--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