go558a83nk

tested on my Mint VM. host CPU is an i7 4790 @ 3.6GHz. max theoretical is 798mbit/s. test took 4.009seconds. this is pretty cool. thanks for sharing.

already been discussed. it's not happening. why not run VPN from a router/gateway so that all devices behind said router go through the VPN tunnel?

1) Local ISPs wouldn't cover the range of possibilities concerning from where a user is connected. Users could be connected from anywhere around the world. 2) Even if an ISP said a user was connected to that VPN server they'd never be able to prove which user it was downloading a torrent because there are no logs on the server, there are tens of other users, and data is encrypted between the user and the VPN server.

The saying goes, "iron sharpens iron". A healthy community should have some friction with the intent being constructive criticism. The members of a healthy community should learn from eachother and teach eachother and be humble in doing so.

every server you attempt to connect to knows your IP. there's nothing amazing about netflix knowing your IP, whether it's the VPN server IP or your home IP.

8.666u 0.646s 0:09.33 99.6% 742+177k 0+0io 0pf+0w silly question but what is the time in seconds in this output from the test run? I see where it says 0.646s but the test took longer than that. If it's the 9.33 (that makes sense for how long it took to complete) then my max theoretical throughput is 343mbit/s. this in pfsense with AMD A6-7400K Radeon R5

you just didn't read the whole thread I guess. as has already been said by others, it doesn't work anymore. for a day or two routing netflix outside the VPN worked, now it doesn't.

it's best to just shut it off in your browser. search the forum more.

I can't understand what the problem is in this thread. The line about the "hack" ? Isn't that just some code that Air has written to get Eddie to work in a variety of conditions?

tunnelblick may not have the option to to edit routing. but don't bother anyway. read the whole thread.

if you can find a VPN provider that can still access netflix tell us in the proper forum section. But, I doubt one exists.

if that's the case then you should talk to them

just checked netflix again. indeed, they are blocking me even though I allow AS2906 & AS55095 outside the VPN. I'm using apple tv. Each attempt to play a video netflix creates a connection with a different amazonaws server which is probably meant to determine my IP once more. they probably assume I'm not allowing the whole amazonaws IP range outside the VPN too.

I did some searching. Best I could tell that router can't run as an openvpn cilent. It does support an openvpn server. But, maybe I missed something.

torrents work fine for me connected to a USA server. many of the public trackers work as well as about 176 DHT nodes. qbittorrent in a linux virtual machine running Eddie.

Staff at air told me all USA servers are down now for Netflix. No fix as yet. that's correct. what I wrote previously in this thread will no longer get netflix working. now you must basically use netflix without a VPN. it's being discussed in other netflix threads.

well, all I can say is it works for me. I didn't subtract any /24s

just try what's already been discussed in this thread.

could be that wifi network is blocking traffic to the German server IP range or if your config file didn't have resolved hosts they could be blocking DNS resolution of the server name.

thanks for looking. it shouldn't make a difference but I'm using pfsense and not Eddie. Yes, hopefully others can help work this out.

when it's "not working" can you still ping 8.8.8.8 ?

torrents have been working just fine for me no matter the port on USA servers. In a linux VM with qbittorrent. I don't use uTP.

I'm using a linux VM and qbittorrent and torrents are working just fine in the USA. doesn't matter what port I use. I don't use uTP.

just manually change the DNS back to automatic if you are not connected to VPN at the time. it should revert back to automatic (from 10.4.0.1) when Eddie disconnects but sometimes there's a hiccup.

