Search the Community

Currently AirVPN servers ONLY provide you with IPv6 connectivity (IPv6 traffic via VPN) if OpenVPN correctly pushes a certain value to the server. This is what the relevant config lines look like: push-peer-info setenv UV_IPV6 yes 'UV_IPV6 yes' is a variable that is set to 'yes', basically: yes, gimme IPv6 push-peer-info sends the server information about the client. This includes: OS version and OpenVPN client release, your router's MAC address and of course the UV_IPV6 variable that tells the server to give you an IPv6 address. This last part is problematic and has already led to problems for AirVPN users: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/556 I've run into this issue myself when I tried to get AirVPN running on Linux using the NetworkManager interface (present in virtually every distro out there). It's confusing because it seems to work but in reality it doesn't. You do get a connection, except without IPv6 forwarding. It's no surprise people encounter this: Why would one really need to install your client if the preinstalled GUI manager has worked fine before? Nobody knows the intricacies. Not even those who reported the issue to the correct place above! *drum-roll* and the problem is: NetworkManager. Really. NetworkManager is crippled in that it DOES NOT support many of the OpenVPN features. The combination of push-peer-info + setenv is one of them. The variable is not set upon connection -> VPN connects to the server -> The server does not see UV_IPV6=yes -> The server only setups IPv4 for the client. Yes, THIS IS A SECURITY ISSUE. According to Google, 32% of users have IPv6. Here come you, an AirVPN user with IPv4 and IPv6 on Linux, using NetworkManager. It seems to connect. You quickly check a website to see your IP and see that you indeed got a new IP (IPv4) after connecting to the VPN. Maybe the website doesn't show IPv6 at all, or the user doesn't pay attention to the fact this long and cryptic IPv6 didn't change or maybe the user did not yet have IPv6 and it was enabled later by the ISP... And there the user goes to surf online with half his ass naked: IPv4 is properly routed through AirVPN but IPv6 is still going through his real ISP. This must be changed. IPv6 must be the default. Do not leave a chance to expose users. When this change is applied, both config lines will be rendered obsolete and as a bonus, the clients will no longer unnecessarily send their internal MAC addresses to the server, which can be used too: - https://threatpost.com/fbi-mum-on-how-exactly-it-hacked-tor/117127/ | https://www.theregister.com/2018/02/24/tor_fbi_hacking_appeal/ - https://web.archive.org/web/20180923231303/https://blog.owenson.me/analysis-of-the-fbi-tor-malware/ Finally if you feel there's someone who really wishes to not use IPv6 via Air: reverse the config. Make it an explicit UV_IPV6=no to opt-out. Security must be the default. Thanks for reading. I really hope this change to be introduced soon. PS: Can someone login at the Freedesktop bug tracker above to tell these people that it's fixable? I don't have an account PPS: You can see what push-peer-info sends if you set verbosity to 4: "verb 4" in the config Tags: IPv6 not working AirVPN Linux config openvpn

Hi, Is it possible to use ChaCha20 if I'm using the Gnome Network Manager OpenVPN wrapper? If so, how do I do it?

When trying to add a .ovpn to Gnome network manger with ipv6 enabled (Linux | >=2.4 | UDP 53 Entry 2 | IPv4 & IPv6 (connect with IPv6) | continent > America) It gives the error seen in the Attached file The VPN Plugin failed to import the VPN connection correctly configuration error: invalid 1th argument to 'proto' (line 23) With line 23 being proto udp6 OS Info System: Kernel: 4.19.7-103.current x86_64 bits: 64 compiler: gcc v: 8.2.0 Desktop: Budgie 10.4-85-g36667bcb Distro: Solus 3.9999 Is this something wrong with the Config Generator or should I contact Solus support and try to debug there

Eddie client not starting up in Gnome. Runs well on Cinnamon on the same Debian system. Here the output: https://pastebin.com/QqEEFczQ some info with the help of reportbug: Package: airvpn Version: 2.12.4 System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=es_AR:es (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages airvpn depends on: ii curl 7.52.1-5 ii gksu 2.0.2-9+b1 ii libmono-system-core4.0-cil 4.6.2.7+dfsg-1 ii libmono-system-windows-forms4.0-cil 4.6.2.7+dfsg-1 ii mono-runtime 4.6.2.7+dfsg-1 ii mono-utils 4.6.2.7+dfsg-1 ii openvpn 2.4.3-4 ii stunnel4 3:5.39-2 airvpn recommends no packages. airvpn suggests no packages. -- no debconf information

I'm trying to connect to AirVPN under Arch Linux via NetworkManager/OpenVPN. It connects successfully (it shows a padlock), but if I go to http://ipleak.net/ I can still see both my ISP public IP and my ISP DNS server. I followed this guide (even if it's for Ubuntu). You can find the relevant logs from the "journalctl" command in the attachment.