Re: Netflix VPN detection - actual engineer needed

On 08/06/2016 18:17, Owen DeLong wrote: >>> Get your own /48 and advertise to HE Tunnel via BGP. Problem solved. >> >> Even though that sounds like an awesome idea it does not seem trivial to >> me to obtain your own /48. > > It’s trivial in the ARIN region. Other regions are YMMV. I thought you

Re: Netflix VPN detection - actual engineer needed

On 08/06/2016 18:23, Laszlo Hanyecz wrote: > Well there is one good thing that might come out of this if you're a > tunnel user.. the tunnels can have even more bandwidth now, with all the > Netflix traffic moving off them. I have no special visibility into how > (over)loaded they are, just

Re: Turning Off IPv6 for Good (was Re: Netflix VPN detection - actual engineer needed)

On 6/1/16 9:23 PM, Roland Dobbins wrote: On 2 Jun 2016, at 10:47, Paul Ferguson wrote: There is an epic lesson here. I'm just not sure what it is. :-) That Netflix offering free streaming to everyone over IPv6 (after fixing their VPN detection) would be the most effective way to convince

Re: Netflix VPN detection - actual engineer needed

On Wed, 8 Jun 2016, Baldur Norddahl wrote: A start would be blocking 2620:108:700f::/64 as discovered by a simple DNS lookup on netflix.com. I am not running a HE tunnel (I got native IPv6) and I am not blocked from accessing Netflix over IPv6 so can't really try it. I am I sent some email

Re: Netflix VPN detection - actual engineer needed

On Wed, 8 Jun 2016, Mark Andrews wrote: And which set of prefixes is that? How often do they change? etc. Apparently there's only 2620:108:7000::/44 and I doubt it'll change often. An associate actually reported this problem to me today. I ended up just installing a host firewall rule on

Re: Netflix VPN detection - actual engineer needed

Why? I use Mobile Hotspot… It’s part of the service I pay for. If Cameron can’t make that work, then that’s T-Mobile’s problem, not mine. Owen > On Jun 8, 2016, at 1:25 PM, joel jaeggli wrote: > > On 6/8/16 9:13 AM, Owen DeLong wrote: >> As of last week, I still wasn’t

Re: Netflix VPN detection - actual engineer needed

On 6/8/16 9:13 AM, Owen DeLong wrote: > As of last week, I still wasn’t getting an IPv6 address by default on my > iPhone 6S+ > on T-Mobile. turn off mobile hotspot... > Just saying. > > Owen > >> On Jun 7, 2016, at 11:00 AM, Ca By wrote: >> >> On Tuesday, June 7, 2016,

Re: Netflix VPN detection - actual engineer needed

On 2016-06-08 17:20, Javier J wrote: Maybe I missed the start of this conversation but why are we talking about blocking Netflix? By blocking the netflix.com IPv6 prefix your browser will automatically fall back to IPv4 because it is using the Happy Eyeballs algorithm.

Re: Netflix VPN detection - actual engineer needed

On 2016-06-08 17:58, Nicholas Suan wrote: On Wednesday, June 8, 2016, Baldur Norddahl > wrote: A start would be blocking 2620:108:700f::/64 as discovered by a simple DNS lookup on netflix.com . I am

Re: Netflix VPN detection - actual engineer needed

On 2016-06-08 16:12, Owen DeLong wrote: It’s a link, just like any other link, over which IPv6 can be transmitted. You can argue that it’s a lower quality link than some alternatives, but I have to tell you I’ve gotten much more reliable service at higher bandwidth from that link than from my

Re: Netflix VPN detection - actual engineer needed

> On Jun 7, 2016, at 11:50 AM, Davide Davini wrote: > > On 04/06/2016 20:46, Owen DeLong wrote: >> Get your own /48 and advertise to HE Tunnel via BGP. Problem solved. > > Even though that sounds like an awesome idea it does not seem trivial to > me to obtain your

Re: Netflix VPN detection - actual engineer needed

As of last week, I still wasn’t getting an IPv6 address by default on my iPhone 6S+ on T-Mobile. Just saying. Owen > On Jun 7, 2016, at 11:00 AM, Ca By wrote: > > On Tuesday, June 7, 2016, Cryptographrix wrote: > >> Very true - I was being a

