General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Rich Brown <richb.hanover@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [Cerowrt-devel] OT: Netflix vs 6in4 from HE.net
Date: Sat, 21 Mar 2020 18:06:14 -0400	[thread overview]
Message-ID: <9061.1584828374@localhost> (raw)
In-Reply-To: <EB01ADF9-3C04-4381-BF60-8DE795935FDA@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]


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.

I suspect it's part of a geo-fencing system.

    > 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.

If your only IPv6 is via the tunnel, then I'd blacklist the netflix device
from getting IPv6.  (Maybe that fails because it's your general purpose laptop)

Maybe you would be able to determine what IPv6 destinations are netflix, and
blacklist that, but given that it usually uses a stack of EC2, etc. servers,
that might be too big a gun.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2020-03-21 22:06 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 [this message]
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=9061.1584828374@localhost \
    --to=mcr@sandelman.ca \
    --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