Staff

Hello! We're very glad to announce that AirVPN Suite 2.0.0 Release is available. Special thanks to the outstanding community beta testers whose continued support in over a year and a half has been invaluable and decisive to find out and address several, insidious bugs. AirVPN Suite 2.0.0 introduces AirVPN's exclusive per app traffic splitting system, bug fixes, revised code, WireGuard support, and the latest OpenVPN3-AirVPN 3.12 library. Please see the respective changelogs for a complete list of changes for each component of the suite. The 2.0.0 Suite includes: Bluetit: lightweight, ultra-fast D-Bus controlled system daemon providing full connectivity and integration to AirVPN servers, or generic OpenVPN and WireGuard servers. Bluetit can also enforce Network Lock and/or connect the system to AirVPN during the bootstrap Goldcrest: Bluetit client, allowing full integration with AirVPN servers, users, keys, profiles as well as generic OpenVPN and WireGuard servers Hummingbird: lightweight and standalone binary for generic OpenVPN and WireGuard server connections Cuckoo: traffic split manager, granting full access and functionality to AirVPN's traffic split infrastructure airsu: a "run and forget" tool to automatically set and enable the user environment for the X.Org or Wayland based ecosystem without any user input WireGuard support WireGuard support is now available in Bluetit and Hummingbird. OpenVPN or WireGuard selection is controlled by Bluetit run control file option airvpntype or by Goldcrest option -f (short for --air-vpn-type). Possible values: openvpn, wireguard. New 2.0.0 default: wireguard. Bluetit run control file (/etc/airvpn/bluetit.rc) option: airvpntype: (string) VPN type to be used for AirVPN connections. Possible values: wireguard, openvpn. Default: wireguard Goldcrest option: --air-vpn-type, -f : VPN type for AirVPN connection <wireguard|openvpn> Suspend and resume services for systemd based systems For your comfort, the installation script can create suspend and resume services in systemd based systems, according to your preferences. allowing a more proper management of VPN connections when the system is suspended and resumed. The network connection detection code has also been rewritten to provide more appropriate behavior. Asynchronous mode A new asynchronous mode (off by default) is supported by Bluetit and Goldcrest, allowing asynchronous connections. Network Lock can be used accordingly in asynchronous connections. Please consult the readme.md file included in every tarball for more information and details. Word completion on bash and zsh Auto completion is now available by pressing the TAB key when entering any Goldcrest or Hummingbird option and filename on a bash or zsh interpreter. Auto completion files are installed automatically by the installation script. AirVPN's VPN traffic splitting AirVPN Suite version 2.0.0 introduces traffic splitting by using a dedicated network namespace. The VPN traffic is carried out in the default (main) namespace, ensuring all system data and traffic to be encrypted into the VPN tunnel by default. No clear and unencrypted data are allowed to pass through the default namespace. Any non-tunneled network traffic must be explicitly requested by an authorized user with the right to run cuckoo, the AirVPN traffic split manager tool. AirVPN's traffic splitting is managed by Bluetit and configured through run control directives. The system has been created in order to minimize any tedious or extensive configuration, even to the minimal point of telling Bluetit to enable traffic splitting with no other setting. In order to enable and control AirVPN's traffic splitting, the below new run control directives for /etc/airvpn/bluetit.rc have been implemented: allowtrafficsplitting: (on/off) enable or disable traffic splitting. Default: off trafficsplitnamespace: (string) name of Linux network namespace dedicated to traffic splitting. Default: aircuckoo trafficsplitinterface: (string) name of the physical network interface to be used for traffic splitting. All the unencrypted and out of the tunnel data will pass through the specified network device/interface. In case this directive is not used and unspecified, Bluetit will automatically use the main network interface of the system and connected to the default gateway. Default: unspecified trafficsplitnamespaceinterface: (string) name of the virtual network interface to be associated to the Linux network namespace dedicated to traffic splitting. Default: ckveth0 trafficsplitipv4: (IPv4 address|auto) IPv4 address of the virtual network interface used for traffic splitting. In case it is set to 'auto', Bluetit will try to automatically assign an unused IPv4 address belonging to the system's host sub-network (/24) Default: auto trafficsplitipv6: (IPv6 address|auto) IPv6 address of the virtual network interface used for traffic splitting. In case it is set to 'auto', Bluetit will try to automatically assign an unused IPv6 address belonging to the system's host sub-network (/64) Default: auto trafficsplitfirewall: (on/off) enable or disable the firewall in Linux network namespace dedicated to traffic splitting. The firewall is set up with a minimal rule set for a very basic security model. Default: off AirVPN's traffic splitting is designed in order to minimize any further configuration from the system administrator. To actually enable traffic splitting, it is just needed to set "allowtrafficsplitting" directive to "on" and Bluetit will configure the traffic split namespace with the default options as explained above. When needed, the system administrator can finely tune the traffic splitting service by using the above directives. Power and limitations The adopted solution offers a remarkable security bonus in terms of isolation. For example, it gets rid of the dangerous DNS "leaks in" typical of cgroups based traffic splitting solutions. However, the dedicated namespace needs an exclusive IP address. If the system is behind a NAT (connected to a home router for example) this is not a problem, but if the system is not behind any NAT, i.e. it is assigned directly a public IP address, you will need another public IP address for the network namespace dedicated to traffic splitting. You will need to manually set the other public IP address on the trafficsplitipv4 or trafficsplitipv6 directive as the guessing abilities of Bluetit may work only within a private subnet. Please keep this limitation in mind especially if you want to run the Suite with per app traffic splitting on a dedicated or virtual server in some datacenter, as they are most of the times NOT behind any NAT. Introducing Cuckoo, the AirVPN traffic splitting manager tool To generate out of the tunnel traffic, any application software must be run inside the "traffic split" namespace by using the dedicated traffic split tool cuckoo which can be run by users belonging to the airvpn group only. It cannot be used by the superuser. The usage is documented in the manual and on the inline help. The traffic split namespace uses its own routing, network channels and system DNS. It will not interfere or communicate in any way with the default namespace using its own encrypted tunnel. Programs started with cuckoo are regular Linux processes and, as such, can be managed (stopped, interrupted, paused, terminated and killed) by using the usual process control tools. The programs started by cuckoo are assigned to the user who started cuckoo. As a final note, in order to work properly, the following permissions must be granted to cuckoo and they are always checked at each run. Owner: root Group: airvpn Permissions: -rwsr-xr-x (owner can read, write, execute and setuid; group can read and execute, others can read and execute) Special note for snap packages users Snap is a controversial, locking-in package management system developed by Canonical and praised by Microsoft. It packages applications as snaps, which are self-contained units that include all necessary dependencies and run in a sandboxed environment in its default namespace. Therefore, "snap" applications will bypass the order by the system via Cuckoo to have an application running in one specific namespace created for reverse traffic splitting. As a result, snap applications will jettison the Suite's reverse traffic splitting feature. Currently, you must avoid snap packages of those applications whose traffic must flow outside the VPN tunnel. The issue is particularly relevant ever since Ubuntu migrated certain packages exclusively to Snap, such as Chromium and Firefox. At the moment it is still possible to eradicate snap from various distributions, including Ubuntu, quickly. Special note for firewalld users Please read here, it's very important: https://airvpn.org/forums/topic/70164-linux-network-lock-and-firewalld/ AirVPN Switch User Tool Airsu Running an application in a graphical environment requires a user having a local environment properly set, in particular variables and access to specific sockets or cookies. They are usually set at the moment of graphical login, while they may not be properly set in case a user logged in by using the system tool su. In this specific case the user will not probably be allowed to access the graphical environment, so any GUI application will not start. AirVPN’s airsu is used for this specific purpose and configures the user environment to the current X.Org (X11) or Wayland based manager, thus allowing access to GUI applications when run through cuckoo. Note on GUI software and Web Browsers Complete compatibility with both X11 and Wayland based environments has been implemented. Because of the specific Linux architecture and namespaces, some applications may need to specify the graphical environment in order to start and use the currently selected window manager on an X.Org (X11) or Wayland based habitat. Cuckoo can automatically do this by “injecting” predefined options to some preset applications, in particular those based on the chromium engines, most of them being web browsers. To see the list of predefined applications, please start cuckoo with --list-preset-apps option. When running an application with cuckoo, the user should make sure to actually start a new instance. This is usually granted by starting an application from the command line (such as running it with cuckoo). By starting an application from the desktop environment this may not happen. Download AirVPN Suite 2.0.0 The Suite is available in various flavors: ARM 64 bit, ARM 64 bit legacy, ARM 32 bit, ARM 32 bit legacy, x86-64 and x86-64 legacy. Download page: https://airvpn.org/linux/suite/ Changelog and source code Changelog for each component is available inside each package and on GitLab. Source code is available on GitLab: https://gitlab.com/AirVPN/AirVPN-Suite Kind regards and datalove AirVPN Staff

