Staff

Hello! Thanks, this is a matter for GlueTun developer, we would recommend that you contact him and explain the problem. Please note that in the compose file you set a variable with the = char, not with : . Kind regards

Hello! When VPN_SERVICE_PROVIDER is set to airvpn the optional environment variables deciding the end point are: SERVER_COUNTRIES: Comma separated list of countries SERVER_REGIONS: Comma separated list of regions SERVER_CITIES: Comma separated list of cities SERVER_NAMES: Comma separated list of server names SERVER_HOSTNAMES: Comma separated list of server hostnames https://github.com/qdm12/gluetun-wiki/blob/main/setup/providers/airvpn.md If you feel that this is a bug or unexpected behavior (we see your point: WIREGUARD_ENDPOINT_IP should not be ignored when a non-generic VPN provider is selected, as it apparently happens in your case), the matter should be reported to GlueTun's developer. Please keep in mind that GlueTun is fully compatible and well integrated with AirVPN but it is not developed by AirVPN so every issue should be reported properly also here: https://github.com/qdm12/gluetun-wiki/issues Kind regards

Hello! Your setup is fine and we can reach your listening software through the port that you remotely forwarded. If you need more ports please make sure to pick a free port (the proper tools on the bottom of your AirVPN account port panel will let you find free ports) or just let the system pick a free one for you by leaving the "Port number" field blank and clicking the '+' button. Kind regards

Hello! Thank you! No reason apart from obsolescence of the announcement. Build is anyway for M1. Kind regards

I am also interested in this, but I didn't get it working. Could you please provide more details on how to set it up? A few snippets for the Powershell would be very helpful. Allowing DHCP traffic out, seems to be an default rule with Windows 10. Hello! Something like this will do the trick, starting from a clean status and Windows Firewall enabled. Make sure you operate from a Powershell with administrator privileges. The rules will survive at reboot. You must adjust your local network address/netmask (change 192.168.0.0/16 and fe80::/10 if necessary). Do not proceed if you don't understand exactly every single command; instead, get documented first. netsh advfirewall set allprofiles firewallpolicy blockoutbound netsh advfirewall firewall add rule name="Allow DHCPv4" protocol=UDP dir=out localport=67,68 action=allow netsh advfirewall firewall add rule name="Allow DHCPv6" protocol=UDP dir=out localport=546,547 action=allow netsh advfirewall firewall add rule name="Allow Local IPv4 Network" protocol=TCP dir=out remoteip=192.168.0.0/16 action=allow netsh advfirewall firewall add rule name="Allow Local IPv6 Network" protocol=TCP dir=out remoteip=fe80::/10 action=allow You may also consider to backup the rules and enable them only when needed, instead of keeping them permanent. Check your system manual to do this. Kind regard

Hello! Yes, perfectly possible. Just configure your application(s) to connect to your proxy and use it/them while the system is connected to the VPN. Kind regards

@Hitotsume Hello! Traffic splitting on a destination address basis is not implemented in the Suite and as a consequence exceptions to Network Lock are not available from the options: you would need to add specific rule(s) after the lock has been enforced. However, in your case this is not necessary as Network Lock already allows local networks. Furthermore, the Suite may take care to avoid VPN traffic tunneling into the local network even with WireGuard (default behavior). The behavior can be set through the specific option allowprivatenetwork as you might already know from the manual: * allowprivatenetwork (yes/no) Control how the local and private network traffic can pass through the Network Lock. When disabled, only VPN traffic is allowed through the Network Lock. When enabled local and private network traffic, as well as VPN traffic, is allowed to pass through the Network Lock. Default: yes Please note that WireGuard support and configuration of Network Lock behavior for local network are implemented on AirVPN Suite 2.0.0, currently available as Release Candidate 2: https://airvpn.org/forums/topic/66706-linux-airvpn-suite-200-preview-available/ AirVPN Suite 2.0.0 also implements traffic splitting on an application basis. Although not required in your specific case, since from your description it sounds like you need to connect to sshd only locally, in various scenarios per app traffic splitting may be more useful and/or a valid replacement of traffic splitting on a destination basis. In your case, if you need to have sshd traffic outside the VPN tunnel (i.e. you explicitly want to leak SSH traffic outside the VPN tunnel so that you can reach sshd from the Internet without pointing to AirVPN server addresses and without AirVPN remote port forwarding) it's preferable to just split ssh traffic (read the 2.0.0 user's manual to achieve in a very simple way this purpose if it is necessary). Kind regards

Hello! AirVPN Suite 2.0.0 RC 2 is now out and the error you found has been addressed. Can you please test again and report back at your convenience? Kind regards

Hello! We're very glad to inform you that Hummingbird 2.0.0 Release Candidate 2 is now available for macOS, both for Intel and M1/M2/M3 based systems. The links to the latest RC 2 and the main changes have been updated in the first message of this thread. This version does not differ from RC 1: RC 2 is out just for cross platform versioning consistency. Kind regards

Hello! We're very glad to inform you that AirVPN Suite 2.0.0 Release Candidate 2 for Linux is now available. The original post is updated to show the new download URLs. The important improvements over RC 1 are: Cuckoo's design flaw has been fixed. Now cuckoo can be run when no graphic environment is installed added check and warning to clearly inform the user when firewalld is configured to be the exclusive owner of its tables / chains / rules in case VPN is busy in a pending process (such as reconnecting) stop_connection command is not performed by Bluetit, thus avoiding potential problems a few changes to greatly improve network management during sessions based on WireGuard libxml2 is now statically linked. This pondered decision was driven by various problems caused by a few Linux distributions inconsistencies with established practices and standards linked against the new OpenVPN3-AirVPN 3.12 library 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

Solved. More details: https://airvpn.org/forums/topic/70745-eddie-cant-connect-to-any-server/?do=findComment&comment=249545 Kind regards

@arcanapluvia Hello! The AirVPN Suite offers complete integration with the AirVPN infrastructure, a client/daemon architecture, connections via OpenVPN3-AirVPN and WireGuard, Network Lock compatible with any currently available Linux firewall, per app traffic splitting, synchronous and asynchronous modes, and several other features that you don't have with the native OpenVPN and WireGuard clients. As far as we can evaluate from the feedback the most required features are the infrastructure integration, the Network Lock and the traffic splitting on an application basis, all available in a very light daemon with minimal RAM footprint. Please note that only the Suite 2.0.0 offers all of the above, and it is currently at Release Candidate stage: https://airvpn.org/forums/topic/66706-linux-airvpn-suite-200-preview-available/ Apart from the regular user, for the developer Bluetit exposes a D-Bus interface which can be used by client applications in order to control the daemon (thorough developer's manual included). So it is also instrumental to develop clients or have a deep look at how the infrastructure works. Normally you should be up and running in a couple of minutes. If you still experience issues with 2.0.0 version after you have read the user's manual please do not hesitate to open a ticket. Remember to declare your distribution name and version and if possible include a Bluetit log (for example if you are in a systemd based system you can extract it through journalctl). Kind regards

@jhg23 Hello! A plausible explanation is that the browser downloaded the whole page and not the actual profile. Please try with another browser or use the QR code with the aid of a computer. If a different browser solves the issue, can you please tell us which browser caused it? Kind regards

Hello! It's all pre-defined by GoDaddy and nothing can be configured on our side, unfortunately. We will query GoDaddy and warn them about the issue. We own and control authoritative DNS for almost all of our domain names but not for airvpn.org. to add redundancy. Kind regards

Hello! Already explained in the previous post: enable Network Lock to allow connections to AirVPN infrastructure. Kind regards