Staff

Hello!

The Express VPN interface causes a critical error to OpenVPN:

Tell Eddie to ignore any alien interface: Select from Eddie's main window Preferences > Networking, write eddie in the "VPN interface name" field click Save.
You may also consider to switch to WireGuard to bypass the alien interface. You can do it in Preferences > Protocols window. Uncheck Automatic, select a WireGuard connection mode and click Save.

Kind regards
 

Hello! Android 14 and 15 and Android TV 14 and 15 do not allow background activities; Android 14 and 15 however do have "Always on VPN", unless deleted by the manufacturer; Android TV 10, 11, 12, 13, 14 and 15 do not have "Always on VPN"; Android TV 10, 11, 12, 13 allow background activities. Therefore: on Android TV 14 and 15 the connection to a VPN during the device bootstrap remains impossible on an un-rooted device (*); on Android 14 and 15 connection to a VPN during the bootstrap is possible in spite of the forbidden background activities, thanks to "Always on VPN"; on Android TV 10, 11, 12, 13, connection to a VPN during the bootstrap is possible in spite of lack of "Always on VPN" feature because background activities are allowed. However Eddie, unlike the other apps you mentioned, will not take advantage of it, due to a coded limitation according to which it doesn't let you configure app start at bootstrap if "Always on VPN" is not available on any Android TV 10 and higher versions and other specific Android versions. This is Eddie's part that needs to be re-designed and re-implemented in order to allow connection at boot on Android TV 10, 11, 12, and 13. (*) Except maybe on specific devices for some manufacturer customization thru apps start managers at boot or anything else

Kind regards
 

Hello!

We confirm the problem and we could determine that both the domain name authoritative DNS and the web site block the Taiwan server. Packets get out regularly from the server and from Taiwan but they are black holed by the final destination datacenters. Furthermore the authoritative DNS does not answer to our DNS server in Taiwan (this is a lesser problem as you could resolve the name through some other public DNS or the hosts file). We don't know the reasons of this behavior. If you query Democracy Now and you receive a reply please let us know.

In the meantime we can "micro-route" Democracy Now web site from Sulafat, we will examine how to do it soon.
 
Yes, this is in the official ISO-3166 that Eddie uses to find areas names assigned by the United Nations. According to a previous administrative division, Taiwan is the biggest province of the Republic of China (ROC), not to be confused with People's Republic of China (PRC, mainland China).

By using Taiwan as the country's name, "Province of China" is also a definition pushed by PRC at all levels (from UN to NGOs) to shape two ideas: that PRC must "re-unify" with Taiwan and that when you say "China" you don't talk about the Republic of China, but about the PRC (even PRC detractors fall prey of this propaganda as we can see from this thread). In this sense ISO-3166-2:TW entry could be seen as a concession to PRC narrative and the PRC can "play" over the ambiguity of the definition.

In the next version we may either stay with this one, according to the United Nations status (but see here for some arguments against this), or censor the ISO document itself. A UN spokesperson’s statement in May 2024, reiterating that Taiwan is a province of China (referring to PRC and not ROC according to directly or indirectly PRC controlled media), guided by the General Assembly resolution of 1971 (Resolution 2758), is important to see how much energy PRC spends to affirm the notion that there is only one China and this only China is PRC and not ROC.

On the other hand, we have been fighting and circumventing mainland China (PRC) censorship for 14 years, we recognize China (PRC) as a country enemy of the Internet, controlled by a regime hostile to various human rights, and in reality resolution 2758 interpretation may have been distorted by PRC..

Therefore ISO-3166-2:TW unilateral modification to delete "Province of China" is not unreasonable for us. The matter will be discussed.

However, to insinuate that the normal software usage of an ISO document to translate or find a country/area name means that AirVPN endorses PRC (or PRC alleged wet dream to invade Taiwan) or that AirVPN fails its mission after all the sacrifices brought on to circumvent censorship in mainland China is offensive to say the least, or not in good faith in the worst case. The very fact that we list the server in Taiwan with Taiwan as a country tells a lot, as today Taiwan is recognized as a country only by 12 countries in the world.

Kind regards
 

