On 25/Jun/20 18:08, Brandon Jackson via NANOG wrote:
> Actually it's a good thing that Netflix does support IPv6 for this. As
> any device using Netflix via IPv6 from your ISP would likely correctly
> be protected as not a VPN or proxy.
>
> The problem is the ISPs that deploy CGNAT without
Hi Adam,
> On 25 Jun 2020, at 16:55, Adam Thompson wrote:
>
> So in the ARIN world, Krill only works with "delegated" RPKI, not "hosted"
> RPKI - do I understand that correctly?
Krill is RPKI Certificate Authority software to run Delegated RPKI under one or
multiple RIRs simultaneously. It’s
On 26/Jun/20 03:12, Denys Fedoryshchenko wrote:
>
>
> Honestly, this is very confusing suggestion from Netflix support (i
> have native ipv6!).
> Looking to
> https://www.reddit.com/r/ipv6/comments/evv7r8/ipv6_and_netflix/ there
> is definitely some issues for other users too.
This seems to
On Thu, 2020-06-25 at 17:32 -0500, Mike Hammett wrote:
> IPv6?
I realize this list is for network operators, but as a user, when your
ISP doesn't provide IPv6, this is not possible. Even with
tunnelbrokers like HE as they are blocked at Netflix. I have to put
rules in my firewall to force the
On 6/26/20 1:42 PM, Sabri Berisha wrote:
Hi,
Hi,
This is the part that matters the most. I'm sure they're willing.
Let's agree to disagree on Netflix's willingness.
I'm also sure that in the past, enough people have abused their
trust.
I question the veracity of that statement.
Since
- On Jun 26, 2020, at 1:21 AM, Mark Tinka mark.ti...@seacom.com wrote:
Hi,
> Sadly, PlayStation still don't support IPv6. Hopefully, it comes with
> the PS5,
Don't hold your breath. It's most likely not related to the capabilities
of the hardware, or even the kernel running on the
On Fri, 2020-06-26 at 12:45 -0500, Mike Hammett wrote:
> I believe they're only blocking the HE v6 prefixes used for the VPN
> service.
I don't use any VPN service of HE but I still get errors from Netflix
when my client chooses my HE tunnel prefix as it's source.
Or I guess I should say I was,
I believe they're only blocking the HE v6 prefixes used for the VPN service.
-
Mike Hammett
Intelligent Computing Solutions
Midwest Internet Exchange
The Brothers WISP
- Original Message -
From: "Gary E. Miller"
To: nanog@nanog.org
Sent: Friday, June 26, 2020 12:25:07
On 6/26/20 12:08 PM, Brandon Jackson via NANOG wrote:
Correct they block HE.net's tunnel broker IP's because they practically
are at least for the sense of geo restrictions "VPN" that can be used to
get around said geo restriction.
I want to agree, but I can't. Move up the stack. I pay my
> On Fri, 2020-06-26 at 12:45 -0500, Mike Hammett wrote:
>> I believe they're only blocking the HE v6 prefixes used for the VPN
>> service.
>
I don’t understand the rational to block specific ipv6 ranges, for example the
UK ipv6 ranges and Africa ipv6 ranges are not blocked from testing done
On 6/26/20 3:21 PM, William Herrin wrote:
Hi Grant,
Hi,
Philosophically, Netflix agrees with you.
My interactions with and observations of Netflix make me want to
disagree with you.
Unfortunately they have to keep the studios happy or many of their
content contracts evaporate.
I fail
Yo Mark!
On Fri, 26 Jun 2020 10:21:47 +0200
Mark Tinka wrote:
> If you don't use some kind of device to connect to Netflix, if you
> have a reasonably modern TV that supports a native Netflix app as
> well as IPv6, you'd be good to go.
Nope. Netflix blocks a lot of IPv6. Their blocking of HE
This is an automated weekly mailing describing the state of the Internet
Routing Table as seen from APNIC's router in Japan.
The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG
TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG.
Daily listings are sent to
Correct they block HE.net's tunnel broker IP's because they practically are
at least for the sense of geo restrictions "VPN" that can be used to get
around said geo restriction.
As much as I hate it as I use said tunnel service it is understandable and
I don't really blame Netflix for this, I
Media licensing is a complicated topic and the source of all of these problems.
-
Mike Hammett
Intelligent Computing Solutions
Midwest Internet Exchange
The Brothers WISP
- Original Message -
From: "colin johnston"
To: "Brian J. Murrell"
Cc: nanog@nanog.org
Sent:
On Fri, Jun 26, 2020 at 12:34 PM Grant Taylor via NANOG wrote:
> I want to agree, but I can't. Move up the stack. I pay my bill with a
> CC which has my billing address. I would even be willing to tell
> Netflix my home address directly.
>
> If they are willing to trust the CC information to
- On Jun 26, 2020, at 12:32 PM, nanog nanog@nanog.org wrote:
Hi,
> they should also be willing to trust the information for my service address.
This is the part that matters the most. I'm sure they're willing. I'm also
sure that in the past, enough people have abused their trust. Since they
I take his statement more as:
“If Netflix wasn’t doing IPv6, they’d be in more of a corner
to resolve CGNAT issues. Since they support IPv6, likely their
response to CGNAT issues is ``Press your provider to do IPv6,
it’s better.’’”
Likely, that is true. Support
> Perhaps BGP Alerter is a solution for you:
> https://github.com/nttgin/BGPalerter
yes! very happy user here. i run it into the slack api.
randy
> On Jun 25, 2020, at 8:38 AM, Mark Tinka wrote:
>
>
>
> On 25/Jun/20 16:45, Christian wrote:
>> wow. blaming support for IPv6 rather than using cgnat is a huge
>> stretch of credibility
>
> I have no idea what's going through Netflix's mind - it's all, as my
> American friend would say,
20 matches
Mail list logo