Re: Netflix VPN detection - actual engineer needed

> On Jun 7, 2016, at 10:22 AM, Ca By wrote: > > On Tuesday, June 7, 2016, Cryptographrix wrote: > >> As I said to Netflix's tech support - if they advocate for people to turn >> off IPv6 on their end, maybe Netflix should stop supporting it on

Re: Netflix VPN detection - actual engineer needed

On Wednesday, June 8, 2016, Baldur Norddahl wrote: > > > On 2016-06-08 07:27, Mark Andrews wrote: > >> In message <20160608070525.06fd5...@echo.ms.redpill-linpro.com>, Tore >> Anderson writes: >> >>> * Davide Davini >>> >>> Blocking access to

Re: Netflix VPN detection - actual engineer needed

On Wed 2016-Jun-08 11:23:35 -0400, Owen DeLong wrote: On Jun 7, 2016, at 9:21 AM, Mark Felder wrote: On Jun 6, 2016, at 22:25, Spencer Ryan wrote: The tunnelbroker service acts exactly like a VPN. It allows you, from any arbitrary location

Re: Netflix VPN detection - actual engineer needed

On Wed, Jun 8, 2016, at 10:23, Owen DeLong wrote: > Mark, > > That would be bad. > > At least in my case. > The trailing /s at the end was the sarcasm tag :-) -- Mark Felder f...@feld.me

Re: Netflix VPN detection - actual engineer needed

> On Jun 8, 2016, at 8:13 AM, Baldur Norddahl wrote: > > > > On 2016-06-08 07:27, Mark Andrews wrote: >> In message <20160608070525.06fd5...@echo.ms.redpill-linpro.com>, Tore >> Anderson writes: >>> * Davide Davini >>> >>> Blocking access to

Re: Netflix VPN detection - actual engineer needed

Mark, That would be bad. At least in my case. My addresses (192.159.10.0/24, 192.124.40.0/23, 2620:0:930::/48) are not from a known residential ISP or mobile ISP. However, they are within my household and nowhere else. There’s no valid reason for Netflix to block them. They are not a server

Re: Netflix VPN detection - actual engineer needed

On 2016-06-08 07:27, Mark Andrews wrote: In message <20160608070525.06fd5...@echo.ms.redpill-linpro.com>, Tore Anderson writes: * Davide Davini Blocking access to Netflix via the tunnel seems like an obvious solution to me, for what it's worth. And which set of

Re: Netflix VPN detection - actual engineer needed

On Wed, 8 Jun 2016, Tore Anderson wrote: I wonder if anyone has attempted to estimate approx. how much RIB/FIB space a single DFZ route requires in total across the entire internet... You mean in money? A lot. The problem is that we have so far no feasible way to make "polluter pay". So

Re: Netflix VPN detection - actual engineer needed

In message <20160608070525.06fd5...@echo.ms.redpill-linpro.com>, Tore Anderson writes: > * Davide Davini > > > On 04/06/2016 20:46, Owen DeLong wrote: > > > Get your own /48 and advertise to HE Tunnel via BGP. Problem > > > solved. > > > > Even though that sounds like

Re: Netflix VPN detection - actual engineer needed

* Davide Davini > On 04/06/2016 20:46, Owen DeLong wrote: > > Get your own /48 and advertise to HE Tunnel via BGP. Problem > > solved. > > Even though that sounds like an awesome idea it does not seem trivial > to me to obtain your own /48. Which is a good thing, as

Re: Netflix VPN detection - actual engineer needed

Some of this reminds me of talking to IBM the the other day about problems I was having with their "Rapport Trusteer" security package which one of my banks requires to be running when I try to log in. Invariably the bank claims it's not running, I restart it that software, still no-go, the

Re: Netflix VPN detection - actual engineer needed

On 07/06/2016 17:00, Ca By wrote: > fixed line: Comcast, AT, TWC, just to name the largest in the nation have > meaningful deployments of ipv6. The only thing holding back greater > deployment for those networks are legacy CPE that will age out slowly. It is probably totally off topic as this is

