Staff

Update: Eddie Android edition 2.4 Release Candidate 1 is available. Please check the thread updated initial message for changes. Kind regards

Hello! Please check your system DNS settings before and after the issue occurs. It's a trivial yet safest and fastest way to understand what happens. It's important to know that Eddie changes nameservers immediately after the VPN server DNS push. After that, and during the same VPN session, Eddie does not check or alter DNS anymore, so if "you" (your system) changes them on the fly, Eddie will not do anything. Additionally, you must be aware that Eddie may NOT able to handle DNS properly in systems where systemd-networkd AND systemd-resolved run (also important to know: systemd-resolved might run with or without systemd-networkd running). Unless you have on-link DNS (an abomination for DNS leaks, which unfortunately is now available on Linux too) Linux has a global DNS, so DNS leaks simply don't exist (DNS queries are tunneled regardless the DNS server they are sent to). For various complications and combinations involving DNS please cross check: https://wiki.archlinux.org/index.php/Systemd-networkd Kind regards

Hello! Qomui for Linux allows traffic splitting on an application basis, through cgroups. https://airvpn.org/forums/topic/26327-alternative-airvpn-client-with-provider-independent-double-hop-support-gnulinux/?do=findComment&comment=71685 Whether the feature is compatible with leaks prevention (of any traffic not to/from the "out of tunnel" processes) via firewall rules can be clarified by Corrado, Qomui author. Kind regards

Hello! It is not planned at the moment but we can of course keep your suggestion into consideration. What's the purpose? By knowing the scenario we can make better decisions. Kind regards

Hello! Eddie desktop edition is being developed as usual, with somehow a slower pace but you will see news soon. Eddie Android edition and OpenVPN 3 fork are being developed by another small team that does not work in any way on Eddie Desktop editions. Additional software for Linux, FreeBSD and OpenBSD (as well as OpenIndiana under consideration) will also be developed by the same team, after Eddie 2.4 stable is released. Currently the roadmap includes software for both x86 and ARM based Linux. Kind regards

Hello! Yes, definitely. According to our roadmap, "OpenVPN 3.3 AirVPN" based clients will be deployed for Linux (not only x86 but also ARM), OpenBSD and FreeBSD, three systems which are widely used even in various devices (including routers) using CPUs not supporting AES-NI. Kind regards

Hello! We can't reproduce the issue... Please upgrade to Eddie 2.3, or 2.4 beta 1 and test again at your convenience. Also, do not enter custom directive "block-outside-dns": that's a directive implemented only on OpenVPN 2.3.x and higher version for Windows, which is a system with incomplete DNS implementation (lack of global DNS). Kind regards

Hello! You can't at the moment: please generate profiles directly with Eddie Android edition, or use the following directives to connect from different platforms (remember that only OpenVPN 2.5 beta and OpenVPN 3.3 AirVPN support ChaCha20 on Data Channel): ncp-disable cipher CHACHA20-POLY1305 Kind regards

Hello! That's correct. You can start Eddie and have it connected to an experimental server with ChaCha20 during your device bootstrap by using a profile. Remember that you can generate a profile from inside the app, you don't necessarily have to rely on the Configuration Generator. Go to "Settings" > "AirVPN" and make sure that you have selected "ChaCha20-Poly1305" as "Encryption algorithm" Open "AirVPN Server" view Locate your favorite experimental server Long-tap on it and select "Add to OpenVPN profile", then confirm Go to "OpenVPN Profile" view, tap the generated profile and confirm When the connection is established, reboot your device. Eddie will start and connect to that experimental server during your device bootstrap Kind regards

Hello! Message edited properly to show how you can do that. Thank you very much for your remark. Kind regards