The simple answer is: No, it is not a great solution. Some clients are connected for months here, so they would absolutely expose themselves over time. Forcing them to reconnect every now and then if they want to preserve their privacy is bad design. If everyone's got one shared IP, it gets more difficult to tell the users apart.
Offering this service for those who want it requires the appropriate infrastructure. It must be possible to switch it at a moment's notice, per account, and per device. Then thinking about how to do this with OpenVPN and Wireguard simultaneously, seamlessly. You also need to educate people that this will only affect v6, a protocol some people around here even disable outright, so your target audience is small, if not niche.

All in all, doing this is not rewarding, and, as written, goes against AirVPN design.

Hello!

We're very glad to inform you that a new 10 Gbit/s full duplex server located in Zurich, Switzerland, is available: Alpherg.

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, 47107 and 51820 UDP for WireGuard.

Alpherg 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.

You can check the status as usual in our real time servers monitor by clicking the names of the servers.
 
Do not hesitate to contact us for any information or issue.
 


Kind regards & datalove
AirVPN Staff

Hello!

We're very glad to inform you that four new 10 Gbit/s full duplex servers located in New York City are available: Muliphein, Paikauhale, Terebellum, Unukalhai. They have replaced Haedus, Iklil and Lich with more powerful hardware and higher overall bandwidth.

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.

The servers 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 by clicking the names of the servers.
 
Do not hesitate to contact us for any information or issue.


Kind regards and datalove
AirVPN Team

Hello!

We're very glad to inform you that AirVPN Suite version 2.0.0 alpha 1  is now available.
UPDATE 2023-11-24: version 2.0.0 alpha 2 is now available.
UPDATE 2024-05-14: version 2.0.0 beta 1 is now available.
UPDATE 2024-12-16: version 2.0.0 beta 2 is now available.

AirVPN Suite 2.0.0 introduces AirVPN's exclusive per app traffic splitting system as well as some bug fixes, revised code in order to pave the way towards the final and stable release, WireGuard support, and the latest OpenVPN3-AirVPN 3.9 library. Please see the respective changelogs for a complete list of preliminary changes for each component of the suite. If you feel adventurous and you wish to test this beta version, please feel free to report any glitch, bug and problem in this very thread.

 
The 2.0.0 Beta 2 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. Default: openvpn. The option is documented in the 1.3.0 manual as well.

Bluetit run control file (/etc/airvpn/bluetit.rc) option:
airvpntype: (string) VPN type to be used for AirVPN connections. Possible values: wireguard, openvpn. Default: openvpn 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 behaviour.

  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, therefore completely separating the VPN traffic from unencrypted and "out of the tunnel" traffic. The VPN traffic is carried out in the default (main) namespace, ensuring all system data and traffic to be encrypted and tunneled into the VPN by default. No clear and unencrypted data are allowed to pass through the default namespace.
Any optional unencrypted data or clear 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 enabled and controlled by Bluetit and by means of 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 introduced: allowtrafficsplitting: (on/off) enable or disable traffic splitting (unencrypted and out of the tunnel traffic) 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

Bluetit supports and implements a traffic splitting facility by using a dedicated network namespace.

AirVPN Traffic splitting is implemented by using a separate and independent network namespace, directly communicating with the system’s default gateway through a virtual interface associated to a physical network interface available in the system. This ensures a true separation of traffic between tunneled and encrypted VPN data from the unencrypted and clear data to be channeled out of the VPN tunnel. The unencrypted traffic generated within the traffic splitting network namespace will never pass through the default (main) namespace - which is under the VPN control - including, and most importantly, DNS requests.

To generate unencrypted and 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 and it cannot be used by the superuser.

The usage is documented in the manual as well as on the inline help.
The traffic split namespace uses its own routing, network channels and DNS. It will not interfere or communicate in any way with the default namespace using its own encrypted tunnel. As for DNS, the traffic split namespace will use default system DNS settings.
 
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)
 
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
The previous limitations on browsers have been completely resolved. Furthermore, complete compatibility with Wayland based environment 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 beta 2
ARM 64 bit:
https://eddie.website/repository/AirVPN-Suite/2.0-Beta2/AirVPN-Suite-aarch64-2.0.0-beta-2.tar.gz
https://eddie.website/repository/AirVPN-Suite/2.0-Beta2/AirVPN-Suite-aarch64-2.0.0-beta-2.tar.gz.sha512

