From: Dave Taht <dave.taht@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Rich Brown <richb.hanover@gmail.com>,
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 15:41:19 -0700 [thread overview]
Message-ID: <CAA93jw6jWPc8w=Mu86oxTGUUUFkJTXap=TgNUawkXt7RWNJC5Q@mail.gmail.com> (raw)
In-Reply-To: <54620DA1-1B6B-456E-990E-3C99B6779887@gmx.de>
Per the url I posted earlier you can stick something like this into
/etc/firewall.user
ip -6 route add blackhole 2406:da00:ff00::/96 # AWS
ip -6 route add blackhole 2607:FB10::/32
ip -6 route add blackhole 2620:0:ef0::/48
ip -6 route add blackhole 2a00:86c0::/32
I actually used "unreach" and put it in /etc/config/networks
config 'route6' 'killnetflix61'
option 'interface' 'lan'
option 'target' '2406:da00:ff00::/96'
option 'type' 'unreachable'
option 'proto' '50'
... etc...
I then used the proto 50 bit (requires ip-full), to make babel pick it up with
a redistribute proto 50
line. (I use this also to propigate /22s around for ipv4)
Neither approach is something "joe user" will be able to do.
But it turned out to be essentially just as much work to just
propigate my native /60s
to the entire campus network statically and try to work out what new security
holes I'd introduced. I have 22 APs to renumber if I get renumbered,
and a few dns entries.
On Sat, Mar 21, 2020 at 3:14 PM Sebastian Moeller <moeller0@gmx.de> wrote:
>
> 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
>
> _______________________________________________
> 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 22:41 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 ` Dave Taht [this message]
2020-03-22 0:47 ` 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='CAA93jw6jWPc8w=Mu86oxTGUUUFkJTXap=TgNUawkXt7RWNJC5Q@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--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