No, they are strictly forbidden, as you might already know from the ToS. Instead of opening an account to complain on community forums, which is useless if we miss the message, please contact abuse@airvpn.org and provide evidence and any information relevant to enable the department to end the abuse. Do not forget to include the targeted IP address or addresses. Kind regards

Hello! You'll be able to avoid any problem by fixing your unit files according to our previous directions. An updated recap after extensive tests and gdb debugging which shows no problems and no crashes (again, provided that the modifications have been implemented). 1. Change permissions of /etc/airvpn.org into 755 (default is 660) to avoid systemd errors (you must have already done this, or you have used proper directives in the unit file, otherwise Bluetit wouldn't start at all but we repeat it for reader's comfort) chmod 755 /etc/airvpn 2. Add the following directives in Bluetit unit file: KillSignal=SIGTERM SendSIGKILL=no to prevent systemd from sending an expected SIGKILL to Bluetit 3. Consider to define the dependency and sequence criteria (systemd correctly warns you that you have not defined them, so it does not know when to start the unit). Example (taken from the default Bluetit unit file): After=network-online.target firewalld.service ufw.service dbus-daemon.service dbus.socket Wants=network-online.target firewalld.service ufw.service dbus-daemon.service dbus.socket 4. Just in case you will decide to use WireGuard and/or Network Lock, you must allow Bluetit to load kernel modules (WireGuard, iptables, nft, xtables...), so this directive: ProtectKernelModules=true must be deleted or set to false to prevent a critical error. 5. Just in case you will decide to use per app traffic splitting, the following directive must be deleted or set to false RestrictNamespaces=true because per app traffic splitting is based on namespace construction. Kind regards

