go558a83nk

https://airvpn.org/topic/19348-what-does-airvpn-has-to-do-with-amazon/?hl=amazon

I'm not so sure. if my old asus AC68 could do 50mbit then a late generation CPU at 1.7ghz may be able to do it. but, I admit I had the same thought as you at first.

I assume you have allow local/lan switched on?

oh sweet. and those two dallas servers are at two different datacenters, both different from the other we already had. very nice.

it should work just the same. make sure you're using AirVPN DNS on the router as that is required for what you're wanting to do.

another user, posts on page 10 of this thread, found that the squid proxy was causing "leaks". so, you might begin there.

yeah, I had to laugh when I read that. I hope the free, horrible quality, tv is worth it to them.

then you should be more worried about your ISP than AirVPN.

They can't anyway assuming all those sites use TLS (https).

I think this is the 2nd or 3rd time somebody has asked this. I'm no expert by any means and I figured it out myself by just looking around and posting on the pfsense forums. I'll write up something here for using an SSL tunnel. SSH doesn't require stunnel but may require installing something like bash. The other steps and actions are very similar. You must install stunnel from the freebsd repo with a small workaround It's recommended to install nano and screen from the pfsense repo Start by browsing to https://pkg.freebsd.org/FreeBSD:10:amd64/latest/All/ This is for 64bit systems, which I assume all are these days. Find stunnel, and copy the link to it. Open an SSH session to your pfsense machine, select 8 for the shell command line. I use putty for this. https://the.earth.li/~sgtatham/putty/latest/x86/putty.exe run it and put in the ip address of your pfsense machine e.g. 192.168.1.1 with connection type SSH. Via your SSH session find or create a directory on the pfsense machine to which to download stunnel use fetch to download stunnel from the SSH prompt, like this - fetch https://pkg.freebsd.org/FreeBSD:10:amd64/latest/All/stunnel-5.40,1.txz use pkg to install stunnel - pkg install stunnel-5.40,1.txz use pkg to install nano - pkg install nano use pkg to install screen - pkg install screen exit out of the shell session by typing exit at the command prompt re-enter the shell session by selection option 8 download the config files you need from the AirVPN config generator page with your web browser. Then we will upload them to the pfsense machine via the web GUI interface. In the pfsense web GUI go to diagnostics>command prompt In the upload file section upload the *.ssl files you need, for each server you may want to use. And upload a stunnel.crt file. If you've downloaded configs for several servers you may have many stunnel.crt files but you only need to upload one. They're all the same. Via the SSH session command line move those files you've uploaded to the pfsense machine to a permanent location. Right now they're in the temp folder as the web GUI told you. This step is not necessary but should help with performance. I edit the .ssl files to use the least CPU intensive TLS 1.2 cipher. By default it'll use a stronger cipher but this isn't the real security later, openvpn is. This is just meant to defeat DPI. Since your machine will be crunching SSL for stunnel and openvpn, choosing a weaker cipher here will save you some clock cycles. In the permanent directory to which you've moved the .ssl and stunnel.crt files use nano to edit... e.g. nano AirVPN_the_server_you_chose.ssl under the line "options = NO_SSLv2" paste another line (no quotes) "ciphers = DHE-RSA-AES128-SHA256" type ctrl+o to save the changes. type ctrl+x to exit out of nano run stunnel using screen so that it runs in the background. like this - screen -dmS tunnel stunnel AirVPN_the_server_you_chose.ssl the options -dmS are important, and so is the letter case. "tunnel" is the name of the screen session, you can call that whatever you want. Look via your web GUI of the pfense machine at Status>system logs to see that stunnel is running properly. If it is, then proceed to editing your openvpn client by going to vpn>openvpn>clients and editing your AirVPN client so that it goes through stunnel. The edits you must make to the openvpn client are: protocol must be TCP, interface must be localhost, server must be 127.0.0.1, server port must be 1413, and you must add to custom options from the corresponding .ovpn file (same server as the .ssl file you started with stunnel) the line "route server_IP_address 255.255.255.255 net_gateway" (without quotes). Just open the .ovpn file for the server you chose with wordpad to copy and paste the line. If "explicit-exit-notify x" is in your custom options remove it as that option won't work with a TCP tunnel. click save to save the changes to the openvpn client and it should connect. Again you can look in system logs to see more stunnel actions, and look at your openvpn status and logs, all via the web GUI.

