go558a83nk

this would have the same problem as using your own VPS as a VPN server - it's got your info all over it.

It's easy to know you're using a VPN by your IP address if they've done their homework and logged all exit IP addresses of known VPN providers. maybe Amazon are in the midst of blocking VPN providers but the last time I tried Amazon video over VPN it worked. That was a few weeks ago.

not only that but in my experience NAT acceleration would "leak" by allowing connections made prior to the VPN connection to continue to exist instead of forcing everything through the VPN tunnel.

are you using merlin's build?

OK, fixed the problem! Specifying outgoing gateway on the general settings page now works. what i had to do was change the NAT rules for localhost outgoing to VPN and WAN to be "this firewall", not 127.0.0.0/8. Will this cause an additional problem somehow?

I'll look into this. Thanks! Edit: tested and doesn't work. Rebooted just to make sure. But, getting DNS requests out the WAN still. Edit #2: since I'm looking at routes I realize now that specifying a gateway on the general settings page adds a static route, same as the system_routes page. But, it seems that Unbound ignores it. I have made sure that my NAT settings allow 127.0.0.0/8 to access the VPN tunnel. But, still, no luck.

Sorry, I forgot to mention that I've tried specifying the outgoing gateway on the general setup page and it's ignored when using Unbound in forwarding mode. I can test by connecting to a far away VPN server and testing for DNS "leaks". The servers that are shown are both local and near the VPN server. This is due to me having to allow Unbound to use the WAN for outgoing in the Unbound settings. From what I've read the outgoing gateway is only obeyed when not in forwarding mode. But, as I wrote previously, that presents other problems.

pfsense_fan, how would you setup DNS if you had some devices routed to WAN, other devices through VPN? My setup: 1) all regular devices on my network have static leases 2) I have some devices routed to WAN 3) I changed the DNS forwarding rule that prevents alternate DNS to allow those WAN routed devices to use whatever DNS 4) Unbound was still only allowed the VPN interface for outgoing requests. There wasn't a problem until recently. Now my streaming TV service (Vue) is really picky about things it seems. It won't work unless I allow Unbound outgoing WAN as well. I assume the IP address querying DNS must match my WAN address? This poses a problem for me because I want my VPN devices to also use public DNS but make sure the requests go through the VPN tunnel. I like public DNS because I get geo-optimized content and they are faster. But if I went with these settings my VPN devices would be doing DNS requests out the WAN and VPN. So, I've had to resort to using Air DNS to get things working properly. I use AirDNS in the general settings page, and put in public DNS in the static lease settings of the WAN routed devices. Things work, but I'd like to be able to use public DNS for everything, just out the respective interfaces. I've tried using resolver mode (unticking forwarding mode in unbound settings) but this seems to force the use of the VPN DNS and ISP DNS and ignores my settings on the general setup page. I've tried using the forwarder (dnsmasq). It obeys my DNS settings on the general settings page but other problems cropped up for some reason - Vue stopped working again.

how are you controlling DNS usage per interface? Just curious since I use pfsense too. Do WAN interface devices also use Air DNS? Air DNS is slower than huge corporate DNS, I can testify to that. Maybe that's the slowness you're seeing?

if latency is poor then choose a closer server. latency has nothing to do with the server but with your route to the server.

have you rebooted your computer?

Kind regards interesting. PIA have a win-win scenario. If their audit finds problems - they look like heroes not only because they found problems but because they are probably still using some ancient hacked version of openvpn that they can claim is SAFE!. If their audit doesn't find problems they still take credit in marketing for the wonderful work they've done.

I can't find anything either. But, I do see that M247 was bought by Metronet UK in October.

of course. I can't wait for the release of the new software which should be better about this problem.

Okay, thanks for letting me know, I should not worry. no, that's not the place to insert verb 4. Sorry, like this ? http://imgur.com/a/jBmAz If so : http://pastebin.com/SMB2N9nF two thoughts. what type of internet connection do you have? cable, fiber, DSL? try putting "mssfix 0" in the same place as you put "verb 4" and see if you still get the errors.

no, that's not the place to insert verb 4.

arjanvirdi, thanks. but, that doesn't have all the info I was looking for due to the default verbosity setting of the log. if you can insert "verb 4" (without the quote marks) into the custom directives field in advanced preferences/settings that should do it.

arjanvirdi, you should post here a log that shows the start up of the AirVPN client until connection to a server.

I'd love to see your evidence that they are owned by 3rd parties.

https://airvpn.org/topic/20481-suggestion-airvpn-ipv6-support/?hl=ipv6

I run into the same problem every evening - the route to the VPN server is overloaded but other routes are just fine. For me it's cogent's peering/transit with comcast.

Online Members: 13193 - BW: 44135 Mbit/s it's blowing up!

Online Members: 12987 - BW: 43181 Mbit/s even more now!

wow, 12885 users online as I write this.

is this correct? good idea to make an alias. looks correct to me.