I see what the problem is. I got my data for AS2906 from http://bgp.he.net/AS2906#_prefixes It seems to have a lot more prefixes than the whois method zhang presented. So, it could be that you just haven't routed all the ranges yet. From HE 23.246.0.0/18 23.246.2.0/24 23.246.3.0/24 23.246.4.0/24 23.246.5.0/24 23.246.6.0/24 23.246.7.0/24 23.246.8.0/24 23.246.9.0/24 23.246.10.0/24 23.246.11.0/24 23.246.12.0/24 23.246.13.0/24 23.246.14.0/24 23.246.15.0/24 23.246.16.0/24 23.246.17.0/24 23.246.18.0/24 23.246.20.0/24 23.246.22.0/24 23.246.23.0/24 23.246.24.0/24 23.246.25.0/24 23.246.26.0/24 23.246.27.0/24 23.246.28.0/22 23.246.28.0/24 23.246.29.0/24 23.246.30.0/24 23.246.31.0/24 23.246.32.0/20 23.246.36.0/24 23.246.37.0/24 23.246.38.0/24 23.246.39.0/24 23.246.40.0/24 23.246.41.0/24 23.246.42.0/24 23.246.44.0/24 23.246.45.0/24 23.246.46.0/24 23.246.47.0/24 23.246.48.0/24 23.246.49.0/24 23.246.50.0/24 23.246.51.0/24 23.246.54.0/24 23.246.55.0/24 23.246.56.0/24 23.246.57.0/24 23.246.58.0/24 23.246.59.0/24 23.246.62.0/24 23.246.63.0/24 37.77.184.0/24 37.77.185.0/24 37.77.186.0/24 37.77.187.0/24 37.77.188.0/24 37.77.189.0/24 37.77.190.0/24 37.77.191.0/24 45.57.0.0/17 45.57.0.0/24 45.57.1.0/24 45.57.2.0/24 45.57.3.0/24 45.57.4.0/24 45.57.5.0/24 45.57.6.0/24 45.57.12.0/24 45.57.13.0/24 64.120.128.0/17 66.197.128.0/17 108.175.32.0/24 108.175.33.0/24 108.175.34.0/24 108.175.35.0/24 108.175.38.0/24 108.175.39.0/24 108.175.40.0/24 108.175.41.0/24 108.175.42.0/24 108.175.43.0/24 108.175.44.0/24 108.175.46.0/24 108.175.47.0/24 185.2.222.0/24 185.2.223.0/24 185.9.188.0/24 192.173.64.0/20 192.173.80.0/20 192.173.96.0/20 192.173.112.0/20 198.38.96.0/24 198.38.97.0/24 198.38.98.0/24 198.38.99.0/24 198.38.102.0/23 198.38.102.0/24 198.38.108.0/24 198.38.109.0/24 198.38.110.0/24 198.38.111.0/24 198.38.112.0/24 198.38.113.0/24 198.38.114.0/24 198.38.115.0/24 198.38.116.0/24 198.38.117.0/24 198.38.118.0/24 198.38.119.0/24 198.38.120.0/24 198.38.121.0/24 198.38.122.0/24 198.38.123.0/24 198.38.124.0/24 198.38.125.0/24 198.45.48.0/23 198.45.48.0/24 198.45.49.0/24 198.45.50.0/24 198.45.52.0/24 198.45.53.0/24 198.45.54.0/24 198.45.55.0/24 198.45.56.0/24 198.45.57.0/24 198.45.61.0/24 198.45.62.0/24 198.45.63.0/24 208.75.79.0/24 From radb 23.246.0.0/18 23.246.15.0/24 23.246.20.0/24 23.246.28.0/24 23.246.29.0/24 23.246.30.0/24 23.246.31.0/24 37.77.184.0/21 37.77.184.0/23 37.77.186.0/23 37.77.188.0/23 45.57.0.0/17 64.120.128.0/17 66.197.128.0/17 69.53.224.0/19 108.175.32.0/20 108.175.47.0/24 185.2.220.0/22 185.2.220.0/24 185.2.221.0/24 185.9.188.0/22 192.173.64.0/18 198.38.116.0/24 198.38.117.0/24 198.38.118.0/24 198.38.119.0/24 198.38.120.0/24 198.38.121.0/24 198.38.96.0/19 198.45.48.0/20 208.75.76.0/22 208.75.76.0/24 208.75.77.0/24 208.75.78.0/24 208.75.79.0/24