Leaderboard

Hello! We're glad to inform you that we have just released: "Road To OpenVPN 2.6" migration plan - https://airvpn.org/road_to_openvpn26/ A new version of Config Generator with options related to OpenVPN 2.6 A new Eddie Desktop beta release (2.23.0) related to the road above, feature-locked to reach stable release https://airvpn.org/forums/topic/56428-eddie-desktop-223-beta-released/ - NOTE: Eddie 2.23 is now obsolete, please upgrade to 2.24 or 2.25 preview versions. Similarly, OpenVPN 2.3 and older versions support will be dropped when DCO migration enters its final stage. A new server (Marsic), the first running OpenVPN 2.6 powered by DCO (server-side) and ready for client-side DCO. UPDATE 2026-03-12 After careful evaluation and considering that: DCO for OpenVPN 2.6 is now considered obsolete the new DCO is aimed at OpenVPN 2.7 only DCO kernel module is included on mainline Linux kernel starting from 6.16 AirVPN VPN infrastructure is based on kernel 6.12 and OpenVPN 2.6 (typical setup of Debian 13, RHEL 10 etc.) OpenVPN usage declined dramatically: today only 24% of connections are based on OpenVPN, and the decline continues at a steady pace the combination of WireGuard and AmneziaWG is more effective than OpenVPN over TCP at bypassing blocks valuable packet payload padding (against encrypted traffic pattern analysis) is offered by AmneziaWG and not DCO: the plan has been momentarily frozen. It can be re-activated when the VPN infrastructure moves to kernel 6.16 (or higher version) and OpenVPN 2.7. Our priority goes to wider AmneziaWG support, on the client software first and then on the server side too (important especially for padding). UPDATE 2026-06-03 We're very glad to inform you that OpenVPN DCO deployment entered its final stage. DCO module and OpenVPN 2.7 are being deployed on all VPN servers. We discarded DCO for OpenVPN 2.6 and aimed at offering OpenVPN 2.7 + DCO directly. As announced in 2023, when DCO was in an embryonic state, we confirm that DCO support implies necessarily end of AES-CBC cipher support, both on Data and Control Channel, because the DCO module does not support it. AES-CBC support, even as a fallback only, would casue the OpenVPN daemons to de-activate DCO globally. Please make sure you run an OpenVPN version that can support AES-GCM on both channels, typically OpenVPN 2.4 or higher versions, linked against an SSL library that includes AES-GCM / CHACHA20-POLY1305 support. UPDATE 2026-10-27 The migration is complete: all AirVPN VPN servers now run OpenVPN 2.7 with the DCO kernel module. The default profile of the Configuration Generator is now DCO compatible. It uses only AEAD ciphers (AES-GCM, CHACHA20-POLY1305) on the Data Channel and no longer contains any compression directive. Continent, country and server selection work with every profile. The OpenVPN profile menu (Advanced) now offers "Default (OpenVPN 2.5 or higher)", "Default without DCO (OpenVPN 2.6 or higher)" and "OpenVPN 2.4". The "2.6 DCO" entry mentioned in the previous update no longer exists, because every server supports DCO. If your OpenVPN client warns that 'comp-lzo' was deprecated (for example Tunnelblick with OpenVPN 2.7), simply generate your configuration files again with default settings. Clarification to the previous update: the AES-CBC restriction applies to the Data Channel, which is the part handled by DCO. OpenVPN 2.3 and older versions can no longer connect. If your device is stuck on an old OpenVPN version (for example an old router or NAS firmware), please consider WireGuard, supported on all our servers. The page https://airvpn.org/road_to_openvpn26/ has been rewritten as "OpenVPN 2.7 and DCO": advantages of DCO, compatibility, Configuration Generator, client-side notes for Linux, Windows and FreeBSD / pfSense / OPNsense, and how to check whether DCO is in use. Kind regards & datalove AirVPN Staff

macOS 13.4 user here. I can confirm that the 2.23.1 Hotfix release has fixed the issues from 2.23.0 which some users have described in this thread. With 2.23.0 and Network lock enabled, it was pretty much unsuable as a lot of sites didn't open up or were horribly slow. So far I have zero issues with the updated release (with and without NWL enabled). Works great, so far so good - thanks a lot @Clodo

Works great now. Thanks for the fix!

Yes, unfortunately it's the "comp-lzo no" directive that disable the DCO, and even if removed (add "-comp-lzo" in Preferences > OpenVPN Directives, note the 'minus') the directive are pushed server-side and cause issues. As explained in the "Road", comp-lzo are not present anymore in 2.6 migrated servers (Marsic). Thanks for your testing and feedback.

