From: Sebastian Moeller <moeller0@gmx.de>
To: Rich Brown <richb.hanover@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] OT: Netflix vs 6in4 from HE.net
Date: Sat, 21 Mar 2020 23:14:26 +0100 [thread overview]
Message-ID: <54620DA1-1B6B-456E-990E-3C99B6779887@gmx.de> (raw)
In-Reply-To: <EB01ADF9-3C04-4381-BF60-8DE795935FDA@gmail.com>
Hi Rich,
since it seems to be IPv6 related, why not use firefox for netflix and disable IPv6 in firefox (see https://support.mozilla.org/en-US/kb/firefox-cant-load-websites-other-browsers-can#w_ipv6) maybe that works well enough?
Best Regards
Sebastian
> On Mar 21, 2020, at 21:20, 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.
>
> Rich
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2020-03-21 22:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 20:20 Rich Brown
2020-03-21 20:27 ` [Bloat] [Cerowrt-devel] " Dave Taht
2020-03-21 22:06 ` Michael Richardson
2020-03-21 22:14 ` Sebastian Moeller [this message]
2020-03-21 22:41 ` 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=54620DA1-1B6B-456E-990E-3C99B6779887@gmx.de \
--to=moeller0@gmx.de \
--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