Search the Community

Hello, I really didn't want to write this post, especially after reading the "Config Generator not resolving hosts for Entry IP 2" post and the https://airvpn.org/topic/14378-how-can-i-get-vpn-servers-entry-ip-addresses post over and over again. I read these posts a million times each but still couldn't figure out how to get my entry IP address and I kind of guessed for the DNS. The only command line prompt I could even get a response for was: nslookup nihal.airservers.org. I tried so many variations of nslookup nl.all.vpn.airdns.org (for example, uslookup pavo.airservers.org) and couldn't get the earth one to work either: earth.all.vpn.airdns.org I went to the specs page of the airvpn website looking for the VPN DNS and kind of just guessed with 10.4.0.1 Here we go: Operating System: RouterOpenVPN version: >= 2.4 IPv4 only Servers: by Continent Protocol: TCP Port: 1194 I chose TCP 1194 because the router I'm flashing has Tor capability and I'm shooting for true anonymity. Everything is just about set up and ready to go but despite reading the entry-ip-addresses article over and over again I couldn't seem to ascertain how exactly to get it. Thoughts anyone?

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

Topic closed.

Just a short question to the admins here. I would like to use the AirVPN DNS servers on my VPN routers. The manuals (DD-WRT and Tomato) are referring to the Specs Page but I can't find them there anymore.

Hi, I have an issue with my home network. I have an ASUS RT-AC87U router. I use Expressvpn on the router with polcy routing. My Mac is connected straight to the WAN but I use AirVPN'd client Eddie. I have had no issues with either Expressvpn or AirVPN. Last night I spent serveral hours on my universities website doing work. At the end of the night I decided to just check everything was running ok with the VPN connections. I found no matter what I did (clear caches, delete cookies, check my dns settings, renew the lease etc) this problem persists. My iPhone uses the Expressvpn (openvpn in the router) and my mac uses the AirVPN client eddie. When I run the ipleak.net test I receive 100 DNS errors. I have not changed any settings in the router whatsoever. I've changed nothing. See the screenshots ... (Sweden is AirVPN, US is Expressvpn) Obviously the error is being caused within my router, which I have restarted and checked for a ASUS-WRT Merlin update).

EDIT: Hello all In order to get an Internet connection i need to reset dns and ip settings everytime after being connected to AirVPN. Help and information about any of this is greatly appreciated. Thanks for reading. SOLVED using merlin user scripts.

Hi guys, Sorry I'm a bit of a noob. Is there any tutorial or has anyone set up Pi-hole (https://pi-hole.net/)+ Air on a RP3 so as to not have DNS be leaked via Pi-hole? Also the ability to VPN from my phone whilst on cellular data to my Pi would be great. How exactly would would the whole process look, presumably I wont use Eddie because the Pi will be handling the Air VPN requests? So how exactly do I connect using my computer and phone? Thank you!

Hi guys, Sorry I'm a bit of a noob. Is there any tutorial or has anyone set up Pi-hole (https://pi-hole.net/)+ Air on a RP3 so as to not have DNS be leaked via Pi-hole? Also the ability to VPN from my phone whilst on cellular data to my Pi would be great. How exactly would would the whole process look, presumably I wont use Eddie because the Pi will be handling the Air VPN requests? So how exactly do I connect using my computer and phone? Thank you!

I normally use AirVPN with openvpn in my computer, with openresolv to allow openvpn to connect to the server then change the DNS so it is tunnelled through the VPN connection. The openvpn config file I downloaded specifies a country, not a particular server, so DNS resolution is needed initially to make the connection. However I am interested in putting the VPN inside a router instead, and I have been experimenting. Looking at the instructions for ddrwt and here: https://airvpn.org/topic/14378-how-can-i-get-vpn-servers-entry-ip-addresses/ it seems it will not be possible to continue using my existing per-country configuration, as I need to give a specific IP address, ie choose just one server (and edit the .ovpn file accordingly). At the moment, I am using an OpenNIC DNS server in parallel with the VPN one instead, but I'd rather not continue to do this. Am I right in thinking each query goes to both DNS servers (rather than using the second one only if the first doesn't return an IP address)? Is there a way to select a country or region, rather than a specific AirVPN server, in this situation? I want to continue using openvpn manually as I understand and trust this method. I am also more familiar with the command line (ssh into the router) than LEDE/OpenWRT, which is new to me.

