Leaderboard

I made DNS server changes. Using my own PiHole at home as DNS server, while having a VPN Client connection from the router to the AirVPN server. The PiHole DNS is running Quad9 (malicious source block) DNS as backend, and in the PiHole I added a lot of Tracker and Adblocker lists, blocking toally around 1.700.000 domains. For the VPN while traveling I did a similar setup, but use nextDNS as a PiHole alternative in the cloud. Very handy! The main reason for using an own DNS ist the Ad and Tracker blocking functionality inbuild in those DNS setups, with a part of maliocus connections blocked too.

Where I am at with this : After speaking with the AirVPN staff, we looked at a few of the advanced settings and tried to use logs before, during and after the disconnects. Firstly, I updated to the latest Eddie version. This did not solve the problem out right. We then noted that in Eddie under Preferences>advanced there is a section 'Microsoft Windows only.' In that area I had 'Force all network interfaces for DNS' and 'Ensure DNS lock' enabled. Now while I had always had it like this, and never faced the DNS and disconnects as detailed in this thread by myself and other users, disabling those two features did seem to reduce the amount of disconnects overall. Next, I made sure to set my normal Windows Ethernet adapter to manual/static despite it already being static in my router. And for DNS, I used my own gateway address as the first DNS (left second DNS blank). Things were going well for several days and then it happened again. However there was one noteable difference. After the disconnect, I was able to close Eddie down and run via my normal Ethernet connection, without delay. Before with the old version of Eddie and settings, I would have to restart the computer for Eddie to let go of the Ethernet connection and release it. Then I got really busy and didn't use the internet much. I moved, setup new machines, reinstalled Windows and subsequently due to the move, am on a new internet line/connection. Using the same Eddie version and configuration, I have been consistent and stable without any of the issues mentioned in this thread. I informed the guys on the team..it's not very conclusive but there were some things above that did contribute to a more positive experience, regardless of whether the issue is actually solved. Personally I still think it was on Air's side and either it went away on it's own or they figured it out and silently fixed it.

I agree with Stephen use the remote command : put the servers to reconnect to in the order you want them to reconnect too. today was literally a perfect example. My isp dropped at least 5 times today i had ; remote us3.vpn.airdns.org 443; under client / custom options. It reconnected once my isp got its issue fixed. You could use the static ip instead followed by the port to use

I already know the link from https://nguvu.org/pfsense/pfsense-multi-vpn-wan/. pfSense only allows a failover when the client is down or "packet loss or high latency". The script I asked for in the pfSense forum should automatically restart the chain if, for example, the second server of three fails. This should ensure the order. I think it would be more complicated if you restart the failed server and restart the route order. For this purpose a KillSwitch would be helpful, which makes sure that pfSense does not leave anything if for example the second server fails. Do you have any other suggestions? Greetings John