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

Hello! We're very glad to inform you that two new 1 Gbit/s full duplex servers located in Miami, Florida, are available: Gudja and Kang, The AirVPN client will show automatically the new servers; if you use any other OpenVPN or WireGuard client you can generate all the files to access them through our configuration/certificates/key generator (menu "Client Area"->"Config generator"). The servers accept connections on ports 53, 80, 443, 1194, 2018 UDP and TCP for OpenVPN and ports 1637 and 47107 UDP for WireGuard. Gudja and Kang support 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. You can check the status as usual in our real time servers monitor: https://airvpn.org/servers/Gudja/ https://airvpn.org/servers/Kang/ Do not hesitate to contact us for any information or issue. Kind regards and datalove AirVPN Team

You would've had the same problem with IPv4 if that setting were a problem. Do you have access to a shell on your Android device? You can enable one in Developer settings starting with Android 11, I think. In there you could try a series of pings with varying packet sizes to nail down what your optimal MTU is. Ask away if you have questions about any of that.