Hello! AirVPN is very proud to introduce for the first time ever OpenVPN 3 support for ChaCha20-Poly1305 cipher with Eddie Android edition 2.4. The new implementation means remarkably higher performance and longer battery life for your Android device. CPUs that do not support AES New Instructions, typically ARM CPUs mounted on most Android devices, are much faster to encrypt and decrypt a stream of data with ChaCha20 than AES. At the same time, ChaCha20 offers the same security when compared to AES. https://en.wikipedia.org/wiki/Salsa20#ChaCha_variant You can test right now the new cipher. We have prepared four test servers running OpenVPN 2.5 and supporting ChaCha20 in Canada, the Netherlands and Singapore. When you pick ChaCha20 as cipher in Settings, Eddie will filter properly Air VPN servers to let you connect to them. The outstanding feature has been made possible by AirVPN implementation on "OpenVPN AirVPN" of new directives, never supported before by OpenVPN 3, as well as a brand new, rationally re-engineered class for AEAD ciphers, which currently includes both AES-GCM and ChaCha20. Development of OpenVPN 3 will go on during the next months. Here's the current status: Eddie Android edition available languages are: Chinese (simplified), Chinese (traditional), Danish, Dutch, English, French, German, Italian, Portuguese, Spanish, Russian, Turkish. Eddie for Android is free and open source software released under GPLv3. We invite you to check from independent 3rd parties lack of trackers code signatures, for example here: https://reports.exodus-privacy.eu.org/en/reports/search/org.airvpn.eddie You can download Eddie Android 2.4 apk directly from our repository: https://eddie.website/repository/eddie/android/2.4/org.airvpn.eddie.apk You can also download it from the Google Play Store: https://play.google.com/store/apps/details?id=org.airvpn.eddie and in Amazon Appstore: https://www.amazon.com/Eddie-AirVPN-official-OpenVPN-GUI/dp/B07KTD6DH9/ref=sr_1_1?keywords=eddie+airvpn Source code is available in GitLab: https://gitlab.com/AirVPN/EddieAndroid/ How to enable ChaCha20 on the Data Channel Open "Settings" view, then open "AirVPN". Locate "Encryption Algorithm", tap it and set "CHACHA20-POLY1305", then tap "OK". New in version 2.4: Updated native library to OpenVPN 3.3 AirVPN ChaCha20-Poly1305 support on both OpenVPN Control and Data channels Support by OpenVPN 3 AirVPN of ncp-disable directive integrated in the app according to the cipher suite picked by the user For new features complete list, please see the changelog at the bottom of this post Main features: Free and open source OpenVPN GUI based on "OpenVPN 3.3 AirVPN" Complete ChaCha20, AES-GCM and AES-CBC support The only Android application officially developed by AirVPN Robust, best effort prevention of traffic leaks outside the VPN tunnel Battery-conscious application Low RAM footprint Ergonomic and friendly interface Ability to start and connect the application at device boot Option to define which apps must have traffic inside or outside the VPN tunnel through white and black list Localization in simplified and traditional Chinese, Danish, English, French, German, Italian, Portuguese, Russian, Spanish, Turkish Full integration with AirVPN Enhanced security thanks to locally stored encrypted data through master password Quick one-tap connection and smart, fully automated server selection Smart server selection with custom settings Manual server selection Smart attempts to bypass OpenVPN blocks featuring protocol and server fail-over Full Android TV compatibility including D-Pad support. Mouse emulation is not required. Enhancements aimed to increase accessibility and comfort to visually impaired persons AirVPN servers sorting options Customizable "Favorite" and "Forbidden" servers and countries OpenVPN mimetype support to import profiles from external applications Multiple OpenVPN profile support. The app now imports and manages multiple OpenVPN profiles Support for custom bootstrap servers Support for favorite and forbidden countries AirVPN broadcast messages support User's subscription expiration date is shown in login/connection information The app is aware of concurrent VPN use. In case another app is granted VPN access, Eddie acts accordingly and releases VPN resources Optional local networks access. In such case, local network devices are exempted from the VPN and can be accessed within the local devices Localization override. User can choose the default language and localization from one of the available ones Favorite and forbidden lists can be emptied with a single tap VPN Lock can now be disabled or enabled from settings VPN reconnection in case of unexpected OpenVPN disconnection. (It requires VPN Lock to be disabled) User can generate an OpenVPN profile for any AirVPN server or country and save it in OpenVPN profile manager Server scoring algorithm implementing the latest AirVPN balancing factors in order to determine the best server for quick connection Network name and extra information are shown along with network type Device network status management Kind regards & datalove AirVPN Staff Changelog 2.4 (VC 26) - Release date: 30 July 2019 by ProMIND [ProMIND] Production release Changelog 2.4 RC 1 (VC 25) - Release date: 26 July 2019 by ProMIND [ProMIND] OpenVPN 3.3 AirVPN fork synchronized to master OpenVPN branch [ProMIND] Native library dependencies updated to the latest releases [ProMIND] Minor bug fixes ConnectAirVPNServerFragment.java [ProMIND] connectServer(): pendingServerConnection is now properly cleared. This prevents a double call from onAirVPNLogin event (user login + user credentials loaded from AirVPN server) in case of a pending server connection going on Changelog 2.4 beta 1 (VC 24) - Release date: 19 July 2019 by ProMIND [ProMIND] Updated native library to "OpenVPN 3.3 AirVPN" supporting CHACHA20-POLY1305 cipher and ncp-disable profile option (forked from OpenVPN:master 3.2 qa:d87f5bbc04) [ProMIND] Updated default manifest to V256 airvpn_server_listview_item.xml [ProMIND] added a new layout for showing server's warning_open field AirVPNServerProvider.java [ProMIND] Added cipher filter according to user settings AirVPNServerSettingsActivity.java [ProMIND] Added encryption algorithm option for AirVPN servers AirVPNServer.java [ProMIND] Added class members to comply to Manifest V256 AirVPNServerGroup.java [ProMIND] New class for manifest V256 handling AirVPNUser.java [ProMIND] getOpenVPNProfile(): profile generator uses "cipher" and "ncp-disable" according to the user settings [ProMIND] getPasswordDialog(): soft keyboard is shown by default [ProMIND] loginDialog(): soft keyboard is shown by default CipherDatabase.java [ProMIND] New class for manifest V256 handling ConnectAirVPNServerFragment.java [ProMIND] Show a warning in yellow in case server has a warning_open status [ProMIND] Servers are now filtered according to selected encryption [ProMIND] searchDialog(): soft keyboard is shown by default ConnectionInfoFragment.java [ProMIND] Added cipher name and digest to info box OpenVPNTunnel.java [ProMIND] Added method getProtocolOptions() QuickConnectFragment.java [ProMIND] Show user selected encryption in status box SettingsActivity.java [ProMIND] Added encryption algorithm option for AirVPN servers SettingsManager.java [ProMIND] Added methods getAirVPNCipher() and setAirVPNCipher() SupportTools.java [ProMIND] Changed AIRVPN_SERVER_DOCUMENT_VERSION to 256 [ProMIND] editOptionDialog(): soft keyboard is shown by default VPN.java [ProMIND] Added class members cipherName and digest

