Leaderboard

Hello! We're very glad to inform you that AirVPN has begun to actively contribute to OpenVPN 3 development. Our first goal has been adding support for ChaCha20 cipher with Poly1305 as authenticator on OpenVPN 3 Data Channel. ChaCha20 is a stream cipher developed by Daniel J. Bernstein which combines strength and remarkable performance. https://en.wikipedia.org/wiki/Salsa20#ChaCha20_adoption When compared with AES-GCM, ChaCha20 offers significant computational relief to all AES-NI non supporting processors, such as ARM processors. ARM processors, routinely used on very many tablets, smart phones, media centers, smart TVs and routers, will get great benefits from OpenVPN with ChaCha20. Our tests show that CPU load caused by ChaCha20 on recent ARM 64 bit processors is at least 50% less than AES-256-GCM, on equal terms, which translates into dramatic performance boost and longer battery life (if you have ever tested Wireguard on an ARM based device you know what we mean). OpenVPN 3 is a client library. However, OpenVPN 2.5, which is currently in beta testing and includes all the necessary servers features, supports ChaCha20 on the Data Channel. Therefore, making OpenVPN 3 with ChaCha20 available to our users and allowing a real life test will be a matter of days. We will progressively release beta clients for Android, Linux, OpenBSD and FreeBSD, in this order. We are considering a porting to OpenIndiana as well. Internal alpha testing has concluded successfully. We have already pulled a merge request to OpenVPN 3 main branch, to let the whole community take advantages from our code, and let OpenVPN developers merge the new code into the main branch if they wish so. https://github.com/OpenVPN/openvpn3/pull/78 Implementation has been designed, developed and programmed for AirVPN by ProMIND, who is also Eddie Android edition developer. Stay tuned, more will come! UPDATE: https://airvpn.org/forums/topic/44069-openvpn-3-development-by-airvpn/ The above linked topic is now the central thread to discuss anything related to OpenVPN 3 development and testing. Kind regards and datalove AirVPN Staff

Hello! On April 2018 we made an important step forward: we began to accept Bitcoin directly, through no intermediaries at all. Today, we're very glad to announce that we are able to accept directly more cryptocurrencies. In alphabetical order: Bitcoin Bitcoin Cash Dash Dogecoin Ethereum Ethereum Classic Litecoin Any intermediary acting as a payment processor is no more required. As we wrote in 2018, we stll feel it as an additional, important step forward in privacy protection. Moreover, cutting out any intermediary is very coherent with cryptocurrencies spirit and unleashes their potential. Kind regards and datalove AirVPN Staff

Ok, looks like shellcmd does work, I just had it setup wrong. Using: route -q add 10.4.0.1 `ifconfig ovpnc1 | grep "inet " | cut -d ' ' -f 4` as the command and setting it to run afterfilterchangeshellcmd updates the route table to use the correct gateway and interface if the VPN IP changes. Hopefully, this will be of value to anyone else who has run into a similar issue.

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?

I'm the author of Passepartout and "adware junk" made me sincerely smile. The app recently went from free to paid because it's how I cover a (very) minor fraction of the costs. Not to mention the time I invest(ed) on it, which is far beyond the little money I get from the app. Also, Passepartout has been free as long as I haven't deemed it stable enough to ask people to pay for it. For one, the reviews are 100% legit. It's a strange world where one's guilt is being paid for his hard work. Anyway, I believe that AirVPN users would love an integration with Passepartout.

Yes AES-GCM will perform better with AES-NI support then ChaCha20. Thats the reason why Cloudflare uses ChaCha20 for mobile but AES-GCM for desktop.