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: rfc 1812 third party address on traceroute

> I'm assuming you'd like this behavior on EdgeOS changed? no, the opposite. j & c got it right. microtik did not. vyatta seems to have. randy

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: rfc 1812 third party address on traceroute

I'm assuming you'd like this behavior on EdgeOS changed? I know a guy... On Jun 5, 2016 8:41 PM, "Randy Bush" wrote: > > is anyone seeing the dreaded rfc1812 behavior in a citable fashion? how > > common is it? > > we verified that the juniper and cisco platforms we tested

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: rfc 1812 third party address on traceroute

> is anyone seeing the dreaded rfc1812 behavior in a citable fashion? how > common is it? we verified that the juniper and cisco platforms we tested replied with the source address being the ingress interface. this is, imiho, good. a kind soul actually sent citable tests > At least my

Re: IPv6 is better than ipv4

i just want my mtv. and the normal commercials are bad enough.

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

Re: Netflix VPN detection - actual engineer needed

In message

Re: Netflix VPN detection - actual engineer needed

In message , Spencer Ryan writes: > I'm unaware of any US based user who gets native dual stack from their ISP > having issues. Netflix is blocking anonymous VPNs based on their content > providers requests. HE'S tunnel broker

Re: 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? We used them to use our own (ARIN) IP space before we had connections in all sites that we could BGP to the carriers, this allowed us to avoid

Re: Netflix VPN detection - actual engineer needed

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 training as a sysadmin taught >> me that any time you switch away from a default setting, you're venturing >> into the

Re: Netflix VPN detection - actual engineer needed

I'm unaware of any US based user who gets native dual stack from their ISP having issues. Netflix is blocking anonymous VPNs based on their content providers requests. HE'S tunnel broker is effectively that. On Jun 5, 2016 7:34 PM, "Laszlo Hanyecz" wrote: > > > On 2016-06-05

Re: Netflix VPN detection - actual engineer needed

In message , Damian Menscher writes: > On Sun, Jun 5, 2016 at 2:59 PM, Owen DeLong wrote: > > > > > On Jun 5, 2016, at 14:18 , Damian Menscher wrote: > > > On Fri, Jun 3, 2016 at 4:43

Re: Netflix VPN detection - actual engineer needed

On 2016-06-05 22: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; nobody

Re: Netflix VPN detection - actual engineer needed

On Sun, Jun 5, 2016 at 6:48 PM, Damian Menscher wrote: > I suggest you focus your efforts on bringing native IPv6 to the masses, not > criticizing service providers for defending themselves against abuse, just > because that abuse happens to be over a network (HE tunnel

Re: Netflix VPN detection - actual engineer needed

> On Jun 5, 2016, at 15: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

Re: Netflix VPN detection - actual engineer needed

On Sun, Jun 5, 2016 at 2:59 PM, Owen DeLong wrote: > > > On Jun 5, 2016, at 14:18 , Damian Menscher wrote: > > On Fri, Jun 3, 2016 at 4:43 PM, Baldur Norddahl < > baldur.nordd...@gmail.com> wrote: > >> Den 4. jun. 2016 01.26 skrev "Cryptographrix"

Re: Netflix VPN detection - actual engineer needed

On 2016-06-05 21: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 allowed

Re: Netflix VPN detection - actual engineer needed

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 Netflix, and what (if anything) they are doing to

Re: Netflix VPN detection - actual engineer needed

> On Jun 5, 2016, at 14:18 , Damian Menscher wrote: > > On Fri, Jun 3, 2016 at 4:43 PM, Baldur Norddahl > wrote: > >> Den 4. jun. 2016 01.26 skrev "Cryptographrix" : >>> >>> The information I'm getting from Netflix

Re: Netflix VPN detection - actual engineer needed

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 the rest of the geeks not loving them/it enough. -jim On

Re: Netflix VPN detection - actual engineer needed

On Fri, Jun 3, 2016 at 4:43 PM, Baldur Norddahl wrote: > Den 4. jun. 2016 01.26 skrev "Cryptographrix" : > > > > The information I'm getting from Netflix support now is explicitly > telling > > me to turn off IPv6 - someone might want to stop

Re: ISP License in the USA?

> On Jun 5, 2016, at 11:31 AM, Ryan Finnesey wrote: > > Would you mind sharing some of the telecommunications focused law firms? I > am about to start a company that is going back into the CLEC/ISP/VoIP > Business and I am going to have to establish relationships with a

Re: ISP License in the USA?

http://www.commlawgroup.com/#hashslider1 or Kris Tomey 's Info:- > Law Office > 1725 I Street, NW, Suite 300 > Washington, DC 20006 > > Phone: 202.250.3413 > Fax: 202.517.9175 > k...@lokt.net > > LoKT Consulting > 1425 Leimert Blvd., Suite 404 > Oakland, CA 94602 > > Phone: 510.285.8010 >

Re: ISP License in the USA?

A couple of places to start: Baller Stokes & Lide, P.C. (www.baller.com) http://www.bbklaw.com (which absorbed Miller & Van Eaton a few years back) They both have practices that focus on telecom from a municipal point of view (municipal broadband, right-of-way issues, cable franchises, and

RE: ISP License in the USA?

Would you mind sharing some of the telecommunications focused law firms? I am about to start a company that is going back into the CLEC/ISP/VoIP Business and I am going to have to establish relationships with a few law firms. -Original Message- From: NANOG

ERPS/G.8032 interoperability

Hi all, Is there any study on ERPS/G.8032 interoperability between different equipment manufacturer ? Denis