Jump to content
Not connected, Your IP: 35.175.191.36

Staff

Staff
  • Content Count

    9008
  • Joined

    ...
  • Last visited

    ...
  • Days Won

    1313

Everything posted by Staff

  1. @Aronos Hello! By disabling IPv6 in your Wireless LAN adapter Wi-Fi you made Eddie and OpenVPN unable to connect. The IPv6 layer combo box has not been set to "Block", according to the system report you kindly included. We see that you set "Internet protocol for connection" to "IPv4 only", but that's a different thing. Please open "Preferences" > "Networking" window and set the "IPv6 layer" combo box to "Block", then click "Save" and try again. Alternatively, make sure that IPv6 is enabled in your network interfaces. Kind regards
  2. @Tazhill Hello! Are you 100% sure that your system as well as all network interfaces have IPv6 enabled? If so, can you open a ticket to investigate the matter more thoroughly? Please include a system report ("Logs" > LIFE BELT icon > copy all icon > paste into your message) generated while the system is still connected successfully thanks to the "blocked" IPv6 layer. Kind regards
  3. Hello! Yes, that's plausible. The outcome we and our customers had with Wireguard can have been capped by server bandwidth availability (which may become more significant with WIreeguard than OpenVPN, according to your report) and other factors. Anyway it's a real world/real life test performed between different providers and on equal ground with OpenVPN. On the other end, your OpenVPN findings are low when compared to our customers' and ours.. With weaker CPUs (old i7) our clients achieve much higher performance than yours, up to 700 Mbit/s, with a single instance, while on the server side, with a slightly weaker CPU than yours (but maybe stronger on a per.-core basis, which is crucial with OpenVPN), we could manage to beat 700 Mbit/s on a single OpenVPN daemon connected to about 200 clients. Another factor that comes to mind is the SSL library, which you don't need to worry about when you run Wireguard, but which is vital for OpenVPN performance. Did you compile the library with high optimization for your own server? We recommend OpenSSL currently in x86-64 systems, because it is now remarkably faster than mbedTLS which lacks asm. NOTE: we have never tested LibreSSL and we don't know whether it's a pain to link OpenPVN against LibreSSL. If you need to beat the current performance you report, on top of OpenVPN and OpenSSL optimizations for your system when you build them, the most obvious way is running multiple instances, each one with a different CPU affinity. With the large cores amount you have, you can even aim to saturate your 10 Gbit/s line. Currently our VPN servers Xuange and Ain work around 2-3 Gbit/s with a very low load (around 11 on 32 "CPU" systems). Kind regards
  4. Hello! The actual official cause is lack of IPv6 support either at system level or in any of the network interfaces, including the tun/tap one. It has been verified several times. Should you find cases for which IPv6 layer needs a block inside Eddie preferences even when IPv6 is fully supported by the system and is enabled on all network interfaces, including TAP-Windows or wintun, please report to Clodo. Kind regards
  5. Yes I know this, but can you tell Eddie to only activate Network Lock when connected to VPN, and disconnect when disconnected? Hello! No, Network Lock needs activation BEFORE a VPN connection starts. Anyway Eddie allows "events", check "Preferences" > "Events". You can have a command/script when each event takes place. For security reasons, events linked items are NOT launched with root privileges, so if you need some operation needing root privileges you need take care yourself of it. Only with an operator's input, by default. If you order a disconnection, Eddie will remain disconnected. But if the connection is lost for any reason other than explicit operator's order, Eddie will try to re-connect continuously in any case. You can modify this behavior only through events. For example, if you define an event at VPN disconnection that kills Eddie itself, you will have an approximation of what you want, i.e. "tell Eddie to disconnect when disconnected". However, if you kill Eddie, make sure to reset firewall rules too, because Eddie might fail to restore previous firewall rules (signal handling needs some improvement). You will need to gain root privileges in your script in order to kill Eddie backend and manipulate firewall rules. Kind regards
  6. Hello! && means the logical and in various shell languages, bash (Bourne Again Shell) included, therefore: if (and only if) a command (in this case sleep) is executed and exits successfully, then the command following && will be executed too. This is a short-circuit evaluation. About sleep, enter the following command in a terminal man sleep for more information. In our previous messages we never talked about auto running Eddie. Please re-read at your convenience. You can tell Eddie to activate Network Lock or not when Eddie itself is launched. You can tell Eddie to connect to some VPN server at startup. Kind regards
  7. @Terry Stanford Hello! If you run Eddie GUI, you can configure Eddie to activate Network Lock at startup, check "Activate Network Lock at start" in "Preferences" windows. You can also configure Eddie to connect when it is launched. If you run Eddie CLI, in a screen or tmux session run something like "sleep n && eddie-cli <options here>" where n is in seconds. Kind regards
  8. @frpergflf Hello! SELinux correctly prevents systemd to delete the lock file. That's an illegal operation that systemd wants to perform and that tells something on how systemd is designed. Bleutit crash is caused by the fact that systemd bombards with SIGTERM Bluetit (and in general any real daemon). Under specific circumstances, i.e. when 2 or more SIGTERM signals are sent to Blueit almost simultaneously, Bluetit crashes, because the promise object has been already depleted when the 2nd or nth SIGTERM is received. Again, this incomprehensible behavior tells something about how systemd is designed, but at least it made us find a bug which might cause crashes in any other similar circumstance (imagine if you manage to send SIGTERM from two "kill" commands synced to be executed almost simultaneously). Fix will be of course implemented in the next, imminent version. Kind regards
  9. @Shiloh @Tazhill Hello! The most common cause of the issue is that IPv6 is not supported by system OR some network interface (virtual tun included). In both cases you have two options: 1) Enable IPv6 2) Tell Eddie to "block" IPv6 layer, i.e. the solution aopplied by Shiloh. Kind regards
  10. @harryhoudini Hello! 1) You can use the ListenAddress option in the configuration file. Read the manual for details. Consider whether binding it to any interface (ListenAddress *) in order to make your system accessible even when it's not connected to the VPN. Restart sshd to apply the change. Your current ssh session will not be reset and you will remain connected. 2) We're sorry, maybe we don't understand the question, feel free to elaborate. Consider that if your machine is in a VPN, it's in it, regardless of the exact connection procedure. 3) AirVPN servers exit-IP addresses might change only under exceptional circumstances. Make sure that your machine connects always to the same VPN server, or the same defined range of servers, so you can rely on the same IP address to reach the ssh daemon. Check also https://airvpn.org/faq/servers_ip Note that there is no catch 22. Configure and re-start sshd, see answer 1, then connect the VPN through a terminal multiplexer (consider using screen for example https://linux.die.net/man/1/screen or tmux https://linux.die.net/man/1/tmux.). Once the connection is established, your ssh socket is reset, and you must re-connect, (via the VPN server exit-IP address this time). screen or tmux will have detached the OpenVPN or Eddie process which will continue to run flawlessly even though your previous session is killed for the disconnection (if needed you can of course re-attach OpenVPN/Eddie to your own future session). See also: https://www.shell-tips.com/linux/disown-a-running-shell-process-and-reattach-it-to-a-new-screen/ For a more general approach, check Nadre's articles: https://github.com/tool-maker/VPN_just_for_torrents/wiki/Maintaining-SSH-Access-Using-a-VPN-on-a-Remote-Linux-Server Kind regards
  11. @frpergflf Thank you, the log entry showing a crash problem "Process 133092 (bluetit) of user 0 dumped core." and its previous and following entries seem very relevant. The problem will be soon under investigation. Kind regards
  12. @frpergflf Hello! Allowing access to those directories to group "airvpn" is a choice of each superuser. For security reasons, by default the installer sets them belonging to root user and root or wheel group to comply to the best security practices consolidated in UNIX in the last 30 years. In general, as an optimal security solution, we want that Bluetit files can be edited only by root and sudo-ers, while Goldcrest files (but not Goldcrest binary) can be changed only by users belonging to airvpn group. The lock file removal failure after Bluetit clean stop order by systemd is unexpected. When the problem re-occurs, would you be so kind to send us Bluetit log? sudo journalctl | grep bluetit @asdfasdfasdfasdfasdf No, it is not. If you proceed to implement, don't forget that Bluetit is a daemon. @dL4l7dY6 @airvpnclient A source of Bluetit instability in OSMC and Raspbian 32 bit has been detected, and it's libcurl . The linked library explodes now and then. The problem has been resolved with specific libcurl linking. Development is now focused on a new Network Lock approach, to make the whole environment more secure especially during a system bootstrap. Once it is implemented (a matter of just a few days) we will be ready for testing and soon after a new release will follow, perfectly compatible with OSMC too. Kind regards
  13. @Maggie144 Hello! Since Network Lock is enforced via pf rules, which act directly on the kernel filtering table, it is not plausible that Apple services can bypass them. Leaks observed on Catalina and Big Sur with other software (not our software) take place because filtering rules are enforced via specific network API. The specific network filtering exceptions (for Apple programs) hard coded in macOS Catalina and Big Sur filtering API, which caused a lot of controversies (and rightly so), allow the horrendous behavior. Actually, lack of traffic leaks when Eddie or Hummingbird Network Lock is active on Intel Mac has been thoroughly verified by us through external network sniffers. We confirm that nothing, including Apple services and apps, is able to bypass the firewall (pf) rules. We can perform the same verification on Mac M1 in the near future. The problem in iOS is worse and can't be resolved, because in iOS devices you are not in control of the device filtering table (and you are not in control of the device in general). Anyway we do not write software for iOS, as you know. Should, in the future, "Apple Silicon" platforms evolve in iOS-like system which the user can not control, then they will be unsuitable for purposes where privacy and a layer of anonymity are a priority. We doubt anyway that Apple will expel its own customers from administrative device control like it did with iOS, but let's wait and see. Kind regards
  14. Hello! We're very glad to announce that we have just released Hummingbird for Apple M1 based machines. Hummingbird is a robust, light-weight and very fast OpenVPN 3 command line tool for Linux and macOS offering DNS handling and rock solid traffic leaks prevention out of the box. It's the first time that OpenVPN 3 library and Hummingbird are available as native software in M1 based Mac computers, providing faster execution speed and higher performance. As usual Hummingbird uses our OpenVPN 3 AirVPN library fork, which includes bug fixes and very important features missing in the main branch. Please find overview, details, documentation and download link here: Kind regards
  15. @watcherblue Hello! You can try to disable the route check, so you can determine whether it was a "false positive" or Eddie was right: in "Preferences" > "Advanced" window de.-tick "Check if the tunnel works" and click "Save" in "Preferences" > "DNS" window de-tick "Check Air VPN DSN" enable "Network Lock" from Eddie's main window for additional safety If you see no traffic after the connection, Eddie was right in detecting a route failure, and some other problem is ongoing. If everything is fine, on the contrary, Eddie was wrong (and it remains to be seen why). Kind regards
  16. @OpenSourcerer Understood now, thank you. Kind regards
  17. @dL4l7dY6 Hello! What is the operating system running in your Pi device? Kind regards
  18. Hello! For 2FA we already offer TOTP, which (we think, as far as we can see on documentation after a quick glance) is supported by YubiKey, can you check? Kind regards
  19. @Searching Hello! OK. First of all, can you please make sure that Hummingbird can run successfully? Please run it from a terminal, do not even launch Eddie. Hummingbird documentation and manual: https://airvpn.org/hummingbird/readme/ Let's check binary file ownership too, just in case: please provide us with the output of (when you are in the correct directory): ls -l hummingbird Kind regards
  20. Hello! Please upgrade Eddie at your earliest convenience. You have reported a terrible and actual bug, but it affected only one of the (very) old Eddie versions. Kind regards
  21. @tomMarvoloRiddle Hello! openvpn-connect can be configured as a VPN On Demand application. "VPN-On-Demand ... allows a VPN profile to specify the conditions under which it will automatically connect." Setup is not trivial and requires some patience and time, please see here: https://openvpn.net/vpn-server-resources/faq-regarding-openvpn-connect-ios/#can-i-use-ios-6-vpn-on-demand-with-openvpn Not all OpenVPN services meets "VPN on Demand" requirements. The necessary requisites are met by AirVPN. Kind regards
  22. Hello! We inform you that the following servers located in the Netherlands: Alphecca Alphard Alzirr Asellus Alphirk Chara Matar Phaet are having their IP addresses changed as a necessary datacenter restructuring. What you need to do If you run Eddie (all desktop and Android editions), data will be updated automatically. No action is required. If you have OpenVPN profiles pointing to those servers qualified domain names, everything will be updated automatically. No action is required. If you have OpenVPN profiles pointing directly to those servers IP addresses, you will necessarily have to re-generate such profiles. Kind regards AirVPN Staff
  23. @FunThomas We did not change anything at all... and as we explained the requests you mentioned came from your system itself. Anyway we're glad to know that the mentioned problem is not occurring. Enjoy AirVPN! Kind regards
  24. @Searching Hello! Sure, that test was essential to understand whether the problem was Eddie-specific or involved Hummingbird, it did not imply that we want you to renounce to Eddie. Now that we know that Hummingbird runs just fine, we know that the problem is Eddie-specific and we can investigate with the help of Eddie's developer. First of all, please make sure that Hummingbird belongs to root. Eddie will refuse to run with root privileges a binary file that does not belong to root, and rightly so: it's an important security feature to prevent some kind of attacks aimed at escalating privileges and taking machine control when the attacker can not gain root privileges in the first attack phase. In order to change ownership of Humminbird, open a terminal and issue the following command: sudo chown root /usr/bin/hummingbird The above command will assign Hummingbird to superuser ("root") ownership. We mention /usr/bin because you wrote that you have moved Hummingbird there, but of course enter the correct path if you moved it again. Then re-start Eddie and check whether "Use Hummingbird" is still grayed out or not. Kind regards
  25. @Stack of computer parts Hello! Yes, the OP could do that. It's essential that the Virtual Machine is attached to the host via NAT, in this case, and not bridged. Kind regards
×
×
  • Create New...