SonicMetal15

Yes policy routing is what you need, where you have some traffic going out the tunnel and other traffic going out the default WAN interface. The way I have set this up is by first creating a host alias under Firewall, Aliases, IP tab, and then adding hosts one by one which are going to be the websites you want to access out the default WAN and not the VPN tunnel. Then create a firewall rule that resembles this: Action: Pass Interface: (whatever interface it is) Address Family: IPv4 Protocol: TCP/UDP Source: (the interface chosen above plus the word net) Destination: Single Host or Alias - Address: (type the name of the host alias group you created above listing the websites you want to access via default GW) Destination Port Range: From: (up to you) To: (up to you) Description: Policy routing through default WAN

Thank you for the advice. I will try that.

I just convinced my friend who lives down the street to sign up for AirVPN given my wonderful experience with it so far. His experience on the other hand, has been far from it. First, he uses the Eddie client on his host Windows 7 PC using the same cable ISP as I do, the only difference being that I don't use a client to connect to AirVPN but rather pfSense to establish the tunnel. My speeds have been consistent with the speed plan that I am paying for. However, his seems to drop to unbearably slow levels and he is on the same plan as I am. I went to his house to troubleshoot the issue and cannot figure it out. I have reset his router to default settings, ensuring no traffic shaping or firewall policies were in place. I have turned off his Windows firewall and uninstalled all anti-virus programs. I have even tried using the OpenVPN client but always the same result - load time for web pages are noticeably slow, his torrent download speeds drop from 6 MB/sec. (with VPN off) to always around 20-30 KB/sec. (with VPN on), almost as if it were capped. We have changed the buffer settings in preferences for Eddie to no avail. We have tried other VPN servers in North America also and at first upon connection the results are promising - the speed increases to what it should be, but then slowly and gradually over the course of 30 seconds it drops down to 20-30 KB/sec. again! I have searched this topic and others seem to lay blame to the ISP capping the speeds but I don't think this is the case here because I am using the same ISP as him with the same plan and most likely on the same node since I live down the street and I have NEVER had this happen to me, and I connect to the same AirVPN servers as him. Does anyone have any idea why this is happening? Am I not affected because I don't use the client to connect? Can the ISP somehow tell if one of us uses a client and therefore caps the speed? Why don't I experience such issues using pfSense?

I need help trying to set up this web server to be accessible from the internet. It sits behind a pfSense firewall on a private VLAN for DMZ purposes but is currently listening on port 80. I can access it just fine from any of my local networks behind the firewall but not from outside. I went to the AirVPN client area to set up the port forwarding and since I could not forward port 80 on the AirVPN interface, I went with a random port (let's say 22222) and chose 80 for the local port. This is where I'm having some trouble. Using pfSense, I set up a NAT for the AirVPN interface at port 22222 (the source) to forward to my webserver at port 80 (the destination). Then it automatically setup a firewall rule for allow that traffic to pass. Is that the right way to do it, when the AirVPN interface is listening at port 22222 to forward it to your local VPN IP at 80, which then gets forwarded again from that IP to your local webserver at port 80? That is essentially a double NAT that is taking place? It was pretty straight forward port forwarding a port that wasn't taken for my torrent client but this is a little more confusing. Also another issue: I changed the A record of the DNS for the company that I registered the domain name with.to point to my AirVPN public IP. It won't let me enter a customized port (such as 22222). Is that another reason why I cannot access my website outside my network? Is it therefore not possible to host a private website using AirVPN because you cannot forward port 80 since it's reserved without having to double NAT?

Yes, I am running a Squid Proxy Cache server on pfSense. So you think that's what's causing it? But why only that website and not the others? For security's sake though I will disable it, thank you.

So I followed this guide in setting up AirVPN with my pfSense box: https://airvpn.org/topic/17444-how-to-set-up-pfsense-23-for-airvpn/?do=findComment&comment=40144 Everything looked good - I was able to browse the internet and dnsleak.com reported only one leak (the AirVPN DNS server I was using). I went to a couple of websites that report your public IP address just to make sure, such as whatismyip.com and even google.com can do it too, and they all showed the VPN server IP...except for this site: whatismyipaddress.com That website actually reported my true public IP address when all the others didn't. How is that possible? Do you guys get the same results? Does this mean I didn't set this up properly? How secure is my VPN connection and does it have to do with the particular AirVPN server I chose to connect to? I will try a different server tomorrow and see if I get the same results.