Re: Netflix VPN detection - actual engineer needed

On 04/06/2016 20:46, Owen DeLong wrote: > Get your own /48 and advertise to HE Tunnel via BGP. Problem solved. Even though that sounds like an awesome idea it does not seem trivial to me to obtain your own /48. I mean: "You can only request IPv6 assignments and Autonomous System Numbers through

Re: Netflix VPN detection - actual engineer needed

On Tuesday, June 7, 2016, Cryptographrix wrote: > Very true - I was being a bit extremist out of frustration, but I think > you're spot on - he.net tunnels and even 6to4 are toys to provide IPv6 > support, not actually IPv6 support. > > And I'm quite frustrated because

Re: Netflix VPN detection - actual engineer needed

Very true - I was being a bit extremist out of frustration, but I think you're spot on - he.net tunnels and even 6to4 are toys to provide IPv6 support, not actually IPv6 support. And I'm quite frustrated because there's so little actual v6 support, and I *do* actually need it on a daily basis for

Re: Netflix VPN detection - actual engineer needed

On Tuesday, June 7, 2016, Cryptographrix wrote: > As I said to Netflix's tech support - if they advocate for people to turn > off IPv6 on their end, maybe Netflix should stop supporting it on their > end. > > It's in the air whether it's just an HE tunnel issue or an

Re: Netflix VPN detection - actual engineer needed

On 6/7/16 6:55 AM, Cryptographrix wrote: > As I said to Netflix's tech support - if they advocate for people to turn > off IPv6 on their end, maybe Netflix should stop supporting it on their end. > > It's in the air whether it's just an HE tunnel issue or an IPv6 issue at > the moment, and if

Re: Netflix VPN detection - actual engineer needed

As I said to Netflix's tech support - if they advocate for people to turn off IPv6 on their end, maybe Netflix should stop supporting it on their end. It's in the air whether it's just an HE tunnel issue or an IPv6 issue at the moment, and if their tech support is telling people to turn off IPv6,

Re: Netflix VPN detection - actual engineer needed

: "Cryptographrix" <cryptograph...@gmail.com> To: "Mark Felder" <f...@feld.me>, nanog@nanog.org Sent: Tuesday, June 7, 2016 8:55:10 AM Subject: Re: Netflix VPN detection - actual engineer needed As I said to Netflix's tech support - if they advocate for people to tu

Re: Netflix VPN detection - actual engineer needed

> On Jun 6, 2016, at 22:25, Spencer Ryan wrote: > > The tunnelbroker service acts exactly like a VPN. It allows you, from any > arbitrary location in the world with an IPv4 address, to bring traffic out > via one of HE's 4 POP's, while completely masking your actual location. >

Re: Netflix VPN detection - actual engineer needed

> On Jun 6, 2016, at 18:12, Baldur Norddahl wrote: > > It is a bit surprising that your browser would choose the ipv6 path via > tunnel over the more direct ipv4 path. Anyway, you could blackhole the > Netflix ipv6 prefix to force the situation. > On modern Apple

Re: Netflix VPN detection - actual engineer needed

RDAP is same across RIRs. Yes old REST API was PITA On 07/06/2016 02:08, Ricky Beam wrote: > Yes, ARIN and RIPE have REST APIs, but they're completely different > interfaces with different schemas (and different capabilities.) I have > independent applications for talking to each. And those are

Re: Netflix VPN detection - actual engineer needed

I’m sorry to say, Blair, that there are, in fact, many who do use HE tunnels for Geo Fence evasion. Sure, it doesn’t represent even a significant fraction of tunnel users, but they exist and they’ve been vocal, thus spoiling it for the rest of us. Owen > On Jun 6, 2016, at 8:27 PM, Blair Trosper

Re: Netflix VPN detection - actual engineer needed

I believe there are a lot more than 4. Owen > On Jun 6, 2016, at 8:25 PM, Spencer Ryan wrote: > > The tunnelbroker service acts exactly like a VPN. It allows you, from any > arbitrary location in the world with an IPv4 address, to bring traffic out > via one of HE's 4 POP's,

