Search the Community

Hi everyone, Here's what happened. I have set up my pfSense Firewall Appliance almost two months ago. Using the pfSense Tutorial that AirVPN provides. It worked flawlessly until last Thursday. Suddenly my pfSense router wasn't transferring data anymore and I went on doing some tweaking and noticed that AirDNS (10.4.0.1 wasn't resolving DNS queries anymore. I replaced it with Google, Cisco, Cloudfare, you name DNSs and was back online. I wonder if someone else here has also encountered (or is encountering) this situation? This is very weird. I am positively sure that wasn't any loss of data (my Firewall Appliance is connected to a brand new UPS) Please, let me know. Regards

Hi all, Now that I have my VPN connection running 'tls-crypt, tls1.2' on my pfSense, I am faced with a new problem that I am hoping someone has a solution to. At the time, all I needed was 10.4.0.1 as my DNS Server and I'd be set. I was also able to ping 10.4.0.1. Currently, I have a connection 10.7.114.4 so as 10.4.0.1 seems to be unavailable, I point to 10.7.114.1. The problem is that it's no longer a /24 but a /16 so each time the VPN connection is reset, I have to add a new entry in my 'DNS Resolver' or I am without DNS. What am I missing? Is there a document somewhere on how to properly use a Gen2 server? 10.4.0.1 unreachable $ dig @10.4.0.1 google.com ; <<>> DiG 9.10.6 <<>> @10.4.0.1 google.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached The entries I keep adding to the DNS Resolver forward-addr: 10.7.102.1 forward-addr: 10.7.114.1 Thanks for your help.

I've used the dynamic DNS service for a very long time and all of a sudden the DNS entry doesn't get updated anymore. What I have tried: Wait for 3 hours to make sure that the TTL has been reached: Check ✔Check the TCP Port via the ✔Check my client if the connection worked: Works ✔Try to connect via the IP under "Mapped to public IP:": Works ✔Connect to the server via the airdns.org domain name: Fail ✘Resolve the AirDNS IP: Fail ✘Issue: The IP address is wrong and hasn't been updated yet

Hello, I have a http file server (HFS) running on my Windows PC and I need to access it from the web. I can't find a way to make it work and I'm starting to worry because I precisely chose airvpn in order to be able to forward ports. Here's what I did (infos are fictional) : Forwarded port 12345 on the Forwarded ports page. I entered a DDNS name, let's say "myserver", so it should be accessible from myserver.airdns.org In the service, I set the port to 12345 so the service will listen on that port. Service is running. SelfTest says the server is working fine and is connected. I was forwarding the port 12345 on my router so I stopped doing that to prevent correlation attacks. My router was updating DDNS from no-ip, so I stopped that too (was that necessary? do I absolutely need to use airdns to make it work?) I told my service that my ip is myserver.airdns.org and not a numbered ip like 255.255.255.255 I still cannot access my server when connected to the vpn. It's working just fine without the vpn. I tried to access with the airdns address and on my external address but it can't connect. I tried it on different pc in different locations. What am I forgetting? Thanks for your help!

Hi i made some port forwards with ddns adresses but when i try to connect it says the following when trying to connect to https://myplexserver.airdns.org:portnumber i get a "401 Unauthorized" message when trying to connect to https://mytransmission.airdns.org:portnumber i get a "SSL connection error" message it has something to do wit certificates but i have no knowledge of how to resolve these issues is the someone who can help me understand and fix them? thanks

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: 88.88.22.88 Public WAN VPN Shared IP: 66.66.22.66 Now for example I want to expose a Service on my NAS running on 443/https (TCP) Without considering VPN: Request to 88.88.22.88: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. 66.66.22.66)Set a port foward in Air VPN Config from e.g. 2048 to 443 (TCP)So for public request I need to use url: 66.66.22.66:2048 which will be resolved to 88.88.22.88: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 66.66.22.66:2048 in this instance which resolves to 88.88.22.88: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