Staff

Hello! We're very glad to inform you that a new 1 Gbit/s server located in Singapore is available: Triangulum. The AirVPN client will show automatically the new server, If you use the OpenVPN 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. Just like every other Air server, Triangulum supports OpenVPN over SSL and OpenVPN over SSH. As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses. Do not hesitate to contact us for any information or issue. Kind regards and datalove AirVPN Team

Hello, if you run Windows 10 "Creator" please see https://airvpn.org/topic/22650-windows-10-creator-update-airvpn-dns-slow/ Kind regards

We need to partially fix the support team statement here, we're sorry. Some of the data you enter, including the name, but NOT including the credit card number, is transmitted by the credit card processor to the Air management only (and not to employees or other persons, obviously). Kind regards

DNS leaks on GNU/Linux are impossible because they do not exist. A DNS leak is a DNS query sent in clear text (not in the tunnel) against the custom settings of the machine. It is a definition specifically created for Windows, which does not have a DNS implementation (it lacks the concept of global DNS so it sends out DNS queries to any DNS server of any network interface, even in random order in latest Windows 10 "Creator") and it makes no sense to extend it on systems with a proper DNS implementation and which respect settings. That said, we see that you already found a possible reason for the issue (which is quite a different thing than a DNS leak). Please update this thread at your convenience to report whether it solved the problem or not. Kind regards

Hello! The same base frequency is not by itself an issue provided that you use different channels that do not overlap the slice frequency. Each channel has normally a 20 MHz slice frequency. Unfortunately every channel overlaps with "near" channels, so if you experience issues you might need some trial-and-error procedure. However, the problem is treated here for a more scientific approach. Also, some useful tools are suggested. You can find additional articles facing the problem more properly for your country (the example article is specific to UK) through a web search engine. http://www.expertreviews.co.uk/networks/1401371/how-to-extend-wi-fi-range-increase-speed-and-fix-problems/page/0/1 EDIT: an additional nice article https://www.howtogeek.com/197268/how-to-find-the-best-wi-fi-channel-for-your-router-on-any-operating-system/ Kind regards

Hello! We're very glad to inform you that a new 1 Gbit/s server located in the United States is available: Aquila. It is located in Fremont, California. The AirVPN client will show automatically the new server, If you use the OpenVPN 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. Just like every other Air server, Aquila supports OpenVPN over SSL and OpenVPN over SSH. As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses. Do not hesitate to contact us for any information or issue. Kind regards and datalove AirVPN Team

Hello! Can you please try again now? Kind regards

Hello! Please open a ticket. from your description something went wrong apparently. Kind regards

Error in the entries of the db you're querying. Kind regards

Hello, nslookup is a little tool that queries a nameserver. To frame correctly the problem you need to know how Windows DNS implementation is faulty. Windows never had a global DNS concept (source and core reason of the "DNS leaks") and things got worse with Windows 10, which started to query all the nameservers of all network interfaces at once and resolve the name with the first which answered. Windows 10 "Creator" features an additional deterioration of the already rickety DNS implementation. Windows 10 Anniversary Update changed the way DNS works. It used to resolve a qualified name using all available adapters and IP addresses in parallel, now it still resolves names using all available adapters but in sequence, beginning with random adapter and waiting for the answer of each of them. You can easily see how the above implementation will not work correctly in a variety of situations, including a system which is connected to a VPN with internal name servers and which does not want DNS queries outside the tunnel ("DNS leaks"), for example with the "block-outside-dns" directive of OpenVPN (emulated by Eddie for Windows to prevent DNS leaks, for example). Lowering the metric of the tun adapter appears to be the correct solution at the moment. We don't know how the PIA software client deals with DNS leaks because it's a closed source software but from the description the observed behavior is just a rudimentary or clumsy DNS leak prevention which is not as effective as the one implemented in Eddie or in OpenVPN "block-outside-dns" by ValdikSS. For additional information please see also: https://airvpn.org/topic/22650-windows-10-creator-update-airvpn-dns-slow Kind regards

Hello! It may have some different meanings, which anyway do not change the outcome (server not accessible). A line might be saturated by a flood attack exceeding the upstream port(s) capacity, an IP address could be unreachable, etc. In this specific case our 1 Gbit/s port has been suddenly capped without explanation to 100 Mbit/s and we put the server down with the mentioned reason while we wait for a resolution of the problem by the datacenter (which has been of course timely warned about the issue). Kind regards

Absolutely not, we confirm once again that the problem was never on our side. Not only for logical inferences, because such a gigantic problem would have caused a massive amount of complaints by the 15000 users that at any given time are connected to our servers, but because your own description clearly shows that the problem is in your local network segment or local equipment. Kind regards

Hello! We're very glad to inform you that five new 1 Gbit/s servers located in the United States are available: Antlia, Octans, Pavo, Sagittarius and Scorpius. They are all in Atlanta, Georgia. The AirVPN client will show automatically the new servers, while if you use the OpenVPN 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. Just like every other Air server, these new servers support OpenVPN over SSL and OpenVPN over SSH. As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses. Do not hesitate to contact us for any information or issue. Kind regards and datalove AirVPN Team

