Mark Andrews wrote:
> 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 fro
"David P. Reed" writes:
> 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 onl
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
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
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
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
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
This might turn out to be a problem for me - I have a "smart TV" that I watch
Netflix on, and it appears to use IPv4. What specifically triggers Netflix to
reject specific IPv6 clients? Is it the player's IPv6 address? Is all of
he.net's address space blocked?
I've been planning to move more of
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 "u
Rich Brown 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 pr
On Sat, Mar 21, 2020 at 1:20 PM Rich Brown 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 me
11 matches
Mail list logo
