Search the Community

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 ?

Hello, I have a couple of questions regarding AirVPN's port forwarding/DDNS service and the "new" multiple Device keys per user feature: From your "What is Dynamic DNS" section I can read: When a Premium member connects to an Air VPN server, the .airdns.org DNS record is updated to the exit-IP address of that server. Therefore, be aware that this service may be unusable when you establish multiple connections to different servers from different devices with the same account (in such cases, you need to point directly to the exit-IP address of the server, or use some third-party DDNS which you manually set). I understand how this worked before the multiple Device keys feature came into play but now we can have multiple devices connected to the same server, in which case my guess is that not even trying to point directly to the exit-IP address would make the port forwarding work. My suggestion is to relate de DDNS service to a Device key. For example, adding a "Device key" selector to the port forwarding menu. This way we would have 2 benefits. First, DDNS service would work as long as there were only one device using the related Device key, letting the user have some other connections at the same time. Second, even if a user ended up with a second connection to the very same server, the port forwarding feature would still work for the device with the proper Device key. Thanks in advance for your comments.

Hi I went to test out the port forwarding feature to open my NAT type for call of duty modern warfare 2, but my NAT type is still strict. I want to host some games but use a vpn so people will not ddos my home IP. The ports are: TCP - 3074,27014-27050 and UDP 3478,4379-4380,27000-27031,27036. Maybe I entered them incorrectly?

If I forward a port for my BitTorrent client, are my torrent downloads protected by the VPN?