Re: [Bloat] [Cerowrt-devel] OT: Netflix vs 6in4 from HE.net

2020-03-24 Thread Colin Dearborn
HE IPv6 space has been tagged as a vpn type service by Netflix, since it has users all over the world, but it's space is all geolocated in the US. If HE had geolocated the blocks of each POP to the country the POP resided in, and put some rules around geolocation of using each POP (IE Canadian r

Re: [Bloat] [Cerowrt-devel] OT: Netflix vs 6in4 from HE.net

2020-03-24 Thread Dave Taht
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

Re: [Bloat] [Cerowrt-devel] OT: Netflix vs 6in4 from HE.net

2020-03-24 Thread David P. Reed
Sadly, my home provider, RCN, which is otherwise hugely better than Comcast and Verizon provisioning wise, still won't provide IPv6 to its customers. It's a corporate level decision. I know the regional network operations guys, which is why I know about the provisioning - they have very high-end

Re: [Bloat] [Cerowrt-devel] OT: Netflix vs 6in4 from HE.net

2020-03-24 Thread David P. Reed
Thanks, Colin, for the info. Sadly, I learned all about the licensing of content in the industry back about 20 years ago when I was active in the battles about Xcasting rights internationally (extending "broadcast rights" to the Web, which are rights that exist only in the EU, having to do with

Re: [Bloat] [Cerowrt-devel] OT: Netflix vs 6in4 from HE.net

2020-03-24 Thread Mark Andrews
Netflix could just redirect requests from HE.NET address ranges to IPv4 only servers and that would solve the issue for all HE.NET customers. This isn’t the case of attempting to circumvent GEOIP rules. They can detect that the connection is coming from a HE.NET address range, they can easily

[Bloat] Still seeing bloat with a DOCSIS 3.1 modem

2020-03-24 Thread Aaron Wood
I recently upgraded service from 150up, 10dn Mbps to xfinity's gigabit (with 35Mbps up) tier, and picked up a DOCSIS 3.1 modem to go with it. Flent test results are here: https://burntchrome.blogspot.com/2020/03/bufferbloat-with-comcast-gigabit-with.html tl/dr; 1000ms of upstream bufferbloat Bu

Re: [Bloat] Still seeing bloat with a DOCSIS 3.1 modem

2020-03-24 Thread Aaron Wood
(hit send early, somehow)... Although this thread makes we wonder if perhaps not: https://lists.bufferbloat.net/pipermail/cake/2018-August/004285.html On Tue, Mar 24, 2020 at 10:01 PM Aaron Wood wrote: > I recently upgraded service from 150up, 10dn Mbps to xfinity's gigabit > (with 35Mbps up)

Re: [Bloat] Still seeing bloat with a DOCSIS 3.1 modem

2020-03-24 Thread Matt Taggart
On 3/24/20 10:01 PM, Aaron Wood wrote: [snip] At the moment, however, my WRT1900AC isn't up to the task of dealing with these sorts of downstream rates. So I'm looking at the apu2, which from this post: https://forum.openwrt.org/t/comparative-throughput-testing-including-nat-sqm-wireguard-and-o

Re: [Bloat] Still seeing bloat with a DOCSIS 3.1 modem

2020-03-24 Thread Sebastian Moeller
So, for higher bandwidth plans people started using raspberry pi4bs with an additional usb3 Ethernet dongle. Its WiFi is not really up for the task but it does seem to make a mean wired only router, the quad A76 cores seem to be capable to reliably shape up to 1 gigabit with cpu cycles to spare.