Re: Netflix VPN detection - actual engineer needed

> On Jun 6, 2016, at 6:44 PM, Harald Koch wrote: > > On 6 June 2016 at 19:40, Owen DeLong wrote: > >> >> The problem is that some users travel and they try to watch Netflix using >> their home account in far away lands. >> > > Interestingly, audible.com

Re[2]: Netflix VPN detection - actual engineer needed

nog@nanog.org" <nanog@nanog.org> Sent: 6/6/2016 8:25:40 PM Subject: Re: Netflix VPN detection - actual engineer needed The tunnelbroker service acts exactly like a VPN. It allows you, from any arbitrary location in the world with an IPv4 address, to bring traffic out via one of HE

Re: Netflix VPN detection - actual engineer needed

Right, but I think we know what Netflix is implying when they say "proxy unblocker" or "VPN" -- they mean people are deliberately going around GeoIP. In this case, I don't know anyone who uses TunnelBroker that way. They're using it for V6. That is to say, everyone I know with this issue could

Re: Netflix VPN detection - actual engineer needed

The tunnelbroker service acts exactly like a VPN. It allows you, from any arbitrary location in the world with an IPv4 address, to bring traffic out via one of HE's 4 POP's, while completely masking your actual location. *Spencer Ryan* | Senior Systems Administrator | sr...@arbor.net *Arbor

Re: Netflix VPN detection - actual engineer needed

It should be pointed out that -- the SPECIFIC accusation from Netflix -- is that people on TunnelBroker are on a VPN or proxy unblocker. The data does not bear that out. Hash tag just saying. On Mon, Jun 6, 2016 at 7:53 PM, Ricky Beam wrote: > On Mon, 06 Jun 2016 19:41:14

Re: Netflix VPN detection - actual engineer needed

On Mon, 06 Jun 2016 19:41:14 -0400, Mark Andrews wrote: What lie? Truly who is lying here. Not the end user. Not HE. There is no requirement to report physical location. The general lie that is IP Geolocation. HE only has what I tell them (100% unverified), and what

Re: Netflix VPN detection - actual engineer needed

Holy fuck get on your meds. As someone who actually has to deal with 3 different (4 technically) content providers, their distribution agreements and requirements for distribution a the way through the network are absolutely asinine, but required if you want your eyeballs to receive their

Re: Netflix VPN detection - actual engineer needed

> In other words, it's not just Netflix that has this problem... No, it's Netflix that has the problem. Audible actually gives a fuck about their customers.

Re: Netflix VPN detection - actual engineer needed

On 6 June 2016 at 19:40, Owen DeLong wrote: > > The problem is that some users travel and they try to watch Netflix using > their home account in far away lands. > Interestingly, audible.com (the audio book people) actually warn you about this up front - they point out on their

Re: Netflix VPN detection - actual engineer needed

>> Director of Operations | Purchase, NY 10577 >> OTA Management LLC | Phone: 914-460-4039 >> aim: matthewbhuff| Fax: 914-694-5669 >> >>> -Original Message- >>> From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Scott Mori

Re: Netflix VPN detection - actual engineer needed

> On Jun 6, 2016, at 9:01 AM, Laszlo Hanyecz wrote: > > > On 2016-06-06 15:21, Tore Anderson wrote: >> >> But Netflix shouldn't have any need to ask in the first place. Their >> customers need to log in to their own personal accounts in order to >> access any content,

Re: Netflix VPN detection - actual engineer needed

In message , "Ricky Beam" writes: > On Sun, 05 Jun 2016 19:35:27 -0400, Mark Andrews wrote: > > It is a attack on HE. HE also provides stable user -> address > > mappings so you can do fine grained geo location based on HE IPv6 > >

Re: Netflix VPN detection - actual engineer needed

10577 > OTA Management LLC | Phone: 914-460-4039 > aim: matthewbhuff| Fax: 914-694-5669 > >> -Original Message- >> From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Scott Morizot >> Sent: Monday, June 6, 2016 10:50 AM >> To: Mark Tinka <

Re: Netflix VPN detection - actual engineer needed