I get the same speed via any TCP (that includes SSL) tunnel to the dallas servers - only about 10mbit/s. It's either my ISP or the cogent routers that are traversed.

when sorting by speed it seems that USA residents will always be shown Canadian servers as "fastest". Just test several cities and see which works best for you.

Sorry, what I meant was, I used to use Private Internet Access and you could just connect and disconnect whenever you wanted, depending on whether you wanted to use the vpn or just surf normally. I can't figure out what to do now that I have installed airvpn_windows8_x64_installer. I use windows 10 but I understand that airvpn_windows8_x64_installer is ok to download onto windows 10 operating systems. Hi, sorry it's all double dutch to me, what is Eddie the client please? I downloaded airvpn_windows8_x64_installer I bought the three day premium for one euro. I tried to follow the instructions on what continent to surf from and whether I wanted TCP or UDP (I don't know what those are) thanks in advance. a new version of the AirVPN software was just released today. you might find it more user friendly.

If you're brainstorming this I'm guessing it's not possible to implement this by connecting to a certain port/s on the current servers? That would be way too easy.

Yep, the linux page is nice and I added the repo to my Mint setup. Maybe it's obvious to those with more experience with linux but I had to actually add the repo in the additional repos section of software sources, not the PPA section. When I attempted to add it as a PPA I was told that it didn't support xenial. But, I updated from 2.11.11 to 2.11.15 via the update manager so it seems to be working.

how did this thread get so off topic?

keep that in mind. even though a lot of posts in the forum are complaints over things not working there are a lot of users who are probably having no problems.

Online Members: 14007 - BW: 44861 Mbit/s 14000!!

I ran an AC68 for years with merlin asus firmware with zero problems connected to VPN 24/7. The only drawback was the speed limitation on openvpn imposed by the relatively weak CPU.

https://airvpn.org/topic/9270-how-to-forward-ports-in-dd-wrt-tomato-with-iptables/?hl=%2Bport+%2Bforward+%2Bdd-wrt

Not for me. Go into the addon's settings and check if the addon's main feature and the option beneath it, the one "recommended for privacy", are enabled. If yes, the problem is related to something else. yes, it's that setting that breaks the vertical scroll bar for me. also breaks some pfense web configurator things - the logon page fields for username and password are gone and the ability to expand text fields to see more by clicking and dragging is broken. if nobody else has this problem then I suppose it's a combination with something else that's relatively unique to me.

began using this when I saw it posted here. is it just me or does enabling blocking of chrome:// URIs break things? for me it removes the vertical scroll bar.

if you followed the guide exactly it should not even be possible for your LAN devices to reach the WAN gateway. Well, I thought so too and I think that I followed the guide to the point. Any suggestion on where I could have missed somethting? My first thought was that the PRIVATE NETWORKS could apply and might route my 192 /24 network through to the 10 /24 network. After removing the RFC1918 rules there was no change. A few days ago I had to add the SMTP port to the WAN PORTS, so I could send mail. The connection attempts to the SMTP got caught, but why do the http attempts not get caught or routed properly? sorry, I won't be much help. my setup never followed the guide exactly and has strayed even further from it in time.

if you followed the guide exactly it should not even be possible for your LAN devices to reach the WAN gateway.

AirVPN has a history of running this forum like it's their own. It is, after all. I've been very angry about the same thing before but I do believe it's within their right to do so. I just wish they were more transparent about it. What thread was it?