I have troubles understanding DNS resolution with AirVPN on debian using IP forwarding. My setup is as follows: One debian 9 virtual machine (VM1), acting as the gateway, is connected to two network interfaces: one (enp0s3) is NAT (connected to the host) and the other (enp0s8) is an internal network named "VPN". The gateway connects to AirVPN using openvpn configuration files. Its /etc/network/interfaces is: auto lo iface lo inet loopback allow-hotplug enp0s3 iface enp0s3 inet dhcp allow-hotplug enp0s8 iface enp0s8 inet static address 192.168.42.10 netmask 255.255.192.0 One debian 9 virtual machine (VM2) acts as the client and is only connected to the internal network "VPN". /etc/network/interfaces: auto lo iface lo inet loopback allow-hotplug enp0s3 iface enp0s3 inet static address 192.168.42.11 gateway 192.168.42.10 netmask 255.255.192.0 Through iptables rules, the VM1 (gateway) transparently forwards traffic from the VM2 (client) to its tun0 interface (AirVPN): iptables -t nat -A POSTROUTING -o tun0 -j MASQUERADE iptables -A FORWARD -i tun0 -o enp0s8 -m state --state RELATED,ESTABLISHED -j ACCEPT iptables -A FORWARD -i enp0s8 -o tun0 -j ACCEPT However, I have found that these rules do not forward DNS traffic (why? I don't know), so after searching around, I have also added the following rules to forward DNS traffic to tun0 (AirVPN) DNS resolver (or so it seems?): iptables -t nat -A PREROUTING -i enp0s8 -p udp --dport 53 -j DNAT --to-destination 10.5.0.1 iptables -t nat -A PREROUTING -i enp0s8 -p tcp --dport 53 -j DNAT --to-destination 10.5.0.1 Everyhting seems to work fine, but I don't understand how DNS resolution works. If I test DNS leaks on websites such as ipleak.net, I see that DNS server is AirVPN (=no leak). If I change the abovementioned rules to Google DNS: iptables -t nat -A PREROUTING -i enp0s8 -p udp --dport 53 -j DNAT --to-destination 8.8.8.8 iptables -t nat -A PREROUTING -i enp0s8 -p tcp --dport 53 -j DNAT --to-destination 8.8.8.8 I see on ipleak.net that DNS resolution is done by Google DNS servers (=leaks). This seems to indicate that DNS resolution is correctly done by the gateway (VM1), which correctly redirects it through tun0 interface and AirVPN DNS. The problem is that the client (VM1) still seems to at least try to resolve DNS itself: if I leave its /etc/resolv.conf file blank, it fails to resolve anything and fails to connect to any website. But if I write nameserver 10.0.2.3 which is the default VirtualBox NAT gateway, everything works fine. Why? Why does the client try to resolve DNS queries locally when all its traffic is supposed to be forwarded to the virtual gateway (VM1)? Does it act like a "dummy" DNS resolver that debian needs in order to work? Same goes for the gateway (VM1): if I leave its /etc/resolv.conf file empty, it cannot resolve anything, if I leave the default NAT VirtualBox entry (as above, nameserver 10.0.2.3), it works properly. Why? Isn't AirVPN supposed to replace the default entry in /etc/resolv.conf by its own (10.5.0.1)?

I am getting no response from: 10.4.0.1 No response 10.6.0.1 No response 10.30.0.1 No response No issues resolving through Google DNS: 8.8.8.8 4 msec Anyone else having issues??

AirVPNs DNS: ``` > nslookup h-bid.com Server: 10.4.0.1 Address: 10.4.0.1#53 ** server can't find h-bid.com: SERVFAIL ``` ISPs DNS: ``` > nslookup h-bid.com 192.168.1.1 Server: 192.168.1.1 Address: 192.168.1.1#53 Non-authoritative answer: Name: h-bid.com Address: 164.132.193.202 ```

I am facing the dreaded DNS issue that is caused by not exiting Eddie properly, which in the case of Linux Mint, is due to Eddie crashing frequently (there is a long thread about this). There is also a long thread about the DNS issue, but that thread is all about Windows and provides no step-by-step instuctions for Linux users who encounter this. ​This is the resolv.conf file on a Linux Mint PC that is able to connect to the internet with Eddie (AND network lock) turned OFF. In other words, this is what my resov.conf file should be when I disconnect from Eddie: ​ However, this is what my resolv.conf file looks like when I exit Eddie now: ​ There is no nameserver, and adding it manually does nothing to resolve the issue. How can I fix this so the resolv.conf file is restored correctly? I need to be able to access the internet when Eddie is disconnected. Thanks.

Hi, I've used AirVPN for years now, but recently when I turn AirVPN on (or off) sometimes my DNS adress changes from the Google one to 10.4.0.1. And when I go to the settings (windows) and tick "automatic DNS adress" and I turn the VPN on it connects again to 10.4.0.1 Since this happend all websites take quite some time to connect to and it says "Resolving Host...", Google for example doesn't even load some times and it says that there's a problem with the DNS. Thanks in advance for help!

Hello, For the last two months - trying to get a connection to a Vancouver server for me has be dismal. I am always getting DNS Check Failes - (red x). Other servers work fine. They may take some time but they work. Van has the best latency for me - so my games are better. Going to other countries that are non English are brutal for regular surfing because I don't read Dutch! But those servers log me in. I have rebooted, unplugged the router and modem, power them them back up. I see the client doing the DNS flush... Suggestions? Thanks, Mr. V

Hi. I am running Eddie 2.12.4 on my Ubuntu 17.04 machine and I have been having problems with DNS checking, with the client giving Curl 28 connection timed out. Eventually the client does manage to connect and I can then use the internet again. If I turn DNS checking off, the client connects but I get no internet. The log is quite lengthy, so I will attach it as a .txt file airvpnlog.txt

This may be a newb question, but I need to satisfy my curiosity. Whenever I fire up a VPN connection, I like to check with www.ipleak.net to make sure everything is on the up & up after connecting. I've noticed that on the results page, it shows "IPv6 test not reachable", which I assume means that the Eddie client is doing it's job and disabling IPv6 when connecting. I then see that under "DNS Addresses" it's show 2 servers, One using an IPv4 IP address and the other using an IPv6 address, but of course these two addresses are connected to the VPN IP address I've been assigned. This tells me that there is no DNS leaking going on. I've only witnessed this situation when using AirVPN's servers and the Eddie client (as opposed to, for example, using another VPN service and their connection client). I attached a screencap to show what I am talking about: So, after my long-winded explanation of the issue, here's my question. Because it is showing two DNS servers, and one being a IPv6 server, is this a potential leak for IPv6 traffic since the test is able to connect to this particular server? Is it also possible for it to be a DNS leak, even though it is obviously associated with VPN server that gave me this particular IP address? I'm wondering about this simply because when I use other VPN providers and check ipleak.net, it only shows the one DNS server (IPv4) with the same IP address as the one issued to me by the VPN server. This would lead me to believe that my VPN connection is correctly blocking leaks and using DNS servers provided by the VPN service. Any help with this would be greatly appreciated, and of course, please don't hesitate to ask if I need to clarify any information.

​Hi everyone, Signed up a couple of weeks ago and from the start I've been experiencing very slow DNS lookup. That is to say, webpages will pause on 'looking up example.com...' for 5-10 seconds. ​So far I have tried: adjusted buffers, changed MTU, rolled back TAP driver, experimental Eddie, disabled IPv6. Have tried multiple servers and different browsers with same results. Actual speeds are reasonable enough. Don't see anything untoward in the logs. ​I'm running experimental Eddie client on Windows 10. Router is ASUS RT-AC66U with Merlin firmware. ​Any suggestions? Thanks all.x

Hi I tried accessing some torrent sites in the UK yesterday while using AirVPN (Eddie client, connected to Atik, Netherlands server) and they still seemed to be blocked "by the high court" which led me to believe that somehow the VPN isn't working on that there's a leak as it's seeing that I'm in the UK. So I went to https://www.dnsleaktest.com/ and it says I'm in the Netherlands, which seems correct as that's the server I've connected to but then when I do the standard test, it shows me 4 servers with my country and ISP provider. I have enabled Network Lock at startup in the preferences but that doesn't seem to change anything. Is there something else I should be doing? Sorry I'm new to this. Why would I not be able to access these sites if I'm connected to the Netherlands where they're not blocked? Thanks. EDIT: El Capitan, not Mavericks!

Is there a way to configure my setup to be able to resolve my internal network hosts when connected to the AIRVPN client? My Home Network Laptop - Linux MINT w/AIRVPN client Workstation - Linux MINT - Role: file server pfSense running DNS Resolver (Unbound) I'm trying to write an rsync over SSH script to sync files between my laptop and workstation. My laptop is always connected to VPN and when it is, DNS resolution does not work for my internal hosts. I am still able to reach my workstation by connecting via IP address. I know this is by design to avoid DNS leaks, but am curious to know if it is possible to configure my network to allow internal resolution without compromising security.

Hello Everyone, ​I would like to ask you something that I couldn't figure out no matter how much I researched for. ​I'm using Fedora 26 with Eddie experimental version 2.13.3 and before then I was using gnome network manager to connect to Airvpn. Network lock is activated through Eddie and I placed the same iptables rules Eddie dictates when I was using network manager. ​The issue here is when I disconnect from airvpn all outbound connections do get blocked. I cannot browse or netstat doesn't show any connection. Strange thing here is when I connect back to airvpn and run a ipleak.net test it shows my local ISP dns next to airvpn dns. Restarting browser restores desired results back. ​I used wireshark to examine the network from network adapter directly to see outbound DNS request to ISP dns servers. Well I am probably not very talented with wireshark yet but I can recognize the dns request made by firefox directly to my router and routers answers. That is the only traffic made during disconnected status. I may assume iptables rules should be blocking these requests too? I cannot give any meaning what is happening and researching the web gave no result. A little bit help would be much appreciated. -P INPUT ACCEPT -P FORWARD ACCEPT -P OUTPUT ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -s 255.255.255.255/32 -j ACCEPT -A INPUT -s 192.168.0.0/16 -d 192.168.0.0/16 -j ACCEPT -A INPUT -s 10.0.0.0/8 -d 10.0.0.0/8 -j ACCEPT -A INPUT -s 172.16.0.0/12 -d 172.16.0.0/12 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -i tun+ -j ACCEPT -A INPUT -j DROP -A FORWARD -i tun+ -j ACCEPT -A FORWARD -j DROP -A OUTPUT -d 10.4.0.1/32 -j ACCEPT -A OUTPUT -d 104.243.24.237/32 -j ACCEPT -A OUTPUT -d 104.243.24.235/32 -j ACCEPT -A OUTPUT -d 64.120.44.140/32 -j ACCEPT -A OUTPUT -d 64.120.44.138/32 -j ACCEPT -A OUTPUT -d 173.234.159.196/32 -j ACCEPT -A OUTPUT -d 173.234.159.194/32 -j ACCEPT -A OUTPUT -d 173.44.55.180/32 -j ACCEPT -A OUTPUT -d 173.44.55.178/32 -j ACCEPT -A OUTPUT -d 96.47.229.60/32 -j ACCEPT -A OUTPUT -d 96.47.229.58/32 -j ACCEPT -A OUTPUT -d 173.44.55.156/32 -j ACCEPT -A OUTPUT -d 173.44.55.154/32 -j ACCEPT -A OUTPUT -d 199.241.147.36/32 -j ACCEPT -A OUTPUT -d 199.241.147.34/32 -j ACCEPT -A OUTPUT -d 199.241.146.164/32 -j ACCEPT -A OUTPUT -d 199.241.146.162/32 -j ACCEPT -A OUTPUT -d 199.241.146.180/32 -j ACCEPT -A OUTPUT -d 199.241.146.178/32 -j ACCEPT -A OUTPUT -d 198.203.28.44/32 -j ACCEPT -A OUTPUT -d 198.203.28.42/32 -j ACCEPT -A OUTPUT -d 94.100.23.164/32 -j ACCEPT -A OUTPUT -d 94.100.23.162/32 -j ACCEPT -A OUTPUT -d 46.21.151.108/32 -j ACCEPT -A OUTPUT -d 46.21.151.106/32 -j ACCEPT -A OUTPUT -d 199.249.230.102/32 -j ACCEPT -A OUTPUT -d 199.249.230.100/32 -j ACCEPT -A OUTPUT -d 107.183.238.188/32 -j ACCEPT -A OUTPUT -d 107.183.238.186/32 -j ACCEPT -A OUTPUT -d 64.120.63.92/32 -j ACCEPT -A OUTPUT -d 64.120.63.90/32 -j ACCEPT -A OUTPUT -d 23.88.114.44/32 -j ACCEPT -A OUTPUT -d 23.88.114.42/32 -j ACCEPT -A OUTPUT -d 107.183.238.196/32 -j ACCEPT -A OUTPUT -d 107.183.238.194/32 -j ACCEPT -A OUTPUT -d 107.183.238.180/32 -j ACCEPT -A OUTPUT -d 107.183.238.178/32 -j ACCEPT -A OUTPUT -d 23.88.114.52/32 -j ACCEPT -A OUTPUT -d 23.88.114.50/32 -j ACCEPT -A OUTPUT -d 149.255.33.156/32 -j ACCEPT -A OUTPUT -d 149.255.33.154/32 -j ACCEPT -A OUTPUT -d 23.88.99.196/32 -j ACCEPT -A OUTPUT -d 23.88.99.194/32 -j ACCEPT -A OUTPUT -d 173.234.62.156/32 -j ACCEPT -A OUTPUT -d 173.234.62.154/32 -j ACCEPT -A OUTPUT -d 198.98.113.156/32 -j ACCEPT -A OUTPUT -d 198.98.113.154/32 -j ACCEPT -A OUTPUT -d 46.21.154.84/32 -j ACCEPT -A OUTPUT -d 46.21.154.82/32 -j ACCEPT -A OUTPUT -d 23.106.56.4/32 -j ACCEPT -A OUTPUT -d 23.106.56.2/32 -j ACCEPT -A OUTPUT -d 108.177.134.76/32 -j ACCEPT -A OUTPUT -d 108.177.134.74/32 -j ACCEPT -A OUTPUT -d 23.82.53.140/32 -j ACCEPT -A OUTPUT -d 23.82.53.138/32 -j ACCEPT -A OUTPUT -d 108.62.228.188/32 -j ACCEPT -A OUTPUT -d 108.62.228.186/32 -j ACCEPT -A OUTPUT -d 104.129.24.156/32 -j ACCEPT -A OUTPUT -d 104.129.24.154/32 -j ACCEPT -A OUTPUT -d 104.129.24.188/32 -j ACCEPT -A OUTPUT -d 104.129.24.186/32 -j ACCEPT -A OUTPUT -d 108.177.134.108/32 -j ACCEPT -A OUTPUT -d 108.177.134.106/32 -j ACCEPT -A OUTPUT -d 104.129.24.180/32 -j ACCEPT -A OUTPUT -d 104.129.24.178/32 -j ACCEPT -A OUTPUT -d 91.231.84.42/32 -j ACCEPT -A OUTPUT -d 91.231.84.39/32 -j ACCEPT -A OUTPUT -d 185.200.116.132/32 -j ACCEPT -A OUTPUT -d 185.200.116.130/32 -j ACCEPT -A OUTPUT -d 209.58.167.171/32 -j ACCEPT -A OUTPUT -d 209.58.167.168/32 -j ACCEPT -A OUTPUT -d 185.200.117.132/32 -j ACCEPT -A OUTPUT -d 185.200.117.130/32 -j ACCEPT -A OUTPUT -d 185.200.116.220/32 -j ACCEPT -A OUTPUT -d 185.200.116.218/32 -j ACCEPT -A OUTPUT -d 185.200.116.204/32 -j ACCEPT -A OUTPUT -d 185.200.116.202/32 -j ACCEPT -A OUTPUT -d 185.200.116.212/32 -j ACCEPT -A OUTPUT -d 185.200.116.210/32 -j ACCEPT -A OUTPUT -d 103.254.153.100/32 -j ACCEPT -A OUTPUT -d 103.254.153.68/32 -j ACCEPT -A OUTPUT -d 62.102.148.176/32 -j ACCEPT -A OUTPUT -d 62.102.148.136/32 -j ACCEPT -A OUTPUT -d 62.102.148.170/32 -j ACCEPT -A OUTPUT -d 62.102.148.139/32 -j ACCEPT -A OUTPUT -d 62.102.148.180/32 -j ACCEPT -A OUTPUT -d 62.102.148.134/32 -j ACCEPT -A OUTPUT -d 62.102.148.165/32 -j ACCEPT -A OUTPUT -d 62.102.148.146/32 -j ACCEPT -A OUTPUT -d 62.102.148.159/32 -j ACCEPT -A OUTPUT -d 62.102.148.143/32 -j ACCEPT -A OUTPUT -d 62.102.148.161/32 -j ACCEPT -A OUTPUT -d 62.102.148.144/32 -j ACCEPT -A OUTPUT -d 62.102.148.184/32 -j ACCEPT -A OUTPUT -d 62.102.148.132/32 -j ACCEPT -A OUTPUT -d 62.102.148.174/32 -j ACCEPT -A OUTPUT -d 62.102.148.137/32 -j ACCEPT -A OUTPUT -d 62.102.148.188/32 -j ACCEPT -A OUTPUT -d 62.102.148.148/32 -j ACCEPT -A OUTPUT -d 62.102.148.155/32 -j ACCEPT -A OUTPUT -d 62.102.148.141/32 -j ACCEPT -A OUTPUT -d 62.102.148.190/32 -j ACCEPT -A OUTPUT -d 62.102.148.150/32 -j ACCEPT -A OUTPUT -d 62.102.148.186/32 -j ACCEPT -A OUTPUT -d 62.102.148.151/32 -j ACCEPT -A OUTPUT -d 62.102.148.153/32 -j ACCEPT -A OUTPUT -d 62.102.148.140/32 -j ACCEPT -A OUTPUT -d 62.102.148.163/32 -j ACCEPT -A OUTPUT -d 62.102.148.145/32 -j ACCEPT -A OUTPUT -d 62.102.148.167/32 -j ACCEPT -A OUTPUT -d 62.102.148.147/32 -j ACCEPT -A OUTPUT -d 62.102.148.157/32 -j ACCEPT -A OUTPUT -d 62.102.148.142/32 -j ACCEPT -A OUTPUT -d 62.102.148.168/32 -j ACCEPT -A OUTPUT -d 62.102.148.149/32 -j ACCEPT -A OUTPUT -d 31.3.152.101/32 -j ACCEPT -A OUTPUT -d 31.3.152.99/32 -j ACCEPT -A OUTPUT -d 185.57.80.148/32 -j ACCEPT -A OUTPUT -d 185.57.80.146/32 -j ACCEPT -A OUTPUT -d 109.163.226.155/32 -j ACCEPT -A OUTPUT -d 109.163.230.232/32 -j ACCEPT -A OUTPUT -d 91.207.102.164/32 -j ACCEPT -A OUTPUT -d 91.207.102.162/32 -j ACCEPT -A OUTPUT -d 213.152.161.150/32 -j ACCEPT -A OUTPUT -d 213.152.161.148/32 -j ACCEPT -A OUTPUT -d 213.152.161.134/32 -j ACCEPT -A OUTPUT -d 213.152.161.132/32 -j ACCEPT -A OUTPUT -d 213.152.161.139/32 -j ACCEPT -A OUTPUT -d 213.152.161.137/32 -j ACCEPT -A OUTPUT -d 213.152.162.100/32 -j ACCEPT -A OUTPUT -d 213.152.162.98/32 -j ACCEPT -A OUTPUT -d 213.152.161.75/32 -j ACCEPT -A OUTPUT -d 213.152.161.73/32 -j ACCEPT -A OUTPUT -d 213.152.161.16/32 -j ACCEPT -A OUTPUT -d 213.152.161.14/32 -j ACCEPT -A OUTPUT -d 213.152.162.115/32 -j ACCEPT -A OUTPUT -d 213.152.162.113/32 -j ACCEPT -A OUTPUT -d 213.152.161.21/32 -j ACCEPT -A OUTPUT -d 213.152.161.19/32 -j ACCEPT -A OUTPUT -d 213.152.162.85/32 -j ACCEPT -A OUTPUT -d 213.152.162.83/32 -j ACCEPT -A OUTPUT -d 213.152.161.235/32 -j ACCEPT -A OUTPUT -d 213.152.161.233/32 -j ACCEPT -A OUTPUT -d 213.152.162.150/32 -j ACCEPT -A OUTPUT -d 213.152.162.148/32 -j ACCEPT -A OUTPUT -d 109.232.227.150/32 -j ACCEPT -A OUTPUT -d 109.232.227.148/32 -j ACCEPT -A OUTPUT -d 213.152.161.240/32 -j ACCEPT -A OUTPUT -d 213.152.161.238/32 -j ACCEPT -A OUTPUT -d 213.152.161.26/32 -j ACCEPT -A OUTPUT -d 213.152.161.24/32 -j ACCEPT -A OUTPUT -d 213.152.161.250/32 -j ACCEPT -A OUTPUT -d 213.152.161.248/32 -j ACCEPT -A OUTPUT -d 213.152.162.155/32 -j ACCEPT -A OUTPUT -d 213.152.162.153/32 -j ACCEPT -A OUTPUT -d 213.152.162.90/32 -j ACCEPT -A OUTPUT -d 213.152.162.88/32 -j ACCEPT -A OUTPUT -d 213.152.162.70/32 -j ACCEPT -A OUTPUT -d 213.152.162.68/32 -j ACCEPT -A OUTPUT -d 213.152.161.31/32 -j ACCEPT -A OUTPUT -d 213.152.161.29/32 -j ACCEPT -A OUTPUT -d 109.232.227.139/32 -j ACCEPT -A OUTPUT -d 109.232.227.137/32 -j ACCEPT -A OUTPUT -d 213.152.162.105/32 -j ACCEPT -A OUTPUT -d 213.152.162.103/32 -j ACCEPT -A OUTPUT -d 213.152.162.182/32 -j ACCEPT -A OUTPUT -d 213.152.162.180/32 -j ACCEPT -A OUTPUT -d 213.152.161.86/32 -j ACCEPT -A OUTPUT -d 213.152.161.84/32 -j ACCEPT -A OUTPUT -d 213.152.162.110/32 -j ACCEPT -A OUTPUT -d 213.152.162.108/32 -j ACCEPT -A OUTPUT -d 213.152.162.11/32 -j ACCEPT -A OUTPUT -d 213.152.162.9/32 -j ACCEPT -A OUTPUT -d 213.152.161.36/32 -j ACCEPT -A OUTPUT -d 213.152.161.34/32 -j ACCEPT -A OUTPUT -d 213.152.162.6/32 -j ACCEPT -A OUTPUT -d 213.152.162.4/32 -j ACCEPT -A OUTPUT -d 213.152.161.41/32 -j ACCEPT -A OUTPUT -d 213.152.161.39/32 -j ACCEPT -A OUTPUT -d 213.152.162.95/32 -j ACCEPT -A OUTPUT -d 213.152.162.93/32 -j ACCEPT -A OUTPUT -d 213.152.161.102/32 -j ACCEPT -A OUTPUT -d 213.152.161.100/32 -j ACCEPT -A OUTPUT -d 213.152.162.75/32 -j ACCEPT -A OUTPUT -d 213.152.162.73/32 -j ACCEPT -A OUTPUT -d 213.152.180.6/32 -j ACCEPT -A OUTPUT -d 213.152.180.4/32 -j ACCEPT -A OUTPUT -d 213.152.161.212/32 -j ACCEPT -A OUTPUT -d 213.152.161.210/32 -j ACCEPT -A OUTPUT -d 213.152.161.166/32 -j ACCEPT -A OUTPUT -d 213.152.161.164/32 -j ACCEPT -A OUTPUT -d 213.152.161.245/32 -j ACCEPT -A OUTPUT -d 213.152.161.243/32 -j ACCEPT -A OUTPUT -d 213.152.162.16/32 -j ACCEPT -A OUTPUT -d 213.152.162.14/32 -j ACCEPT -A OUTPUT -d 109.232.227.134/32 -j ACCEPT -A OUTPUT -d 109.232.227.132/32 -j ACCEPT -A OUTPUT -d 213.152.161.70/32 -j ACCEPT -A OUTPUT -d 213.152.161.68/32 -j ACCEPT -A OUTPUT -d 213.152.162.171/32 -j ACCEPT -A OUTPUT -d 213.152.162.169/32 -j ACCEPT -A OUTPUT -d 213.152.161.220/32 -j ACCEPT -A OUTPUT -d 213.152.161.218/32 -j ACCEPT -A OUTPUT -d 213.152.161.11/32 -j ACCEPT -A OUTPUT -d 213.152.161.9/32 -j ACCEPT -A OUTPUT -d 109.202.107.21/32 -j ACCEPT -A OUTPUT -d 109.202.107.19/32 -j ACCEPT -A OUTPUT -d 109.202.103.171/32 -j ACCEPT -A OUTPUT -d 109.202.103.169/32 -j ACCEPT -A OUTPUT -d 213.152.161.230/32 -j ACCEPT -A OUTPUT -d 213.152.161.228/32 -j ACCEPT -A OUTPUT -d 213.152.162.166/32 -j ACCEPT -A OUTPUT -d 213.152.162.164/32 -j ACCEPT -A OUTPUT -d 109.202.107.16/32 -j ACCEPT -A OUTPUT -d 109.202.107.14/32 -j ACCEPT -A OUTPUT -d 213.152.161.171/32 -j ACCEPT -A OUTPUT -d 213.152.161.169/32 -j ACCEPT -A OUTPUT -d 213.152.161.6/32 -j ACCEPT -A OUTPUT -d 213.152.161.4/32 -j ACCEPT -A OUTPUT -d 213.152.162.80/32 -j ACCEPT -A OUTPUT -d 213.152.162.78/32 -j ACCEPT -A OUTPUT -d 109.202.107.148/32 -j ACCEPT -A OUTPUT -d 109.202.107.146/32 -j ACCEPT -A OUTPUT -d 109.202.107.6/32 -j ACCEPT -A OUTPUT -d 109.202.107.4/32 -j ACCEPT -A OUTPUT -d 109.202.107.11/32 -j ACCEPT -A OUTPUT -d 109.202.107.9/32 -j ACCEPT -A OUTPUT -d 213.152.161.118/32 -j ACCEPT -A OUTPUT -d 213.152.161.116/32 -j ACCEPT -A OUTPUT -d 213.152.161.182/32 -j ACCEPT -A OUTPUT -d 213.152.161.180/32 -j ACCEPT -A OUTPUT -d 159.148.186.33/32 -j ACCEPT -A OUTPUT -d 159.148.186.31/32 -j ACCEPT -A OUTPUT -d 159.148.186.26/32 -j ACCEPT -A OUTPUT -d 159.148.186.24/32 -j ACCEPT -A OUTPUT -d 159.148.186.19/32 -j ACCEPT -A OUTPUT -d 159.148.186.20/32 -j ACCEPT -A OUTPUT -d 159.148.186.12/32 -j ACCEPT -A OUTPUT -d 159.148.186.13/32 -j ACCEPT -A OUTPUT -d 46.166.168.37/32 -j ACCEPT -A OUTPUT -d 93.115.29.33/32 -j ACCEPT -A OUTPUT -d 46.166.168.33/32 -j ACCEPT -A OUTPUT -d 93.115.29.23/32 -j ACCEPT -A OUTPUT -d 46.166.165.240/32 -j ACCEPT -A OUTPUT -d 46.166.165.124/32 -j ACCEPT -A OUTPUT -d 103.16.27.76/32 -j ACCEPT -A OUTPUT -d 103.16.27.74/32 -j ACCEPT -A OUTPUT -d 103.16.27.87/32 -j ACCEPT -A OUTPUT -d 103.16.27.85/32 -j ACCEPT -A OUTPUT -d 103.10.197.188/32 -j ACCEPT -A OUTPUT -d 103.10.197.186/32 -j ACCEPT -A OUTPUT -d 103.16.27.27/32 -j ACCEPT -A OUTPUT -d 103.16.27.25/32 -j ACCEPT -A OUTPUT -d 103.16.27.82/32 -j ACCEPT -A OUTPUT -d 103.16.27.80/32 -j ACCEPT -A OUTPUT -d 103.16.27.92/32 -j ACCEPT -A OUTPUT -d 103.16.27.90/32 -j ACCEPT -A OUTPUT -d 78.129.153.59/32 -j ACCEPT -A OUTPUT -d 78.129.153.40/32 -j ACCEPT -A OUTPUT -d 84.39.116.181/32 -j ACCEPT -A OUTPUT -d 84.39.116.179/32 -j ACCEPT -A OUTPUT -d 84.39.117.58/32 -j ACCEPT -A OUTPUT -d 84.39.117.56/32 -j ACCEPT -A OUTPUT -d 82.145.37.204/32 -j ACCEPT -A OUTPUT -d 82.145.37.202/32 -j ACCEPT -A OUTPUT -d 89.249.74.219/32 -j ACCEPT -A OUTPUT -d 89.249.74.217/32 -j ACCEPT -A OUTPUT -d 89.249.74.214/32 -j ACCEPT -A OUTPUT -d 89.249.74.212/32 -j ACCEPT -A OUTPUT -d 185.103.96.136/32 -j ACCEPT -A OUTPUT -d 185.103.96.130/32 -j ACCEPT -A OUTPUT -d 185.103.96.140/32 -j ACCEPT -A OUTPUT -d 185.103.96.131/32 -j ACCEPT -A OUTPUT -d 185.103.96.148/32 -j ACCEPT -A OUTPUT -d 185.103.96.133/32 -j ACCEPT -A OUTPUT -d 94.229.74.92/32 -j ACCEPT -A OUTPUT -d 94.229.74.90/32 -j ACCEPT -A OUTPUT -d 185.103.96.152/32 -j ACCEPT -A OUTPUT -d 185.103.96.134/32 -j ACCEPT -A OUTPUT -d 185.103.96.144/32 -j ACCEPT -A OUTPUT -d 185.103.96.132/32 -j ACCEPT -A OUTPUT -d 88.150.241.17/32 -j ACCEPT -A OUTPUT -d 88.150.240.7/32 -j ACCEPT -A OUTPUT -d 217.151.98.169/32 -j ACCEPT -A OUTPUT -d 217.151.98.167/32 -j ACCEPT -A OUTPUT -d 217.151.98.164/32 -j ACCEPT -A OUTPUT -d 217.151.98.162/32 -j ACCEPT -A OUTPUT -d 80.84.49.51/32 -j ACCEPT -A OUTPUT -d 80.84.49.4/32 -j ACCEPT -A OUTPUT -d 95.215.62.93/32 -j ACCEPT -A OUTPUT -d 95.215.62.91/32 -j ACCEPT -A OUTPUT -d 185.93.182.172/32 -j ACCEPT -A OUTPUT -d 185.93.182.170/32 -j ACCEPT -A OUTPUT -d 185.183.106.4/32 -j ACCEPT -A OUTPUT -d 185.183.106.2/32 -j ACCEPT -A OUTPUT -d 213.136.64.119/32 -j ACCEPT -A OUTPUT -d 79.143.186.171/32 -j ACCEPT -A OUTPUT -d 178.238.229.55/32 -j ACCEPT -A OUTPUT -d 79.143.191.166/32 -j ACCEPT -A OUTPUT -d 79.143.183.161/32 -j ACCEPT -A OUTPUT -d 80.241.210.238/32 -j ACCEPT -A OUTPUT -d 213.136.66.234/32 -j ACCEPT -A OUTPUT -d 79.143.176.194/32 -j ACCEPT -A OUTPUT -d 185.189.112.20/32 -j ACCEPT -A OUTPUT -d 185.189.112.18/32 -j ACCEPT -A OUTPUT -d 185.189.112.12/32 -j ACCEPT -A OUTPUT -d 185.189.112.10/32 -j ACCEPT -A OUTPUT -d 185.189.112.28/32 -j ACCEPT -A OUTPUT -d 185.189.112.26/32 -j ACCEPT -A OUTPUT -d 185.104.184.44/32 -j ACCEPT -A OUTPUT -d 185.104.184.42/32 -j ACCEPT -A OUTPUT -d 89.238.166.236/32 -j ACCEPT -A OUTPUT -d 89.238.166.234/32 -j ACCEPT -A OUTPUT -d 185.156.174.156/32 -j ACCEPT -A OUTPUT -d 185.156.174.154/32 -j ACCEPT -A OUTPUT -d 185.156.174.28/32 -j ACCEPT -A OUTPUT -d 185.156.174.26/32 -j ACCEPT -A OUTPUT -d 185.156.174.116/32 -j ACCEPT -A OUTPUT -d 185.156.174.114/32 -j ACCEPT -A OUTPUT -d 185.156.175.60/32 -j ACCEPT -A OUTPUT -d 185.156.175.58/32 -j ACCEPT -A OUTPUT -d 91.214.169.70/32 -j ACCEPT -A OUTPUT -d 91.214.169.68/32 -j ACCEPT -A OUTPUT -d 185.156.175.44/32 -j ACCEPT -A OUTPUT -d 185.156.175.42/32 -j ACCEPT -A OUTPUT -d 185.156.175.52/32 -j ACCEPT -A OUTPUT -d 185.156.175.50/32 -j ACCEPT -A OUTPUT -d 185.156.175.36/32 -j ACCEPT -A OUTPUT -d 185.156.175.34/32 -j ACCEPT -A OUTPUT -d 185.156.175.172/32 -j ACCEPT -A OUTPUT -d 185.156.175.170/32 -j ACCEPT -A OUTPUT -d 46.19.137.115/32 -j ACCEPT -A OUTPUT -d 46.19.137.114/32 -j ACCEPT -A OUTPUT -d 71.19.251.249/32 -j ACCEPT -A OUTPUT -d 71.19.251.247/32 -j ACCEPT -A OUTPUT -d 71.19.252.33/32 -j ACCEPT -A OUTPUT -d 71.19.252.31/32 -j ACCEPT -A OUTPUT -d 71.19.252.28/32 -j ACCEPT -A OUTPUT -d 71.19.252.26/32 -j ACCEPT -A OUTPUT -d 71.19.252.115/32 -j ACCEPT -A OUTPUT -d 71.19.252.113/32 -j ACCEPT -A OUTPUT -d 71.19.252.23/32 -j ACCEPT -A OUTPUT -d 71.19.252.21/32 -j ACCEPT -A OUTPUT -d 184.75.221.60/32 -j ACCEPT -A OUTPUT -d 184.75.221.58/32 -j ACCEPT -A OUTPUT -d 184.75.223.204/32 -j ACCEPT -A OUTPUT -d 184.75.223.202/32 -j ACCEPT -A OUTPUT -d 184.75.221.196/32 -j ACCEPT -A OUTPUT -d 184.75.221.194/32 -j ACCEPT -A OUTPUT -d 137.63.71.52/32 -j ACCEPT -A OUTPUT -d 137.63.71.50/32 -j ACCEPT -A OUTPUT -d 184.75.221.44/32 -j ACCEPT -A OUTPUT -d 184.75.221.42/32 -j ACCEPT -A OUTPUT -d 199.19.94.195/32 -j ACCEPT -A OUTPUT -d 199.19.94.19/32 -j ACCEPT -A OUTPUT -d 104.254.90.196/32 -j ACCEPT -A OUTPUT -d 104.254.90.194/32 -j ACCEPT -A OUTPUT -d 184.75.223.196/32 -j ACCEPT -A OUTPUT -d 184.75.223.194/32 -j ACCEPT -A OUTPUT -d 184.75.223.228/32 -j ACCEPT -A OUTPUT -d 184.75.223.226/32 -j ACCEPT -A OUTPUT -d 184.75.221.180/32 -j ACCEPT -A OUTPUT -d 184.75.221.178/32 -j ACCEPT -A OUTPUT -d 104.254.90.188/32 -j ACCEPT -A OUTPUT -d 104.254.90.186/32 -j ACCEPT -A OUTPUT -d 184.75.221.36/32 -j ACCEPT -A OUTPUT -d 184.75.221.34/32 -j ACCEPT -A OUTPUT -d 199.19.94.137/32 -j ACCEPT -A OUTPUT -d 199.19.94.132/32 -j ACCEPT -A OUTPUT -d 184.75.223.220/32 -j ACCEPT -A OUTPUT -d 184.75.223.218/32 -j ACCEPT -A OUTPUT -d 184.75.221.4/32 -j ACCEPT -A OUTPUT -d 184.75.221.2/32 -j ACCEPT -A OUTPUT -d 199.19.94.65/32 -j ACCEPT -A OUTPUT -d 199.19.94.61/32 -j ACCEPT -A OUTPUT -d 199.19.95.189/32 -j ACCEPT -A OUTPUT -d 199.19.95.187/32 -j ACCEPT -A OUTPUT -d 104.254.90.252/32 -j ACCEPT -A OUTPUT -d 104.254.90.250/32 -j ACCEPT -A OUTPUT -d 104.254.90.244/32 -j ACCEPT -A OUTPUT -d 104.254.90.242/32 -j ACCEPT -A OUTPUT -d 199.21.149.70/32 -j ACCEPT -A OUTPUT -d 199.21.149.44/32 -j ACCEPT -A OUTPUT -d 104.254.90.236/32 -j ACCEPT -A OUTPUT -d 104.254.90.234/32 -j ACCEPT -A OUTPUT -d 184.75.214.164/32 -j ACCEPT -A OUTPUT -d 184.75.214.162/32 -j ACCEPT -A OUTPUT -d 184.75.223.236/32 -j ACCEPT -A OUTPUT -d 184.75.223.234/32 -j ACCEPT -A OUTPUT -d 184.75.221.212/32 -j ACCEPT -A OUTPUT -d 184.75.221.210/32 -j ACCEPT -A OUTPUT -d 184.75.221.164/32 -j ACCEPT -A OUTPUT -d 184.75.221.162/32 -j ACCEPT -A OUTPUT -d 184.75.221.172/32 -j ACCEPT -A OUTPUT -d 184.75.221.170/32 -j ACCEPT -A OUTPUT -d 184.75.221.116/32 -j ACCEPT -A OUTPUT -d 184.75.221.114/32 -j ACCEPT -A OUTPUT -d 104.254.90.204/32 -j ACCEPT -A OUTPUT -d 104.254.90.202/32 -j ACCEPT -A OUTPUT -d 199.19.94.18/32 -j ACCEPT -A OUTPUT -d 199.19.94.12/32 -j ACCEPT -A OUTPUT -d 184.75.221.204/32 -j ACCEPT -A OUTPUT -d 184.75.221.202/32 -j ACCEPT -A OUTPUT -d 162.219.176.4/32 -j ACCEPT -A OUTPUT -d 162.219.176.2/32 -j ACCEPT -A OUTPUT -d 184.75.223.212/32 -j ACCEPT -A OUTPUT -d 184.75.223.210/32 -j ACCEPT -A OUTPUT -d 93.123.73.115/32 -j ACCEPT -A OUTPUT -d 93.123.73.113/32 -j ACCEPT -A OUTPUT -d 194.187.251.156/32 -j ACCEPT -A OUTPUT -d 194.187.251.154/32 -j ACCEPT -A OUTPUT -d 194.187.251.164/32 -j ACCEPT -A OUTPUT -d 194.187.251.162/32 -j ACCEPT -A OUTPUT -d 194.187.251.116/32 -j ACCEPT -A OUTPUT -d 194.187.251.114/32 -j ACCEPT -A OUTPUT -d 194.187.251.92/32 -j ACCEPT -A OUTPUT -d 194.187.251.90/32 -j ACCEPT -A OUTPUT -d 217.64.127.196/32 -j ACCEPT -A OUTPUT -d 217.64.127.194/32 -j ACCEPT -A OUTPUT -d 185.9.19.108/32 -j ACCEPT -A OUTPUT -d 185.9.19.106/32 -j ACCEPT -A OUTPUT -d 95.211.138.143/32 -j ACCEPT -A OUTPUT -d 54.93.175.114/32 -j ACCEPT -A OUTPUT -d 54.225.156.17/32 -j ACCEPT -A OUTPUT -d 52.48.66.85/32 -j ACCEPT -A OUTPUT -o lo -j ACCEPT -A OUTPUT -d 255.255.255.255/32 -j ACCEPT -A OUTPUT -s 192.168.0.0/16 -d 192.168.0.0/16 -j ACCEPT -A OUTPUT -s 10.0.0.0/8 -d 10.0.0.0/8 -j ACCEPT -A OUTPUT -s 172.16.0.0/12 -d 172.16.0.0/12 -j ACCEPT -A OUTPUT -s 192.168.0.0/16 -d 224.0.0.0/24 -j ACCEPT -A OUTPUT -s 192.168.0.0/16 -d 224.0.0.0/24 -j ACCEPT -A OUTPUT -s 192.168.0.0/16 -d 224.0.0.0/24 -j ACCEPT -A OUTPUT -s 192.168.0.0/16 -d 239.255.255.250/32 -j ACCEPT -A OUTPUT -s 192.168.0.0/16 -d 239.255.255.250/32 -j ACCEPT -A OUTPUT -s 192.168.0.0/16 -d 239.255.255.250/32 -j ACCEPT -A OUTPUT -s 192.168.0.0/16 -d 239.255.255.253/32 -j ACCEPT -A OUTPUT -s 192.168.0.0/16 -d 239.255.255.253/32 -j ACCEPT -A OUTPUT -s 192.168.0.0/16 -d 239.255.255.253/32 -j ACCEPT -A OUTPUT -o tun+ -j ACCEPT -A OUTPUT -j DROP

Hi, my setup is a fresh install of Debian 9 and i run Eddie in an lxde session. everything works perfect, except the dns. Sometimes it seems to work at first but that's always right after you did reconnect to the vpn, so idk what that means. Perhaps any other application editing iptables etc? i didn't find anything like that, at least for now. would be really nice if someone has any idea here if you need any files just ask and I post Edit: some more information: i already tested all the DNS modes(auto and the 2 "linux only" ones), none work. I also tried to add a dns myself but nothing worked

Sometimes - I just get a blank page. 5 minutes later - it works. When I try to go to their site from Google - everything always works. Baffling.

Hi, I understand that AirVPN is using OpenNIC as its DNS, however, I can not access some OpenNIC TLDs, for example: http://www.opennic.chan http://be.libre http://register.neo http://opennic.oz http://reg.dyn http://register.gopher What works: http://www.nic.fur (FurNIC which OpenNIC peers with) http://opennic.glue http://register.bbs http://opennic.free -- .free being phased out; it's new version is .libre which is not accessible from AirVPN http://opennic.geek http://www.parody http://reg.oss * If I shutdown AirVPN, I can access all the TLDs including those that OpenNIC peers with. * I have to add OpenNIC's tier 2 DNS in Eddie > DNS setting to access all OpenNIC TLD (and peers) via AirVPN Is this a bug?

Greetings, Long Story short; I have a Netgate APU with pfSense configured with one "Clear" Network, i.e. no VPN connection, and one VPN Network connected to AirVPN. The clear network has the WiFi AP on it, and most of the time, my laptop (Fedora 25) is connected to the Clear network, but is connected to another VPN provider separately. However, running DNS leak test (dnsleaktest.org, whoer.net etc) sometimes shows the AirVPN DNS on the Clear network, both then devices are connected to a seperate VPN on the clear network, and when they are not. Is this an AirVPN issue, or some sort of lacking pfSense configuration? Would this perhaps be a questions better suited for the pfSense forum? Thanks for any help.