> And they could easily redirect HE IPv6 addresses to a IPv4 only > service. This would satify both the content providers and the > customers. It's not like there tunneled traffic is IPv6 only as > there has to be a IPv4 endpoint for the tunnel. > > You can't argue that HE is too small to do

Re: Netflix VPN detection - actual engineer needed

On Mon, 06 Jun 2016 15:44:14 -0400, wrote: And if Netflix can't be bothered to consult rwhois for the ownership (which could be used for other use cases as well), they certainly aren't going to do *new* code as a one-off. Said by someone who's never written (r)whois

Re: Netflix VPN detection - actual engineer needed

On Mon, 06 Jun 2016 11:08:13 -0400, John Peach wrote: The whois information on the HE IPv6 address, does give the location. At least, it does on mine. It lists the location of the user's registration -- which could very well be a lie as they do nothing at all to

Re: Netflix VPN detection - actual engineer needed

On Sun, 05 Jun 2016 19:35:27 -0400, Mark Andrews wrote: It is a attack on HE. HE also provides stable user -> address mappings so you can do fine grained geo location based on HE IPv6 addresses. They may be "fine grained", but they are still lies. One's tunnel can be

Re: Netflix VPN detection - actual engineer needed

In message , Eric Kuhnke writes: > None of this is a problem with actual network engineering, HE's tunnels > work fine. It goes in the category of political/economic/contractual , not > "this is a technical problem we need to

Re: Netflix VPN detection - actual engineer needed

> 1. C-band teleport in Singapore with SingTel IPs, remote terminals in > Afghanistan. > > 2. Ku-band teleport in Germany with IP space in an Intelsat /20, remote > terminal on the roof of a US government diplomatic facility in > $DEVELOPING_COUNTRY > > 3. Teleports in Miami with IP space that

Re: Netflix VPN detection - actual engineer needed

Geolocation by IP is even funnier as an idea for those who have worked in network engineering for commercial, geostationary two-way satellite services... Some examples: 1. C-band teleport in Singapore with SingTel IPs, remote terminals in Afghanistan. 2. Ku-band teleport in Germany with IP

Re: Netflix VPN detection - actual engineer needed

On 2016-06-06 19:39, Christopher Morrow wrote: ​Doing any sort of 'authentication' or 'authorization' on src-IP is just .. broken.​ This. Netflix is pretending to have a capability (geolocation by src ip) that doesn't exist and there is collateral damage from the application of their

Re: Netflix VPN detection - actual engineer needed

None of this is a problem with actual network engineering, HE's tunnels work fine. It goes in the category of political/economic/contractual , not "this is a technical problem we need to solve". The problem exists with business/contractual relationship Netflix has with its content providers,

Re: Netflix VPN detection - actual engineer needed

On Mon, 06 Jun 2016 20:30:02 +0100, Aled Morris said: > Maybe HE's IPv6 tunnel packets could be flagged with a destination option > (extension header field) that records the end-user's IPv4 tunnel endpoint > so geolocation could be done in the "old fashioned" way on that address. > > Similar to

Re: Netflix VPN detection - actual engineer needed

On Mon, Jun 6, 2016 at 3:30 PM, Aled Morris wrote: > Maybe HE's IPv6 tunnel packets could be flagged with a destination option > (extension header field) that records the end-user's IPv4 tunnel endpoint > so geolocation could be done in the "old fashioned" way on that address. >

Re: Netflix VPN detection - actual engineer needed

It's obviously a nontrivial number otherwise why would Netflix block it? :) Aled Morris wrote: Maybe HE's IPv6 tunnel packets could be flagged with a destination option (extension header field) that records the end-user's IPv4 tunnel endpoint so geolocation could be done in the "old fashioned"

Re: Netflix VPN detection - actual engineer needed

Maybe HE's IPv6 tunnel packets could be flagged with a destination option (extension header field) that records the end-user's IPv4 tunnel endpoint so geolocation could be done in the "old fashioned" way on that address. Similar to the way that edns-client-subnet records the end user's address

Re: Netflix VPN detection - actual engineer needed

