Staff

Hello, as suggested by zsxawerdu the directive "route-delay 5" solves the problem. Fedora 21 users can enter that custom directive on their Eddie clients, or on the Configuration Generator. We're considering whether to put a "route-delay" directive as default (for Linux only) in the next client release and in the Configuration Generator. Kind regards

Hello, no problems, we understood. Yes, this setting (Network Lock enabled and active) is 'sticky'. What you describe is an anomaly on your system that we would need to reproduce to understand why it happens on your system, if there's some hidden bug in the client etc. Kind regards

Hello! Just for readers information, we have the following countries list where Bitcoin usage is allegedly forbidden (of course such laws are very difficult to be effectively enforced due to how Bitcoin software works). If you have additional information feel free to share. Bangladesh Bolivia Ecuador Iceland Kyrgyzstan Kind regards

Idealy I want network lock to stay active at all the time when I'm not connected to an airvpn server but having the eddie client running. Hello! Yes, and that's exactly what happens. If you are disconnected from a VPN server but Eddie is not shut down, Network Lock remains active. If Eddie is killed without grace or crashes Network Lock remains active. In the moment you shut down Eddie, we have no rights to interfere with your system and we have no will to make invasive software that permanently modifies your system settings. Routing table, DNS and all previous firewall rules will be restored. Kind regards

Is this something I have to do manually, or is it done by the client? If I have to do something manually, how do I do this? I can find the pf.conf in the airvpn directory that has all the rules in it, but how do I load/activate it so eddie can work with it? on a side note, when I activate network lock and restart my machine, connections seem to be blocked until airvpn connects to a server, but as soon as I disconnect from a a server network lock is shown as not active. this setting should be sticky, right? thx for your help Hello! Everything is done automatically. The behavior you detect is anomalous and we can't reproduce it: Network Lock works properly in our test systems. We don't even have any warning from other OS X customers about this issue. We'll keep investigating. On your side, make sure that when you enable Network Lock you also activate it by clicking on the big button on the "Overview" window. The token must become green. On the contrary, if you shut the client down properly, it's correct that Network Lock is de-activated. Network Lock, however, remains active if the client is killed or crashes, which is good for security. Kind regards

Hello! We ceased support to RC4, that's causing the problem in XP with the old client. However, please note that Air client 1.x series is obsolete. Upgrading to client series 2, codename "Eddie", will solve the problem even on XP SP3. Also keep in mind that XP is discontinued and, as you rightly say, switching to more modern Operating Systems is an option to be seriously taken into consideration. Kind regards

Hello, PPTP has not been taken seriously since years and years ago and we think that it does not deserve any consideration, unless security is not required. Maybe fifteen years ago, when several vulnerabilities were not yet discovered, it spread out considerably due to the fact that Microsoft strongly supported it. But we're talking about 1999, "ages ago" in computer science and networking. Some more details here: https://en.wikipedia.org/wiki/Point-to-Point_Tunneling_Protocol#Security As you can see, core problems are the protocol authentication implementations. By the way, it remains as an historical curiosity and a solution with quick deployment when security and other factors are not required. Kind regards

Hello, this guide is quick and effective and it should be easily applicable to a wide variety of Linux installations. http://xmodulo.com/internet-connection-sharing-iptables-linux.html Kind regards

Hello! What are your Operating System and the software you run to connect to our service? Kind regards

Hello! Please see the last part of this message: https://airvpn.org/topic/12671-upgrades-for-eddie/?do=findComment&comment=21663 About latency: https://en.wikipedia.org/wiki/Latency_%28engineering%29 - in particular https://en.wikipedia.org/wiki/Latency_%28engineering%29#Packet-switched_networks Kind regards

Hello, your account is authorized to access every VPN server and as usual it can establish three simultaneous connections from different devices to different VPN servers. Please feel free to publish client logs pertaining to some failed connection. Kind regards

Hello! We don't experience any problem with 2.8RC3 on OS X 10.10. Can you please make sure that you're running RC3 (select "AirVPN" -> "About" menu item)? Can you please provide more details? Is pf running? If so, which rules does it have after you have enabled and activated Network Lock? Kind regards yes, I'm running RC3. I tried with PF or automatic. In both cases after disconnecting from airvpn servers I do have a network lock active confirmation on the overview page of the eddie client. However I can connect to the internet via browsers or apps without any problem. Hello, in this situation, print out pf rules. Open a shell and type the command: sudo pfctl -sr Copy everything and paste into your message. Do you know whether your ISP supports fully IPv6? Kind regards

Hello! We don't experience any problem with 2.8RC3 on OS X 10.10. Can you please make sure that you're running RC3 (select "AirVPN" -> "About" menu item)? Can you please provide more details? Is pf running? If so, which rules does it have after you have enabled and activated Network Lock? Kind regards

Hello, can you please provide a screenshot? We don't notice any problem with Mint 17.1 Rebecca. Make sure that you're really running version 2.8RC3 (run airvpn without arguments from a shell and look at the output). Try also portable version (NOT the portable version with Mono required). Kind regards

Hello, on the other hand, we would recommend that you try 2.8RC3 on Windows as well. Kind regards

Hi, no, not necessarily. We have observed many cases confirming that. In some cases, but not all, re-installation is not necessary, the problem is solved with a reset, including a Winsock sockets catalogs reset (see here for example: https://airvpn.org/topic/8320-solved-connects-but-ip-doesnt-change-on-windows-server-essentials-2012/?do=findComment&comment=8321 ) While these symptoms tend to confirm that it has something to do with the client, and this is a behavior we have been unable so far to reproduce. Would you mind testing Eddie 2.8RC3 to see if it's the same or not? Kind regards

Hello lsat, it looks correct that Gary's client fails and re-tries to re-install the driver because Gary disabled the tun adapter (first message of this thread), so this is not an unexplained problem but an expected behavior and we consider it solved. What we can't reproduce and it seems a unique issue to Gary is the fact that the client needs an ungraceful kill to quit. lsat, which thread are you referring to? About your problem (which we suspect is a different problem than Gary's problem), it might be a corrupt TCP/IP stack, you might try to re-install it in Windows. Kind regards

Hello, of course but this issue is unique to your system at the moment. We can't reproduce it in any way and we have no additional reports to work on. Should you have additional information (such as logs, error messages, system status) do not hesitate to send them to us. Currently your data are insufficient for any deeper investigation. Kind regards

Hello! The problem has been fixed, can you please check now? Kind regards

Hello, what is your download (Operating System and type of Eddie package)? Kind regards

The issue has been addressed in the latest experimental build. Please check it: https://airvpn.org/topic/13002-experimentalbeta-release/

Some latency improvements and the option about when the client downloads servers list have been implemented in the latest experimental build. https://airvpn.org/topic/13002-experimentalbeta-release/

Some latency improvements in the new experimental version, please check it: https://airvpn.org/topic/13002-experimentalbeta-release/ Sorry but the issue about the sleep mode is still under investigation.

The issue has been addressed in the latest experimental build. Please check it: https://airvpn.org/topic/13002-experimentalbeta-release/

The issue has been addressed in the latest experimental build. Please check it: https://airvpn.org/topic/13002-experimentalbeta-release/