Hello! DNS leaks do not exist in GNU/Linux. In Ubuntu 17, NetworkManager might be configured to modify frequently resolv.conf and overwrites changes made by Eddie. Make sure to disable this feature by adding in /etc/NetworkManager/NetworkManager.conf the following line in the [main] section: dns=none The above should solve the problem. Kind regards

That's the problem. Please do not specify such route outside the VPN. Local addresses traffic is already not tunneled, obviously, and adding those exclusions on Eddie "Routes" window will create an inconsistent route which will actually make traffic "looping" to your local devices. Kind regards

DNS leaks do not exist in GNU/Linux. In Ubuntu 17, NetworkManager might be configured to modify frequently resolv.conf and overwrites changes made by Eddie. Make sure to disable this feature by adding in /etc/NetworkManager/NetworkManager.conf the following line in the [main] section: dns=noneKind regards

Hello! If the problem persists please try the following setup in Eddie (preferably 2.12.4): - untick "Check if the tunnel works" in "AirVPN" > "Preferences" > "Advanced" - untick "Check Air VPN DNS" in "AirVPN" > "Preferences" > "DNS" - untick "Enable Pinger / Latency tests" in "AirVPN" > "Preferences" > "Advanced" - enable Network Lock Please feel free to keep us posted. Kind regards

Hello! EDIT: Eddie 2.13.2beta automatically lowers the tun/tap interface metric to fix the problems caused by the wrong DNS implementation by Microsoft. If you run Windows Creator please upgrade to Eddie 2.13. to solve the problem. https://airvpn.org/topic/13002-experimentalbeta-release/ === EDIT: After a deeper investigation the workaround published in this post might be not proper. If it does not work successfully for you, please consider to lower the metric of the tap adapter: https://airvpn.org/topic/22650-windows-10-creator-update-airvpn-dns-slow/page-3?do=findComment&comment=61332 Temporary workaround, until we release an update of Eddie 1. Disable IPv6 Control Panel\Network and Internet\Network Connections, Properties of your real (not TAP) network interface, uncheck Ipv6. 2. Disable SmartNameResolution Run this .reg file: https://airvpn.org/repository/DisableSmartNameResolution.zip Explanation The same issue occurs also on plain OpenVPN 2.4 with directive block-outside-dns From https://sourceforge.net/p/openvpn/mailman/message/35789733/ Windows 10 Anniversary Update changed the way DNS works. It used to resolve qualified names using all available adapters and IP addresses in parallel, now it still resolves addresses using all available adapters but in sequence, beginning with random adapter. This interferes with how --block-outside-dns currently works. Sometimes OS chooses VPN TAP adapter and things work as intended, sometimes the other adapter and user have to wait until DNS request times out and name resolution goes via VPN DNS. This behavior introduces significant lag for web browsing. Eddie uses the same approach than ValdikSS "block-outside-dns" directive of OpenVPN: it blocks DNS query with WFP filters. With Windows 10 Creator build (1703) DNS resolution waits for the timeout of IPv6 resolutions (blocked by Eddie) and non-tunneled resolutions (also blocked by Eddie to prevent DNS leaks). This issue will be addressed shortly by a new Eddie release. Kind regards

In this case you're probably right, we will re-check. It is possible that Air privacy and data protection legally responsible person has deliberately forced non-persistent cookies to remain in full compliance with the privacy mission and the "cookie Directive" of the EU. If so, this setting will not be changed. Kind regards

Hello, it's expected and intended if you have set your browser to delete cookies at the end of a session (which is a good idea). Kind regards

https://airvpn.org/topic/22665-kaspersky-2017-patch-e-released/ This should definitely fix any Kaspersky problem with OpenVPN usage. Kind regards

Yes, tick "Show All" in the "Servers tab" first. When "Show all" is ticked Eddie will ignore any white and black list, so that you can have them ready to be restored with a single click. Kind regards

Hello! You have various options. Pick the most appropriate one for your case. 1) Run one of the many "kill switch" programs. Make sure to pick one that is compatible with OpenVPN and remember that the protection provided by such programs is low and leaks can occur. 2) Use Network Lock and enter in Eddie field "Allowed addresses" in "AirVPN" > "Preferences" > "Network Lock" all the IP addresses of the game servers you connect to (if the game requires peer to peer connections with other game clients without passing through the game servers this solution is not applicable). 3) Define your own firewall rules. Kind regards

That's a "non-problem". Just forward remotely a random port from your account port panel and configure your Bitcoin client to listen to that port. Important note: do not remap the remotely forwarded port to a different local port (in this case it would not work properly due to how Bitcoin works). Kind regards

Hello! In your case, probably the most straightforward solution is just defining a white list will all and only the "good performance" servers you have found out from your node. You can define a servers white list in the "Servers" tab of Eddie (the Air client software). Eddie will pick servers included in the white list only. Kind regards