On Mon, Jun 6, 2016, at 13:09, Brandon Jackson wrote: > Looking up your tunnels block in ARIN will only show HE's Info. > > Using HE's rwhois http://rwhois.he.net/whois.php > > Shows the information provided by the tunnel user at time of signup or as > modified in account settings. > Ahh,

Re: Netflix VPN detection - actual engineer needed

> On Jun 5, 2016, at 16:45 , Damian Menscher wrote: > > On Sun, Jun 5, 2016 at 4:33 PM, Laszlo Hanyecz > wrote: > >> On 2016-06-05 22:48, Damian Menscher wrote: >> >>> >>> What *is* standard about them? My earliest

Re: Netflix VPN detection - actual engineer needed

On Mon, Jun 6, 2016, at 10:08, John Peach wrote: > The whois information on the HE IPv6 address, does give the location. > At least, it does on mine. > That's interesting. On mine it does not. It just shows HE's info. -- Mark Felder f...@feld.me

Re: Netflix VPN detection - actual engineer needed

> On Jun 5, 2016, at 15:48 , Damian Menscher wrote: > > On Sun, Jun 5, 2016 at 2:59 PM, Owen DeLong > wrote: > > On Jun 5, 2016, at 14:18 , Damian Menscher > > wrote: > > On Fri,

Re: Netflix VPN detection - actual engineer needed

No need to speculate some details are available ... http://www.michaelgeist.ca/2015/04/nobodys-perfect-leaked-contract-reveals-sony-requires-netflix-to-geo-block-but-acknowledges-technology-is-imperfect/ And thats just for a single content provider ... On Mon, Jun 6, 2016 at 11:55 AM, Livingood,

Re: Netflix VPN detection - actual engineer needed

> On Jun 6, 2016, at 8:21 AM, Tore Anderson wrote: > > * Spencer Ryan > >> As an addendum to this and what someone said earlier about the >> tunnels not being anonymous: From Netflix's perspective they are. Yes >> HE knows who controls which tunnel, but if Netflix went to HE and

Re: Netflix VPN detection - actual engineer needed

On 2016-06-06 15:21, Tore Anderson wrote: But Netflix shouldn't have any need to ask in the first place. Their customers need to log in to their own personal accounts in order to access any content, when they do Netflix can discover their addresses. Tore Hey there's an idea, how about they

Re: Netflix VPN detection - actual engineer needed

On 6/5/16, 7:11 PM, "NANOG on behalf of Christopher Morrow" wrote: >I dislike the IP folks as much as anyone, but :( flix has to make a >good-faith-effort or they'll lose content sources, I suspect. Perhaps so. And now that they are

Re: Netflix VPN detection - actual engineer needed

On Sun, Jun 5, 2016 at 10:51 PM, Jon Lewis wrote: > On Sun, 5 Jun 2016, Owen DeLong wrote: > >> What is non-standard about an HE tunnel? It conforms to the relevant RFCs >> and >> is a very common configuration widely deployed to many thousands of >> locations >> around the

Re: Netflix VPN detection - actual engineer needed

* Spencer Ryan > As an addendum to this and what someone said earlier about the > tunnels not being anonymous: From Netflix's perspective they are. Yes > HE knows who controls which tunnel, but if Netflix went to HE and > said "Tell me what user has x/48" HE would say "No". Thus, making >

RE: Netflix VPN detection - actual engineer needed

On Mon, 6 Jun 2016, Matthew Huff wrote: You can argue about the content provides business model all you want, but Netflix has to do what they are doing. They aren't blocking IPv6 users, they are blocking users that are using VPNs and/or tunnels since their currently is no practical way of

Re: Netflix VPN detection - actual engineer needed

The SB6141, while fine for now, is only an 8 downstream channel device. If you are buying one now I would recommend a a 16 or 24 channel device. Alternatively, wait (lease) a few months and buy a DOCSIS 3.1 modem in retail when they come out. Jason Livingood Comcast On 6/3/16, 11:42 PM,

RE: Netflix VPN detection - actual engineer needed

...@gmail.com] Sent: Monday, June 6, 2016 11:04 AM To: Matthew Huff <mh...@ox.com> Cc: Mark Tinka <mark.ti...@seacom.mu>; NANOG list <nanog@nanog.org> Subject: Re: Netflix VPN detection - actual engineer needed Nonsense. That is hardly their only option as many others have