Hello! Thank you, most probably you are right but please do not cut the log anyway, we want to see it integrally. Kind regards

Hello! No, by design: it is intentional. If you need a permanent (surviving reboots) set of rules blocking all traffic (so that by running Eddie and enabling Network Lock you can unblock traffic to the AirVPN servers only) then you must enter the rules yourself, according to the firewall you run on your machine. Kind regards

Hello! Can you also send us the complete Bluetit log from the journal? Kind regards

Hello! We're sorry to inform you that due to sloppy support by the datacenter provider (Racklot) we have decommissioned the server Metallah. Metallah went down on June the 18th, 2025, because IP addresses were null-routed. After more than a month, in spite of various contacts and solicitations, Racklot still fails to restore the routing. Our patience is over and we're acting accordingly. This was the last server still not supporting IPv6 (again for the laziness and the sloppy behavior of Racklot), so we finally have IPv6 support on every and each server. Kind regards

Hello! You have two 10 Gbit/s servers in San Jose (3 Gbit/s full duplex each guaranteed) which usually do not exceed 2+2 Gbit/s on peak times, so according to our stats there's still plenty of bandwidth available there. We will check manually anyway. Kind regards

Hello! Does it happen in the same environment described here? https://airvpn.org/forums/topic/66706-linux-airvpn-suite-200-preview-available/?do=findComment&comment=251565 Kind regards

Good to know, but it's outside our scope to force users to be rigorous. We offer the option and the proper tools to act rigorously and we try to educate through articles. We can't do much more. That was a very good suggestion but it still remains in a limbo, we will prioritize it when possible. Kind regards

It's implemented since 2012 and currently defeats any AI or not AI attempt to disclose users' identity via traffic analysis. Only the global adversary is potentially able to do it, if it exists, but by definition the global adversary can not be defeated in any case, you can only make to it the content of your communications inaccessible, not your real origin and destinations of communications. Difficult to take offense by one who does not even know (or pretends he/she doesn't know) features implemented 13 years ago. Now locking the thread for a few days to avoid trolling anyway. Kind regards

@Donwo1995 Hello! There are a couple of wrong assumptions in your scenario: We do not log origin IP addresses according to the ToS and the current legal framework, therefore we can not provide information we do not have. Not really, as ports can be deleted/changed for account inactivity, pool shifts and other actions not involving the user. This problem can be resolved with specific payment methods without intermediaries. On a different, higher priority layer we must make clear that you can't come here, declare publicly an intent of illegal usage of the service by writing from an account that does not even have a valid subscription and then expect that AirVPN aids and abets this illegal usage through additional ad hoc options. If one really claims a criminal intent and comes here to declare it publicly, he/she should not expect help from AirVPN, in fact quite the contrary. Kind regards

Hello! Yes, thanks a lot! It will be fixed very soon. Kind regards

Hello! We're very glad to inform you that Hummingbird 2.0.0 Release Candidate 3 is now available for macOS, both for Intel and M1/M2/M3/M4 based systems. The links to the latest RC 3 and the main changes have been updated in the first message of this thread. This new version is linked against the latest OpenVPN3-AirVPN library version and improves gateway detection when used in WireGuard mode. Kind regards

Hello! We're very glad to inform you that AirVPN Suite 2.0.0 Release Candidate 3 for Linux is now available. The original post is updated to show the new download URLs. The important improvements over RC 2 are: bug fixes Blutetit: added run control directive networkcheck (please see the included user's manual readme.md) Bluetit: removed run control directive airvpnconnectivitycheck (superseded by networkcheck directive) gateway is set in case it was not provided at construction time Special note for firewalld users Please read here, it's very important: https://airvpn.org/forums/topic/70164-linux-network-lock-and-firewalld/ Please note that compatibility with Debian 10 and its derivatives, that reached end of long term support and end of life on June 2024, is lost even for the legacy version, mainly because the Suite is now C++20 compliant. The legacy version remains suitable for Debian 11 and its derivatives. Kind regards