ARM 64 bit legacy:
https://eddie.website/repository/AirVPN-Suite/2.0-Beta2/AirVPN-Suite-aarch64-legacy-2.0.0-beta-2.tar.gz
https://eddie.website/repository/AirVPN-Suite/2.0-Beta2/AirVPN-Suite-aarch64-legacy-2.0.0-beta-2.tar.gz.sha512

ARM 32 bit:
https://eddie.website/repository/AirVPN-Suite/2.0-Beta2/AirVPN-Suite-armv7l-2.0.0-beta-2.tar.gz
https://eddie.website/repository/AirVPN-Suite/2.0-Beta2/AirVPN-Suite-armv7l-2.0.0-beta-2.tar.gz.sha512

ARM 32 bit legacy:
https://eddie.website/repository/AirVPN-Suite/2.0-Beta2/AirVPN-Suite-armv7l-legacy-2.0.0-beta-2.tar.gz
https://eddie.website/repository/AirVPN-Suite/2.0-Beta2/AirVPN-Suite-armv7l-legacy-2.0.0-beta-2.tar.gz.sha512

x86-64:
https://eddie.website/repository/AirVPN-Suite/2.0-Beta2/AirVPN-Suite-x86_64-2.0.0-beta-2.tar.gz
https://eddie.website/repository/AirVPN-Suite/2.0-Beta2/AirVPN-Suite-x86_64-2.0.0-beta-2.tar.gz.sha512

x86-64 legacy:
https://eddie.website/repository/AirVPN-Suite/2.0-Beta2/AirVPN-Suite-x86_64-legacy-2.0.0-beta-2.tar.gz
https://eddie.website/repository/AirVPN-Suite/2.0-Beta2/AirVPN-Suite-x86_64-legacy-2.0.0-beta-2.tar.gz.sha512

Changelogs
Changelogs are available inside each package.




Kind regards & Datalove AirVPN Staff

Hello!

We're very glad to inform you that three new 10 Gbit/s full duplex servers located in Phoenix, Arizona, are available: Gunibuu, Kambalia, Sheratan. They have replaced Chalawan, Indus, Phoenix and Virgo with more powerful hardware and higher overall bandwidth.

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.

The servers 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 by clicking the names of the servers.
 
Do not hesitate to contact us for any information or issue.
 


Kind regards & datalove
AirVPN Team
 

Hello!

We're very glad to inform you that three new 10 Gbit/s full duplex servers located in Los Angeles, California, are available: Maia, Sarin, Xamidimura. They have replaced Groombridge, Saclateni and Teegarden with more powerful hardware and higher overall bandwidth.

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.

The new servers 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 by clicking the names of the servers.
 
Do not hesitate to contact us for any information or issue.
 


Kind regards & datalove
AirVPN Team
 

Hello!

We inform you that due to a few problems we are forced to replace the server Kitalpha in Switzerland. A much more powerful server will replace Kitalpha in the next days and it will be connected to a 10 Gbit/s full duplex port and line. As usual, the new server will be announced in this "News" forum in due time. The new server will not only replace Kitalpha but will also provide the additional bandwidth that several users require in Switzerland. We roughly estimate that the server will be available to you by November the 25th.

Kind regards & datalove
AirVPN Staff
 

Hello!

We're very glad to inform you that a new 10 Gbit/s full duplex server located in Zurich, Switzerland, is available: Alpherg.

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, 47107 and 51820 UDP for WireGuard.

Alpherg 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.

You can check the status as usual in our real time servers monitor by clicking the names of the servers.
 
Do not hesitate to contact us for any information or issue.
 


Kind regards & datalove
AirVPN Staff

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/ A new server (Marsic), the first running OpenVPN 2.6 powered by DCO (server-side) and ready for client-side DCO.
Kind regards & datalove
AirVPN Staff
 

Hello!

We're very glad to inform you that a new 1 Gbit/s (full duplex) server located in Taipei (Taiwan), is available: Sulafat.

The server supports OpenVPN over SSL and OpenVPN over SSH, TLS 1.3, OpenVPN tls-crypt and WireGuard.

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 them 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, 47107 and 51820 UDP for 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.