Hello! Today I learned about OpenVPN's DCO feature for the first time - from this announcement. So, I spent this day testing it. DCO works great, including but not limited to with TCP over SSL protocol & CHACHA20-POLY1305 data cipher. But only with new Marsic server. If I try to connect to any legacy server, log says: OpenVPN > Note: '--allow-compression' is not set to 'no', disabling data channel offload. And then starts usual software-level tun connection. Error message is untrue, because I explicitly added "allow-compression no" to OpenVPN directives -> Custom directives in Eddie's settings. Funny thing: Eddie knows it. When "compress no" is stated as well, there is an error instead telling that "allow-compression no" is already set. But I see, it is expected behavior according to Road to OpenVPN 2.6 article. 2.23.1 update successfully fixed unresolving websites. Manual connection with CLI openvpn and stunnel also works. If anyone going to test this, run openvpn only as root: sudo is not enough. Otherwise you may not be able to finish openvpn process even with help of SIGKILL - but only if it was active for some time, perhaps until authorization timeout. Just in case, prepare your magic request key to reboot peacefully. ArchLinux, AUR "eddie-ui-git" 2.23.1, openvpn 2.6.5, kernel 6.3.9, AUR "openvpn-dco-dkms" 20230426.

Issue identified, please wait, we will release a new version as soon as possible. Thanks. New version 2.23.1 with the hotfix released. My apologies for the issue.

Did some testing from my pfsense+ box. So far it works very well. It's lovely to see all the openvpn work being done in kernel here and 600mbit/s from this great distance seems very respectable.

Hello! We're very glad to inform you that a new 10 Gbit/s (full duplex) server located in Sofia (Bulgaria) is available: Wazn. With Wazn, AirVPN infrastructure can now offer 10 Gbit/s full duplex lines and servers in strategic locations all over Europe: Switzerland, the Netherlands, Sweden and Bulgaria, all of them with direct peering with a wide variety of providers and at least two tier2 transit providers. As WireGuard diffusion increases, such servers will be able to use more and more bandwidth, while the imminent OpenVPN DCO deployment on selected AirVPN servers will also provide for more scalability and performance. According to our tests (*) from Italy, the Netherlands, the United States and Germany (from both residential and business lines) and our statistics, in the countries with a presence AirVPN remains the fastest VPN for consumers in the world, both for available bandwidth and round trip times. We are confident that the progressive increase of CPU power and available bandwidth, together with our usual commitment against overselling, will further widen the gap. (*) Tests performed from tier1 providers such as Telecom Italia Sparkle or "near-tier1" ones such as Cogent and Hurricane. Tests performed against a wide variety of well known VPN services, including the most advertised ones. The AirVPN client will show automatically the new server; if you use any other OpenVPN or WireGuard client you can generate all the files to access it through our configuration/certificates/key generator (menu "Client Area"->"Config generator"). The server accepts connections on ports 53, 80, 443, 1194, 2018 UDP and TCP for OpenVPN and ports 1637 and 47107 UDP for WireGuard. Wazn supports OpenVPN over SSL and OpenVPN over SSH, TLS 1.3, OpenVPN tls-crypt and WireGuard. Full IPv6 support is included as well. As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses and 4096 bit DH key not shared with any other VPN server. You can check the status as usual in our real time servers monitor: https://airvpn.org/servers/Wazn Do not hesitate to contact us for any information or issue. Kind regards and datalove

Long time user of both AirVPN and qBittorrent here. I am using the latest experimental version of AirVPN v2.22.2.with Wireguard UDP 47107and qBittorrent v4.5.5. In qBittorrent I use only the peer connection protocol TCP. I have the M500 Fibre Broadband package and using speedtest with AirVPN as above I am getting between 420 -485mbps d/l and 35.5u/l speeds regularly. With these settings I am getting download speeds of up to 35mb on a well seeded client with between 350-580 nodes. eg a 3-5GB download takes about 10 minutes. you can PM me for any advice on my set up if you like.

Hello! The quick way is just to download the .deb file (so not the portable) and make sure you have the gdebi program installed; which comes with Mint 18 anyway, usually. Then a wizard will appear once the download is done and you just click through . Saves you messing with file locations.

Hello! No, there's no law forcing that. Not even for ISPs. Wikipedia is just right about it: http://en.wikipedia.org/wiki/Telecommunications_data_retention#United_States VPN services that retain users' connection logs or any other data in the USA do it for their own choice, not because they are obliged to. Kind regards