Hello! We're very glad to inform you that two new 10 Gbit/s full duplex servers located in Frankfurt, Germany, are available: Adhil and Fuyue. They will replace 1 Gbit/s servers Intercrus, Serpens, Tucana and Veritate, which will be decommissioned on 2025-07-31 as they run on hardware and lines that show first signs of inadequacy after a year of extraordinary userbase growth. 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, 47107 and 51820 UDP for WireGuard. They 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/Adhil https://airvpn.org/servers/Fuyue Do not hesitate to contact us for any information or issue. Kind regards & datalove AirVPN Staff

Hello! Please note that if Eddie crashes no leak occurs because Network Lock is a set of firewall rules. Kind regards

Hello! This is by design to avoid permanent lock out on remotely accessed machines while allowing non-VPN traffic when wished. Please also note that the article is wrong in telling that there's a leak during a system reboot even when network lock is enabled: the leak may occur only if the Network Lock has not been engaged, for example if you have not started the AirVPN software. On Linux systems you also have the option of setting a persistent network lock with Bluetit daemon, a component of the AirVPN Suite. As soon as the daemon starts it enforces the network lock, no matter whether a connection is started or not. If you have a systemd based Linux distribution, please note that the asinine systemd init startup is not deterministic and this is of course not our responsibility. Therefore you can't be sure when Bluetit will be started, regardless of the priority you wish. If you need permanent blocking firewall rules surviving reboots even when the VPN software is not running the solution is straightforward: set permanent firewall rules as explained in various articles (a recent one is here https://airvpn.org/forums/topic/69097-permanent-kill-switch-for-eddie-client) or follow the suggestion included in the very same article you linked. Be aware that this setup is problematic on remotely accessed machines. Kind regards

Hello! Thank you very much for your tests! Confirmed, the new OpenVPN3-AirVPN library crashes at disconnection as we incautiously dragged in a dirty modification from the main branch. Problem identified and addressed. Kind regards

Hello! No, we do not work with them, luckily! We have different providers in Germany and new servers will be added soon with new address ranges. Probably the block is aimed at various datacenters to prevent not only usage of publicly known VPN for consumers, but also home made VPN or simply SSH access to proxy to the Internet. Kind regards

Hello! The ZeroTier network interface could be the cause of the problem. Please try to disable the interface and make sure that no ZeroTier VPN etc. related software is running, then try again and check whether the problem gets resolved or not. Kind regards

@Pwbkkee Hello! After extensive debugging we noticed that Bluetit does not crash, but WireGuard does. Please note that in your setup the following option on the bluetit.service file you created: ProtectKernelModules=true prevents Bluetit from loading firewall and WireGuard kernel modules, which are needed respectively for Network Lock and WireGuard proper functioning. The following one: RestrictNamespaces=true prevents traffic splitting. The absence of ConfigurationDirectoryMode= with ConfigurationDirectory=airvpn implies a change of permission in /etc/airvpn (by default 660) with subsequent security problems that must be seriously considered, otherwise the unit can not work in general. Running Goldcrest as a service must also be carefully considered and whenever possible Goldcrest should work as it was designed for, i.e. as a client, with the asynchronous mode in your case. Goldcrest keeps all the standard streams (stdin, stdout and stderr, including TTY access) open, whereas Bluetit does not, as it is a real daemon, not a systemd service, which is only a pale daemon surrogate if you want to be kind, or a fake if you want to call a spade a spade. Therefore running Goldcrest with root privileges by systemd is another security flaw that must be pondered. Other directives could introduce additional problems, but we haven't investigated deeply all of them, we just want to point you toward the main problems and explain the issue you experience. The whole setup introduces instability, causes WireGuard and OpenVPN3-AirVPN library to crash, lowers security and prevents important Bluetit features including Network Lock, so proceed only if you know exactly what you're doing and always consider the instability that you cause especially on WireGuard and OpenVPN library. Kind regards

Hello! After the hardware replacement the server is apparently working very well. Should you find any anomaly do not hesitate to warn us and/or update this thread. Kind regards

@name8828 Hello! Please read here: https://airvpn.org/faq/port_forwarding We kindly invite you and everyone to read manuals and FAQ answers before posting. Kind regards

Hello! The problem has been finally isolated. From the provider customer service, just a few hours ago: "We have located the issue with the cabling, and have asked to [...] swap cables and ports around. This will correct the issue. [...] We expect this work to be completed within 24hrs". Kind regards