Hello! On server side, we use OpenVPN 2.5 to support ChaCha20 on the Data Channel, so any server with OpenVPN 2.5 will be marked as "Experimental", to make clear that the OpenVPN running in it is a beta version. As soon as OpenVPN 2.5 stable is released, all the servers will be upgraded to support ChaCha20 on the Data Channel without the "Experimental" warning. Our next, imminent step is releasing Eddie Android edition with OpenVPN 3 supporting ChaCha20-Poly1305 to allow immediate testing from those devices based on Android that need ChaCha20 most, for performance and load reasons (such as any Android tablet, smart phone, Amazon Fire TV and any other Android based mediacenter using a CPU that does not support AES-NI). Kind regards

Hello! In addition to what HannaForest wrote, use end-to-end encryption in any case. Kind regards

@prebrov Please see also here to avoid conflicts: https://airvpn.org/forums/topic/26209-how-to-manage-client-certificatekey-pairs/ Kind regards

Hello! We see now that the web site you mention also blocks some Tor exit-nodes we tested. This fact alone puts an end to your insinuations: go trolling somewhere else. Kind regards

A user can be sure that we do not infringe end-to-end connectivity principle and draw his/her own conclusions. It makes a world of difference and raises various questions, for example why does a service want to know your real IP address? Kind regards

Hello! The final web server and/or firewall on the final service machine blocking our VPN servers exit-IP addresses on ports 80 and 443 explains your observations. Kind regards