Re: Netflix VPN detection - actual engineer needed

| Fax: 914-694-5669 > > > > > -Original Message- > > > From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Scott > Morizot > > > Sent: Monday, June 6, 2016 10:50 AM > > > To: Mark Tinka <mark.ti...@seacom.mu> > > > Cc: NANOG li

Re: Netflix VPN detection - actual engineer needed

10577 > > OTA Management LLC | Phone: 914-460-4039 > > aim: matthewbhuff| Fax: 914-694-5669 > > > > > -Original Message- > > > From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Scott > > > Morizot Sent: Monday, June 6, 2016 10:50

Re: Netflix VPN detection - actual engineer needed

On Sun, Jun 5, 2016, at 23:55, jim deleskie wrote: > Damian, I HIGHLY doubt regular folks are running into issues with this, I > suspect its not even geeks in general having issues, I suspect 80% plus of > those having issues spend most of their time complaining about something > related to v6 and

Re: Netflix VPN detection - actual engineer needed

On Sun, Jun 5, 2016, at 18:45, Damian Menscher wrote: > > Another question: what benefit does one get from having a HE tunnel > broker > connection? Is it just geek points, or is there a practical benefit too? > I can access all my equipment at home remotely without having to resort to Port

Re: Netflix VPN detection - actual engineer needed

On Fri, Jun 3, 2016, at 17:30, Naslund, Steve wrote: > > I guarantee you that Apple does not know where my Apple TV units or any > of my Sony TVs are because they are on hard Ethernet cables with WiFi > disabled so if they told the lawyers that, they lied. > I woud not be surprised if Apple

Re: Netflix VPN detection - actual engineer needed

On Sun, Jun 5, 2016, at 17:18, Matt Freitag wrote: > While it is damaging negative publicity it also makes sense. HE's tunnel > service amounts to a free VPN that happens to provide IPv6. I would love > for someone from HE to jump in and explain better how their tunnel works, > why it's been

Re: Netflix VPN detection - actual engineer needed

uff| Fax: 914-694-5669 > > > -Original Message- > > From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Scott Morizot > > Sent: Monday, June 6, 2016 10:50 AM > > To: Mark Tinka <mark.ti...@seacom.mu> > > Cc: NANOG list <nanog@nanog.or

Re: Netflix VPN detection - actual engineer needed

460-4039 > aim: matthewbhuff| Fax: 914-694-5669 > > > -Original Message- > > From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Scott Morizot > > Sent: Monday, June 6, 2016 10:50 AM > > To: Mark Tinka <mark.ti...@seacom.mu> > > Cc

RE: Netflix VPN detection - actual engineer needed

> -Original Message- > From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Scott Morizot > Sent: Monday, June 6, 2016 10:50 AM > To: Mark Tinka <mark.ti...@seacom.mu> > Cc: NANOG list <nanog@nanog.org> > Subject: Re: Netflix VPN detection - actual enginee

Re: Netflix VPN detection - actual engineer needed