This is our first server in Taiwan; the tests we have performed during the last week have been encouraging but not totally perfect for our quality standards. Your feedback is welcome and it will be crucial to determine whether this server's datacenter can meet your expectations and requirements.

You can check the status in our real time servers monitor:
https://airvpn.org/servers/Sulafat/

Kind regards & datalove
AirVPN Staff

Hello!

We're very glad to inform you that a new 1 Gbit/s full duplex server located in Madrid (Spain) is available: Jishui.

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 OpenVPN connections on ports 53, 80, 443, 1194, 2018 UDP and TCP, and WireGuard connections on ports 1637, 47107 and 51820.

Just like every other Air server, Jishui supports OpenVPN over SSL and OpenVPN over SSH, TLS 1.3, 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 server status as usual in our real time servers monitor:
https://airvpn.org/servers/Jishui

Do not hesitate to contact us for any information or issue.


Kind regards and datalove
AirVPN Team
 

Hello!

The previous problem is resolved. When the connection attempt fails your network is unreachable according to OpenVPN:
. 2024.07.01 15:57:48 - OpenVPN > write UDP: Network is unreachable (code=51) . 2024.07.01 15:57:48 - OpenVPN > Network unreachable, restarting The error message hints at various options: your network is down your physical interface is down the network is up but UDP is blocked directly in the machine (check firewall etc.) Please test a connection over WireGuard to see whether WireGuard can't reach the network too. Switch to WireGuard in Preferences > Protocols window (uncheck Automatic, select any WireGuard line and click Save).

Kind regards
 

@cyberslav

Hello!

For an explanation and a quick solution please see here:
https://airvpn.org/forums/topic/56657-cant-connect-to-anything/?do=findComment&comment=225418

Kind regards
 

Hello!

We post the reply to your ticket by the support team for the reader's comfort.
 
====
Hello and thank you for your choice!

We do not think that the problem can be approached and resolved through OpenVPN configuration files. We would consider policy based routing on the router. In this way you can configure each specific device behind the router to have its traffic routed through the proper tun interface or even through the WAN (outside the VPN, therefore). Please check the documentation.
An overview of the Policy Based Routing (PBR) utility:
https://openwrt.org/docs/guide-user/network/routing/pbr
 
A specific approach to achieve the setup:
https://search.brave.com/search?q=openwrt+policy+routing+for+multiple+OpenVPN+client+connections&summary=1&conversation=f943dbcf532434cd689c65

Kind regards
AirVPN Support Team
====

Kind regards
 

Hello!

Of course. We will study the matter carefully and we will update this thread.

Kind regards
 

I'm in for two more years. Thank you for excellent service.

Hello!

We're very glad to inform you that a new 10 Gbit/s full duplex server located in Zurich, Switzerland, is available: Alpherg.

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, 47107 and 51820 UDP for WireGuard.

Alpherg 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.

You can check the status as usual in our real time servers monitor by clicking the names of the servers.
 
Do not hesitate to contact us for any information or issue.
 


Kind regards & datalove
AirVPN Staff

Hello!

We're very glad to inform you that a new 10 Gbit/s full duplex server located in Zurich, Switzerland, is available: Alpherg.

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, 47107 and 51820 UDP for WireGuard.

Alpherg 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.

You can check the status as usual in our real time servers monitor by clicking the names of the servers.
 
Do not hesitate to contact us for any information or issue.
 


Kind regards & datalove
AirVPN Staff

Hello!

We're very glad to inform you that a new 10 Gbit/s full duplex server located in Zurich, Switzerland, is available: Alpherg.

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, 47107 and 51820 UDP for WireGuard.

Alpherg 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.

You can check the status as usual in our real time servers monitor by clicking the names of the servers.
 
Do not hesitate to contact us for any information or issue.
 


Kind regards & datalove
AirVPN Staff

Thanks. Added another 3 years. Hope that will help to keep the light on.

Thanks for the deal! Have been trying AirVPN out for the last 3 months, that deal just confirmed I will be switching for good

I am just learning about all the available settings and I like AIR VPN already.
Most probably I will extend my subscription.