Search the Community

I have a computer connected to AirVPN using openvpn. I forwarded a port into the "Client Area configurations" and if I check the port by click on "Test open" I receive "Open!" for both ipv4 and ipv6 protocols: my computer is listening the open port correctly on both IP protocol. If I use another computer connected to internet out of AirVPN and I check the open port using ipv4 protocol: nmap <ipv4_of_AirVPN_device> -sV -Pn -p <port_to_check> -4 I receive "open" but if check using ipv6 protocol: nmap <ipv6_of_AirVPN_device> -sV -Pn -p <port_to_check> -6 I receive "filtered". I also can't use the service listening on that port unless I force the use of the ipv4 protocol. What could be the problem? Why is my ip not correctly forwarded despite the AirVPN check being successful?

Hi I am looking to forward one of my ports through TCP on IPv4. I have connected to the vpn (tried both udp and tvp ports . Then setup Port Forwarding on the ports section. (BEWARE: My ISP has CGNAT so there's double a NAT that I have to punch through) Before connecting NetStat output is: Active Connections Proto Local Address Foreign Address State TCP 127.0.0.1:2657 view-localhost:2658 ESTABLISHED TCP 127.0.0.1:2658 view-localhost:2657 ESTABLISHED TCP 127.0.0.1:2659 view-localhost:2660 ESTABLISHED TCP 127.0.0.1:2660 view-localhost:2659 ESTABLISHED TCP 127.0.0.1:9349 view-localhost:11080 ESTABLISHED TCP 127.0.0.1:11080 view-localhost:9349 ESTABLISHED TCP 127.0.0.1:49736 view-localhost:65001 ESTABLISHED TCP 127.0.0.1:49740 view-localhost:49753 ESTABLISHED TCP 127.0.0.1:49753 view-localhost:49740 ESTABLISHED TCP 127.0.0.1:65001 view-localhost:49736 ESTABLISHED TCP 192.168.29.205:1029 eu-de01:50519 ESTABLISHED TCP 192.168.29.205:1294 20.197.71.89:https ESTABLISHED TCP 192.168.29.205:11333 20.54.37.64:https ESTABLISHED TCP 192.168.29.205:11343 172.67.202.182:https ESTABLISHED TCP 192.168.29.205:11368 ec2-15-207-57-185:https ESTABLISHED TCP [2405:201:5003:40a7:3124:eb36:19c:e412]:10941 [2600:9000:2075:2000:a:15d0:77c0:93a1]:https ESTABLISHED TCP [2405:201:5003:40a7:3124:eb36:19c:e412]:11346 upload-lb:https ESTABLISHED TCP [2405:201:5003:40a7:3124:eb36:19c:e412]:11347 airvpn:https ESTABLISHED TCP [2405:201:5003:40a7:3124:eb36:19c:e412]:11353 [2606:4700::6812:126e]:https ESTABLISHED TCP [2405:201:5003:40a7:3124:eb36:19c:e412]:11354 [2a00:c6c0:0:154:4:d8aa:b4e6:c89f]:https ESTABLISHED TCP [2405:201:5003:40a7:3124:eb36:19c:e412]:11355 del12s08-in-x04:https ESTABLISHED After connecting to vpn output of netstat is: Active Connections Proto Local Address Foreign Address State TCP 10.16.55.31:11421 upload-lb:https ESTABLISHED TCP 10.16.55.31:11451 37.218.245.111:https ESTABLISHED TCP 10.16.55.31:11593 104.18.11.207:https ESTABLISHED TCP 10.16.55.31:11595 104.18.11.207:https TIME_WAIT TCP 10.16.55.31:11600 172.67.214.69:https TIME_WAIT TCP 10.16.55.31:11603 104.16.126.175:https ESTABLISHED TCP 10.16.55.31:11604 104.16.87.20:https ESTABLISHED TCP 10.16.55.31:11606 104.16.87.20:https TIME_WAIT TCP 10.16.55.31:11608 104.16.19.94:https TIME_WAIT TCP 10.16.55.31:11609 ams15s40-in-f3:https ESTABLISHED TCP 10.16.55.31:11610 ams15s41-in-f14:https TIME_WAIT TCP 10.16.55.31:11614 204.79.197.219:https ESTABLISHED TCP 10.16.55.31:11623 ec2-52-202-215-126:http TIME_WAIT TCP 10.16.55.31:11627 104.16.126.175:https ESTABLISHED TCP 10.16.55.31:11628 104.16.126.175:https TIME_WAIT TCP 10.16.55.31:11629 104.16.126.175:https ESTABLISHED TCP 10.16.55.31:11630 104.16.126.175:https ESTABLISHED TCP 10.16.55.31:11631 1:https ESTABLISHED TCP 10.16.55.31:11632 1:https ESTABLISHED TCP 10.16.55.31:11637 ec2-15-207-57-185:https ESTABLISHED TCP 10.16.55.31:11638 ec2-15-207-57-185:https ESTABLISHED TCP 127.0.0.1:2657 view-localhost:2658 ESTABLISHED TCP 127.0.0.1:2658 view-localhost:2657 ESTABLISHED TCP 127.0.0.1:2659 view-localhost:2660 ESTABLISHED TCP 127.0.0.1:2660 view-localhost:2659 ESTABLISHED TCP 127.0.0.1:9349 view-localhost:11080 ESTABLISHED TCP 127.0.0.1:11080 view-localhost:9349 ESTABLISHED TCP 127.0.0.1:49736 view-localhost:65001 ESTABLISHED TCP 127.0.0.1:49740 view-localhost:49753 ESTABLISHED TCP 127.0.0.1:49753 view-localhost:49740 ESTABLISHED TCP 127.0.0.1:65001 view-localhost:49736 ESTABLISHED TCP 192.168.29.205:1029 eu-de01:50519 ESTABLISHED TCP 192.168.29.205:1294 20.197.71.89:https ESTABLISHED TCP 192.168.29.205:11393 213.152.186.42:https ESTABLISHED TCP 192.168.29.205:11633 20.199.120.182:https ESTABLISHED TCP [2405:201:5003:40a7:3124:eb36:19c:e412]:11396 airvpn:https ESTABLISHED However Port Forwarding over tcp does not work ?

Hi everyone, I purchased AirVPN recently to use it with a p2p file sharing application SoulSeek. I'm very new to this stuff and really in need of some guidance. I was able to add my 2 ports in the "client area" section of the AirVPN website. Then I ran a TCP test check and recieved the message, "Not reachable on server IP over the external port #####, tcp protocol. Error 110 - connection timed out". I'm not into torrenting, I just want to use this VPN for Soulseek. I haven't done anything to my router since I'm not comfortable messing with the settings on it. Also when I check the ports on SoulSeek it also says the ports are closed. Any guidance is most welcomed! -Nub

I have AirVPN all set up and running great on a pf Sense router that my home network sits behind. I am trying to get port forwarding set up for torrenting on a server running Windows Server 2016. As far as I can tell everything is set up exactly as it should be but I just can't get it to work. I am connected to Metallah. I have created the forwarded port on the AirVPN site. I have the port open in my Windows firewall. I have the port forwarded in pfSense. I have my torrent client configured to listen on the port I've set up in AirVPN and pfSense and I have my torrent client running with an active torrent trying to download. I have verified that the port is open and can be connected to on my LAN. I have tried 2 different torrent clients (qBittorrent and Deluge) as well as a port listener tool that simply opens any port you specify on TCP or UDP and just listens for connections. When I check the port on the AirVPN site I get error 110 timeout. I've also tried other sites and tools for performing external tests on that port and they all indicate that the port is not open. I have tried creating several new ports on AirVPN (at least 4) and tested on multiple computers on my network all with new corresponding NAT rules in pfSense. No matter what I do I can't get port forwarding to work and I'm at my wits end. I hope someone can help me figure this out. Here is a screenshot of my NAT rule in pfSense.

I've lately had increasing amount of issues with AirVPN port forwarding for torrents. Fully working system stopped working. I have Windows firewall blocking qbittorrent, unless traffic goes through VPN. I have set port for incoming traffic to qbittorrent. Lately this has stopped working. I have fixed it previously by removing forwarded port from AirVPN, doing the same port forward again and maybe switching server - So the issue is not with qbittorent or windows firewall rules. Today resetting port forward and switching server has not helped. I confirm VPN connection with IPMagnet or similar service and haven't managed to get working connection yet. I use AirVPN maybe few times a month and there can be weeks without using it. Is AirVPN losing my port forwarding settings, is this server related issue or what gives? EDIT: Ok, got it working again. I had to restart Eddie. Then I tried to switch server and had to restart again to get it working. It's quite a hassle to get things working with AirVNP.

Hi everyone, I'm not a network buff and only understand the basic concept of port forwarding. · How does port forwarding in connection with a VPN work? Does it come on top of the local configuration, instead of it (because of some tunneling or what), or does it have no effect..? My problem is: I cannot get a certain port open (52070 TCP or something), neither with nor without VPN. I explicitly opened the port in Windows (10) Firewall, and configured my Wi-Fi router accordingly, to no avail. I tested the port by going to a website. With my limited knowledge, the only possible explanation for the closed port to me is that the Wi-Fi router does not support port forwarding to a certain (fixed) local IP, but only based on a MAC address. It was suggested to me I do the former (whatever the possible advantage is). What should I do? What can I check to find out what's wrong? And how does VPN affect all this? Thank you.

Hi, After I've forwarded the right port in AirVPN client area and put the right settings in qBittorrent, I finally get great speeds while connected to the VPN service. However, the speeds (for torrents), seem to fluctuate heavily between 0 and 200Mbit (my max speed). I have the feeling it is because of some setting or limit somewhere that high speeds cannot be sustained. Here is a screenshot of the Eddie speed: More info: - Using network lock - Using OS X 10.12.6 - Using an SSD - Using Asus AC-3200 router - Only using the utun3 network interface in qBittorrent - Used settings described here for qBittorrent - Disabled firewall on router - Looked for any settings in my router that might impede sustained speed like ICMP flood detection but cannot find those - Using port forwarding in client area Is this normal behaviour? I don't really mind it for the time being, as speed is much faster than before, however maybe I'm missing a setting that could prevent this?

Hello. Can I have some help please. I'm trying to Port forwarding the following ports for a better multiplayer steam : UDP 27000 to 27015 inclusive (Game client traffic) UDP 27015 to 27030 inclusive (Typically Matchmaking and HLTV) TCP 27014 to 27050 inclusive (Steam downloads) UDP 27031 and 27036 (incoming, for In-Home Streaming) TCP 27036 and 27037 (incoming, for In-Home Streaming) UDP 4380 TCP 27015 (SRCDS Rcon port) UDP 3478 (Outbound) UDP 4379 (Outbound) UDP 4380 (Outbound) and for rocket league: 7000 – 9000 UDP (For Game Servers) 80 TCP (HTTP Connections) 443 TCP (HTTPS Connections) What I sohuld do in the client area-->forwarded ports section? Thanks.

Hello, I am using an Asus RT-AC87U with AirVPN. I have a couple of problems. I wish to forward multiple :80 ports to multiple addresses, but I believe that is not directly possible. I can create the IPTABLES rules, but I can only open port 80 to the VPN if I am correct? Is there a way I can open multiple :80 ports on multiple local IPs? It doesn't really matter if I need different or new hardware. Second, my Asus router seems very instable. The speeds are slow (around 1.5mbps where I can get 300mbps without VPN), but that isn't the real problem. Every week or so, the VPN client disables itself without further notice, and I can't enable it manually, it simply never starts. The logs state nothing. The only option I found so far is to fully reset the router and setup everything from stock again, until it breaks again. Am I maybe better of using a custom (server-grade) box or router running PfSense (or similar)? Also keeping my first quesion in mind.

Hey, I am new to AirVPN and intend to use it mainly for P2P filesharing. Configuration is: Eddie running on Linux Mint (VPN works just fine!) Port fowarding enabled on Client Web Interface Port No. set on my qTorrent as port Looks like I am not getting through my 7390 box though. No connection in qTorrent. Test on AirVPN Client page also not working. Any idea how to get this going? Thx and BR, Mitch

Hi! I am trying to forward a port on ddns. I have finally gotten airVPN working and my goal is to forward a port on a ddns. However, i went to forwarded ports and left the fields blank for both local and public ports, which lead to a random port. You can see the information in the following image: ATTACHMENT When i do the TCP test, it says "Not reachable on server ip over the external port 13096 tcp protocol error 111 connection refused" I have also made a python script which is checking ports and I have set it to check if connection can be established to "osconnection.airdns.prg:13096" and "http://osconnection.airdns.prg:13096" but it says there is no connection at all. Does anyone know how I could fix this? I have had some trouble with AirVPN lately.... :/ Thanks! Cheers, Me

Hi, the port forwarding feature caught my attention but I have some doubts. I think I'm completely lost with this. Let's say I have a server running Linux, basically serving a webpage, I have port forwarding enabled on my router so anyone with my external IP address can connect to it. Okay now let's say I don't want to give out my real IP address, if I understand how the VPN port forwarding feature works, I could use a VPN server to serve that webpage and hide my real IP address (I'd have to deactivate port forwarding on my router and configure it with AirVPN) Is that right? So I connect that Linux server through OpenVPN to an AirVPN's server with port forwarding enabled. For a VPN server, which is a single IP address, there could be maybe 50 persons connected to it, we're sharing the server somehow, but those persons could also enable port forwarding, so, what are the limits/ranges? Two different persons on the same server can't port forward a same port? How does it work? Thanks

In the past I could run the TCP Test to check my Port Forwarding. Now I missed the Check button! Thanks for your help ;-)

I have a couple of questions regarding port forwarding. One - I saw this line - but it isn't explained in the FAQ page: Watch for warnings from our security check: a red token implies that your anonymity layer may be lowered or broken by a malicious adversary. What does this mean exactly? Where would I find this red token and what exactly could it mean? Also - is there any additional setup required after forwarding a specific port, or will this be automatic whenever connecting through the client? And lastly - for Dynamic DNS - is there a specific naming convention I should be following for this when coming up with a name? Thanks in advance, I know this is several questions. KR

I seem to be unable to get port forwarding working. Well, on AirVPN's side it seems to be working but locally the connection is denied because of a "martian source": IPv4: martian source 192.168.1.2 from 2.3.4.5, on dev eth0 eth0 is my local interface behind a regular residential NAT (though in the DMZ). 2.3.4.5 is the ip I'm trying to connect from. Is there any way to solve this? Additionally, I would like to be able to connect to my wan ip directly, but that doesn't seem to be possible either. This is my routing table: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 10.4.0.1 128.0.0.0 UG 0 0 0 tun0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 10.4.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tun0 128.0.0.0 10.4.0.1 128.0.0.0 UG 0 0 0 tun0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 213.152.161.x 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0 I've just generated a standard ovpn file and ran openvpn file.opvn in the console as per instructions. Any help would be appreciated!

Hi there, I want to open a specific port [ no matter which one it is ] as my ISP is blocking all of them! But when I connect to AirVPN servers ( I already port forwarded from the client area as in the screenshot ). But when using CanYouSeeMe.org it appears that no port is open. But I used "http://www.ipfingerprints.com/portscan.php" and it seems that port number 88 is open. So, what's the deal? Will I be able to bypass the ISP block?

All of my forwarded ports are blocked I forward new port, and trying to check it in browser and getting: Not reachable on server IP over the external port 9934, tcp protocol. Error : 111 - Connection refused Same error on other ports system is: Windows 7 32 bit, under Hyper-V , Firewall off . openvpn Any idea how to fix it?