I have Hulu Plus and Amazon Prime. The only thing I would miss from Netflix is their Marvel original series. And I can live with that. I can't live without my IPv6 enabled home network and Internet connection since that's an essential part of my job. (I'm the IPv6 transition technical lead for a

Re: Netflix VPN detection - actual engineer needed

On 6/Jun/16 01:45, Damian Menscher wrote: > > Who are these non-technical Netflix users who accidentally stumbled into > having a HE tunnel broker connection without their knowledge? I wasn't > aware this sort of thing could happen without user consent, and would like > to know if I'm wrong.

Re: Netflix VPN detection - actual engineer needed

On 6/Jun/16 00:48, Damian Menscher wrote: > What *is* standard about them? My earliest training as a sysadmin taught > me that any time you switch away from a default setting, you're venturing > into the unknown. Your config is no longer well-tested; you may experience > strange errors;

Re: Netflix VPN detection - actual engineer needed

On 6/Jun/16 00:18, Matt Freitag wrote: > While it is damaging negative publicity it also makes sense. HE's tunnel > service amounts to a free VPN that happens to provide IPv6. I would love > for someone from HE to jump in and explain better how their tunnel works, > why it's been blocked by

Re: Netflix VPN detection - actual engineer needed

On 5/Jun/16 23:18, Damian Menscher wrote: > This entire thread confuses me. Are there normal home users who are being > blocked from Netflix because their ISP forces them through a HE VPN? Or is > this massive thread just about a handful of geeks who think IPv6 is cool > and insist they be

Re: Netflix VPN detection - actual engineer needed

I've worked at my fair share of eyeball ISPs, and many of them used HE as one of their connections, On Mon, Jun 6, 2016 at 12:38 AM, joel jaeggli wrote: > On 6/5/16 6:23 PM, Josh Reynolds wrote: >> Uhm, what? Where do you think ISPs get their transit exactly? > > They buy from

Re: Netflix VPN detection - actual engineer needed

Fixed it for you > On Jun 5, 2016, at 10:38 PM, joel jaeggli wrote: > > > They buy from 2 or more wholesale transit providers and in general they > opportunistically bureaucratically peer, although scale helps a lot there.

Re: Netflix VPN detection - actual engineer needed

On 6/5/16 6:23 PM, Josh Reynolds wrote: > Uhm, what? Where do you think ISPs get their transit exactly? They buy from 2 or more wholesale transit providers and in general they opportunistically peer, although scale helps a lot there. > On Jun 5, 2016 8:17 PM, "joel jaeggli"

Re: Netflix VPN detection - actual engineer needed

In message , Jon Lewis write s: > On Sun, 5 Jun 2016, Owen DeLong wrote: > > > What is non-standard about an HE tunnel? It conforms to the relevant RFCs a > nd > > is a very common configuration widely deployed to many thousands of locatio > ns

Re: Netflix VPN detection - actual engineer needed

On Sun, 5 Jun 2016, Owen DeLong wrote: What is non-standard about an HE tunnel? It conforms to the relevant RFCs and is a very common configuration widely deployed to many thousands of locations around the internet. Itÿÿs not that Netflix happens to not work with these tunnels, the problem is

Re: HE tunnels, was Netflix VPN detection - actual engineer needed

>Another question: what benefit does one get from having a HE tunnel broker >connection? Is it just geek points, or is there a practical benefit too? It gets your network a reliable IPv6 connection when your own ISP doesn't support IPv6 yet. That's why I use them. And please skip the rant

Re: Netflix VPN detection - actual engineer needed

>What is non-standard about an HE tunnel? It conforms to the relevant RFCs and >is a very common configuration widely deployed to many thousands of locations >around the internet. Nothing whatsoever, but so what? >Most likely, these steps are being taken at the behest of their content

Re: Netflix VPN detection - actual engineer needed

Uhm, what? Where do you think ISPs get their transit exactly? On Jun 5, 2016 8:17 PM, "joel jaeggli" wrote: > HE's downstream cone does not include a whole lot of residential ISPs. > if you further exclude the ones that are multihomed you're left with a > pretty small subset.

Re: Netflix VPN detection - actual engineer needed

HE's downstream cone does not include a whole lot of residential ISPs. if you further exclude the ones that are multihomed you're left with a pretty small subset. that said they (HE) can be and are a valuable peer both in v4 and v6. Personally I wouldn't single home to anything that looks

Re: Netflix VPN detection - actual engineer needed

On Sun, Jun 5, 2016 at 8:15 PM, Laszlo Hanyecz wrote: > For P2P stuff it's a way to get around NAT - you can get inbound torrent > connections or host a shooting game match on your desktop behind the NAT > router. ​but to be fair, stun/ice/upnp has made all that work for

Re: Netflix VPN detection - actual engineer needed

On 2016-06-05 23:45, Damian Menscher wrote: Who are these non-technical Netflix users who accidentally stumbled into having a HE tunnel broker connection without their knowledge? I wasn't aware this sort of thing could happen without user consent, and would like to know if I'm wrong. Only

  1   2   3   >