Hello! We do not block any outbound port except 25. We are forced to do it to mitigate mail spamming. Outbound ports 80 and 443, as well as any other port except 25, are not blocked for any destination. Kind regards

Hello! We are very glad to inform you that our OpenVPN 3 development is progressing swiftly. Today we implemented directive ncp-disable which was still unsupported in OpenVPN 3. https://github.com/AirVPN/openvpn3-airvpn The directive is instrumental to allow clients Data Channel cipher free selection between those available on server, when ncp-ciphers is declared on server side, and keep at the same time total backward compatibility. Since when we implemented ChaCha20-Poly1305 https://airvpn.org/forums/topic/43850-openvpn-3-development/ on OpenVPN 3 Data Channel, "ncp-disable" has become a priority to provide servers and clients with maximum flexibility. We can therefore leave total freedom to clients to pick between AES-GCM, AES-CBC and ChaCha20 while preserving full backward compatibility. Clients with AES-NI supporting processors will prefer AES, while clients running on CPUs without AES-NI, for example most ARM CPUs, will of course tend to prefer ChaCha20. We are working hard to bring you first and foremost a new Eddie Android edition beta version to let you test ChaCha20-Poly1305 on your Android devices as soon as possible. All internal tests both with ChaCha20 and ncp-disable have been fully successful so far. Fingers crossed, maybe you will see a beta release as early as next week. UPDATE: Eddie Android edition with ChaCha20 support on both Data and Control Channel is now available https://airvpn.org/forums/topic/44201-eddie-android-edition-24-beta-1-released-chacha20-support/ https://github.com/AirVPN/openvpn3-airvpn Changelog 3.3 AirVPN - Release date: 13 July 2019 by ProMIND - [ProMIND] [2019/06/02] Forked master openvpn3 repository 3.2 (qa:d87f5bbc04) - [ProMIND] [2019/06/06] Implemented CHACHA20-POLY1305 cipher for both control and data channels - [ProMIND] {2019/07/10] Implemented ncp-disable profile option Kind regards and datalove AirVPN Staff

Nonsense. The tags were meant to make the review easier and in the subsequent commit they were removed as required. Kind regards

Hello! The problem doesn't occur anymore, but if you still experience the issue, probably Eddie won't open again for a corrupt configuration file. If you use Windows version, download and launch this hotfix . Otherwise, please delete default.xml file (on Linux and Mac it's located in ~/.airvpn/default.xml). At the next run, Eddie will re-create a configuration file with default settings. You will need to enter again your AirVPN credentials.  Kind regards

Yes, we're very glad to confirm that the implementation of ChaCha20-Poly1305 on OpenVPN 3 Data Channel is complete and fully working according to our tests, which have been quite thorough. Schwabe's objections are questionable and never enter into the real argument: look at the previous source code of OpenVPN 3 and the new code by ProMIND. You will see all you need to know. Of course our OpenVPN 3 source code will remain available to the community and we want to underline that the style is compliant to the most up to date Knuth's guidelines on the Art of computer programming, while OpenVPN 3 source code is not. We have doubts to comply to Schwabe's requirements and we need to consider the matter carefully: if higher standards are deemed as a problem, then the real problem lies probably in the low standards, not in the higher ones. We now need an additional commit to OpenVPN 3 (almost ready to be published, already tested successfully) and then we will start to develop and release all the software according to the plans we have published. We are talking about days, stay tuned! Kind regards

Hello! The problem doesnn't occur anymore, but if you still experience the issue, probably Eddie won't open again for a corrupt configuration file. If you use Windows version, download and launch this hotfix . Otherwise, please delete default.xml file (on Linux and Mac it's located in ~/.airvpn/default.xml). At the next run, Eddie will re-create a configuration file with default settings. You will need to enter again your AirVPN credentials. Kind regards

Hello! We deeply apologize for the problem that was not caused by Eddie, but by our bootstrap servers. The problem has been resolved. Kind regards

Hello, since 2017 we've been contributing to run about 5-7% of all the worldwide Tor traffic through exit-nodes maintained by Quintex Alliance, please check our mission page. Kind regards