Search the Community
Showing results for tags 'port-forward'.
Found 3 results
Hi, If you want to port-forward and not use the upnp in pfsense, then follow this instruction: In the pfsense browser navigate to Firewall ------> NAT -------> Port Forward Click on the Plus button and follow the instructions in the picture (in the Redirect Target IP section, fill in your client's IP (192.168.0.115 for example) running the program (utorrent for example)In the port sections fill in the forwarded port created on the airvpn websiteIn the Filter rule association section select: create new associated filter rule (this will create a rule for the firewall automatically) Click save and navigate to the Outbound tab and click on the lowest Plus button and follow instructions on the picture (in the Destination IP section, fill in your router's IP)(in the Redirect Target IP section, fill in your client's IP (192.168.0.115 for example) running the program (utorrent for example)In the port sections fill in the forwarded port created on the airvpn website Click Save As you can see in the green light in the below picture, I'm connected: Up and running! Good luck, knicker
Hi all, I am new to AirVPN. I am trying to use it as a way to bypass my ISP block and access my web server. I did configure the VPN with success on my Ubuntu 16.04 machine and i am able to connect to the VPN. Also, I forwarded the traffic to my port 80 and when I check when I check the TCP test everything seems fine (I got a green circle in the AirVPN forwarded port section). Unfortunately, I wasn't able to access the webserver through the given "Mapped to public IP" neither from my same webserver. I also tried with the config files generated using the mode "Direct, protocol UDP, port 80", but still with the same result. Any idea on what am I doing wrong? Thanks in advance, Umberto
Hi, I'd like to be connected to a VPN all the time, but on the other hand want to expose some services to the WAN. My current Setup is follows NAS --> Asus Router running OpenVPN Client with Port Fwds to NAS --> ISP Router/Modem with Asus Router in DMZ --> Air VPN ---/ /--> WAN 192.168.2.2 192.168.2.1 Local: 192.168.1.1 / WAN: 126.96.36.199 Public WAN VPN Shared IP: 188.8.131.52 Now for example I want to expose a Service on my NAS running on 443/https (TCP) Without considering VPN: Request to 184.108.40.206:443ISP Router has Asus Router in DMZ so everything will be forwarded to 192.168.2.1Asus Router has a Port Fwd. Rule for Port 443 -> 192.168.2.2NAS responses to requestWith VPN and VPN Port Forwarding: Find out whats my public ip (eg. 220.127.116.11)Set a port foward in Air VPN Config from e.g. 2048 to 443 (TCP)So for public request I need to use url: 18.104.22.168:2048 which will be resolved to 22.214.171.124:443 and the same happens as described aboveWith VPN and AirVPN DynDNS: Set a port foward in Air VPN Config from e.g. 2048 to 443 (TCP) and DynDNS Name "myservice"Wait at least 1hrequest to myservice.airdns.org should dynamically resolve to 126.96.36.199:2048 in this instance which resolves to 188.8.131.52:443 and the same happens as described above No the problem is this does not seem to work. Please enlighten me if Im thinking wrong here. I pretty sure my setup is ok from the ISP router on since it worked before VPN, also in the AirVPN Port Fwd config I get a green light for at least 1 of my port fwds (not sure why that exactly) Edit: Ok from what I understand the UI Port Fwd only affects income WAN request NOT incomming VPN request (see here: http://www.dd-wrt.com/phpBB2/viewtopic.php?p=642122) so I need to manually add iptables rules for vpn (tun1) port forwarding