Leaderboard

Hello! We're very glad to inform you that a new Eddie Air client version has been released: 2.25 beta. It is ready for public beta testing. How to test our experimental release: Go to download page of your OS Click the button Switch to EXPERIMENTAL Download and install This is a new version of Eddie Desktop (Windows / Linux / MacOS). The primary purpose of this release is to address several specific issues, including a significant CVE affecting macOS only. We expect it to be promoted to STABLE shortly. We are currently working on a substantial codebase refactoring aimed at evolving Eddie Desktop into a more modern client. Main changelog: [change] [all] Encrypted profiles: save with PBKDF2-SHA256; backward-compatible decrypt of SHA-1 profiles [bugfix] [linux] Fix for distro without systemd [change] [all] Fine-tuning of "netlock.allow_ping" option [new] [all] "netlock.allow_ndp", default true [change] [all] OpenVPN 2.6.17 [bugfix] [macOS] CVE-2025-14979: fix (shortcut-cli removed) [change] [windows] hardened SSH key file permissions to reliably remove orphaned ACL entries and prevent "bad permissions" errors [change] [windows] Updated projects and scripts to Visual Studio 2026 Kind regards & datalove AirVPN Staff

@Erquint Hello! Thank you for your tests! Beta 2 has multiple problems and it turned out to be too unstable on various Android versions. Please hold on, beta 3 is addressing the problems you experienced and coming out soon. Kind regards

I didn't bother waiting. Service seems worth it, I got a trial account and lived up to my expectations. Thank you

Hello! We're very glad to announce that Eddie Android edition 4.0.0 beta 2 is now available. New: how to use Eddie in network where the "bootstrap" servers can not be reached Eddie downloads user and infrastructure data, essential to use the service, from special "bootstrap servers" through an encrypted flow inside HTTP. If the bootstrap servers are blocked or the underlying protocol to port 80 is filtered out, Eddie is unable to proceed. Starting from Eddie 4 beta 2 version, the ability to retrieve such data locally has been added. Whenever bootstrap servers are unreachable, Eddie can read the latest available local data to connect to a VPN server. Once connected the bootstrap servers are again reachable and the local data are immediately updated for future usage. The local data remain valid as long as you don't need to change user. On top of all of the above, Eddie can now retrieve such data through the login procedure that now can be started even when a connection to a VPN server was previously established via a profile. Therefore, when you are in a restrictive network that blocks access to bootstrap servers, you can connect through a profile generated by AirVPN web site Configuration Generator. After this first connection, log your account in to the service by selecting the specific option on the left pane, enter your AirVPN account credentials as usual and make sure that Remember me checkbox is ticked: Eddie will download all the necessary files and store them locally. This procedure is "once and for all", at least as long as you don't need to change account. After this initial connection, Eddie will be able to log your account in to the infrastructure, retrieve servers data and establish connections without profiles and without bootstrap servers, offering again full AirVPN integration even when bootstrap servers are unreachable. Only If you change account you must repeat the procedure. New: "Open with..." option added to "Share" option Different Android versions allow management of files with different restrictions. Different apps may support different intents on specific Android versions. To enlarge total compatibility, now Eddie offers two different options to export and manage files, including generated profiles. You will find the usual "Share" option coupled with a new "Open with..." option. Some apps support only one intent, other apps only specific intents on specific Android versions, and so on. By adding this option Eddie enlarges considerably the amount of apps you will be able to open and/or share files with. New: AmneziaWG parameters range validity AmneziaWG parameter range validity has been documented in three different ways (official web site, GitHub documentation files, and developers comment) and the web site documentation that it's still official is in reality not aligned with the source code. The new parameters range validation adopted by Eddie 4.0.0 beta 2 is based now on GitHub latest documentation integrated by source code analysis. The original message of this thread has been updated accordingly. You will find on it the new download link and checksum, as well as detailed Amnezia description. If you decide to test, please report at your convenience any bug and problem in this thread. If possible generate a report from the app in a matter of seconds: by tapping the paper plane icon on the Log view bar rightmost side you will generate a full system report which will include both log and logcat and have it sent to our servers. Then you just need to send us the link the app shows you (open a ticket if you prefer to do it in private). Kind regards & datalove AirVPN Staff

To fully understand this, you need to look into a concept called Network Address Translation, or NAT. We'll be looking at the following simple connection graph for the explanation: Computer <> Router <> ISP <> Website. The current number of devices in the world which can "speak" IPv4 far exceeds the (mathematical) capacity of the IPv4 address space; we'd run into collisions (two or more devices having the same IP) if all these devices get connected to the internet. So one technique to circumvent this is NAT. This method makes it so that Router gets a public IPv4 from your ISP instead of Computer. The idea is that many devices in a household or company can be operated behind Router without any of them having a public IPv4 address – they all share the public IPv4 address of the router while each of those devices behind the router are given local IPv4 addresses like 10.4.100.100 or 192.168.178.20. Let's say, you are hosting a Minecraft server or something on your computer and you want others to connect to it. Obviously the others need to reach you on a certain IP and on a certain port, and the only public IP they can use is the one from Router because Computer does not have a public IP. Now, let's say, you run the server on port 9000. You can reach it easily from within your home network because every device has a unique IPv4 in that network (= in that 192.168.178.x range for example). The others need to contact you on the Router's public IP. The problem: If they connect to Router:9000, they won't be able to connect to your server. Why? Because the Minecraft server is running on Computer and not on Router. So to tell Router that connections on its public IP and port 9000 should be redirected to Computer, you must forward remote port 9000 (= the port others will use from the internet) to local port 9000 (= the port the Minecraft server is using locally). When a connection to an AirVPN server is made, the server virtually becomes that Router in the graph. The connection graph logically stays the same: Computer <> Router (AirVPN server) <> ISP (datacenter) <> Website. NAT is used there as well, obviously, because you can't just give 80 clients connected to an AirVPN server public IPv4 addresses. So every client gets its own local IPv4 address in the 10.x.x.x range and is therefore part of a virtual network that is private, not public, hence the name Virtual Private Network. The router in your home doesn't play any role as a firewall/NAT anymore while you are connected to AirVPN. AirVPN gives you the possibility to forward ports just like you would do on your home router. If we stay with the Minecraft server example, you now need to instead tell the AirVPN server to redirect connections on its public IP on port 9000 (= the remote port) to Computer's local port 9000. With that knowledge you might realize that this: is not correct. This is the port OpenVPN uses to connect to an AirVPN server. What you do is this: Go to the port forwarding page. Simply click on Add+. The port you see there you enter in qBittorrent settings. You either wait a minute or restart qB. Profit from more throughput.