Leaderboard

The Android app seems to require a master password - this looks to (very often) block reconnection attempts (esp. overnight) leaving the phone without a VPN connection. Is there a way to remove this requirement? Seems other VPN providers do not need it. Thanks

First, I apologize if this has already been addressed, but I searched the forums and how-to guides and couldn't find an answer. I'm using pfsense with dnsmasq (DNS Forwarder). In my General Setup, I set the DNS server to 10.4.0.1 and select AirVPN as the gateway. Unfortunately, this doesn't seem to work as the AirVPN "gateway" is the same as my AirVPN IP address. If I look at the route table, it adds an entry for 10.4.0.1, but sets the netif to lo0 instead of the appropriate ovpnc#, resulting in DNS queries not working. If I set the gateway to none and manually add the route to the gateway (my AirVPN IP address with the last by replaced with .1), everything works. Obviously, this is a routing issue, but I can't figure out how to get pfsense to correctly enter the route into the routing table. I know I can use unbound (DNS Resolver) and that does work. I also know that I can push AirVPN's DNS server to clients and that also works. However, I've been using dnsmasq for the last 18+ months with a different VPN provider without any problems. However, I am evaluating switching to AirVPN as I like many of its other features/functions (and cost!) much better than my current VPN provider. As of now, everything else I've setup works great with AirVPN except for this 1 annoying issue. So...is anyone else using dnsmasq? If so, how did you solve/workaround this routing issue?

If it's not a tunnel within a tunnel, what's the purpose? We think about multi-hopping as a way to solve the problem of a wiretapped VPN server: the traffic transiting through the first hop defeats the wiretapping purposes because the "real payload" is still encrypted. But if the traffic in the first hop is not tunneled into the second hop tunnel, but it is just decrypted, re-encrypted and routed/forwarded to another server operated by the same company, the wiretapping is successful in any case. So, the REAL multi-hopping is what we already provide. The useless "multi-hopping" which is just a way to make your routing longer and nothing else is probably marketing fluff and as usual we will provide neither marketing fluff nor bloat-ware. If we miss something really useful for our mission in multi-hopping without multi-tunneling, please feel free to comment. Kind regards