Staff

Hello! Probably not, 10.7.0.1 is the DNS address DHCP-pushed by our servers when you connect to 80 TCP. Since Viscosity fails as well, probably it's worth checking something else in your system. Do you have any program which might interfere, such as LittleSnitch? Check also your firewall rules, please. Can you establish successfully connections over TOR alone? Can you please try a connection (OpenVPN over TOR again) to port 53 TCP? Kind regards

Hello! Can you please send us your client logs (while connected to 53 UDP and 443 UDP), just to check if there's packet loss or packet fragmentation? Did you test several servers? Do they ALL provide the SAME performance? Kind regards P.S. We comply to a "no questions asked" refund policy, so if the service does not meet your requirements you still have 3 days to ask and obtain a full refund.

Hello! It's not a DNS issue... apparently you have no connectivity at all when trying to connect over a proxy. Can you please try Viscosity for testing purposes? It's not open source and it's a commercial product, but Sparklabs offer 1 month free evaluation: http://www.sparklabs.com/viscosity Kind regards

Hello! Just after the unexpected disconnection, can you please send us the complete Tunnelblick logs? In order to determine if it's a DNS issue (at least during the 1 min connection...), please send us the output of the following commands (issued from a command shell): ping 10.4.0.1 ping airvpn.org Finally, if you don't connect over a proxy, does Tunnelblick connect fine? Kind regards

Hello! Please right-click on the Air dock icon after the error occurs, select "Logs" and look at the path and filename of AirVPN.xml. Then close the Air client and delete airvpn.xml. The client will re-create it automatically. Kind regards

Hello! Are you trying the connection to a TCP or an UDP port? Kind regards

Hello! It seems that the proxy is not listening to port 9050 (or it is not running). Maybe is it listening to some other port? In Vidalia, open "Settings"->"Advanced" and uncheck the box that says 'Configure ControlPort automatically'. Your SOCKS port will then be 9050. Kind regards

@RaggaMuffin Hello! Please make sure that the torrent client is not "strangling" your line with excessive upload or download bandwidth (if you have an asymmetric line, saturation of upload bw will clog download bandwidth as well). Set your torrent client upload and download limits in order not to exceed 75-80% of your total available bandwidth. Additionally, test different ports and protocols (in particular, try 53 UDP and 80 TCP) just in case your ISP performs port shaping. Kind regards

Hello! Please see this thread: https://airvpn.org/index.php?option=com_kunena&func=view&catid=3&id=7718&Itemid=142 Kind regards

Hello! Thank YOU for sharing! Just out of curiosity, readers can compare your rules with those suggested in our guide "Prevent Leaks with Linux & iptables": https://airvpn.org/index.php?option=com_kunena&func=view&catid=3&id=1713&limit=6&limitstart=30&Itemid=142#2010 Kind regards

Hello! The problem seems to be here; Kind regards

Hello! It is your VPN IP address, it has been DHCP-pushed by our server to your client. About the rest we don't see any clear mistake. Can you check that the iptables rules have been properly created (check with "iptables -L")? Kind regards

Hello! A general solution is not possible, each mistake must be fixed on its own. About the case you're probably referring to, the error was in the Network Zones, in particular see the recommendation in our guide, just in case you have the same mistake. In any other case please send us all we need according to the guide thread. Kind regards

Hello! Please check that the interface name is correct (type "ifconfig" and check that it is tun0, not tun1 or anything else) and that in the iptables rule the names and "debian-transmission" are correct (use the command "ps aux | grep transmission" to check that). What is that 192.168.0.100? Kind regards

Hello! Contrarily to BBC iPlayer, UK Netflix is not accessible from our german servers. You can access it only from our UK servers. Also, we ignore the geographical detection system of Netflix: if the problem persists try to prevent your iOS to send out your real location by disabling location detection (iOS can determine your real location and send it not only from IP address, but also from GPS and surrounding WiFi hot-spots). Additionally, some iOS apps might try (without your consent) to extract your geolocation information from photographs and send them to a 3rd party (example: http://arstechnica.com/apple/2013/02/path-promises-fix-for-new-privacy-liberties-taken-by-ios-app/ ). Kind regards

Hello! We can't see the Network Zones here in the forum, by the way the Network Zones we could see from your e-mail show a mistake which causes the problem. Please check your inbox. Kind regards

Hello! Your Global Rules look fine, can you send us the Network Zones as well? Kind regards

Hello! Exactly! Kind regards

Hello! Can you please make sure that you select a TCP port for the OpenVPN connection? Also, are you running some wrapper/GUI or OpenVPN directly? Kind regards

Hello! Can you please make sure that you have selected a TCP port for the OpenVPN connection and that port 9151 is actually the SOCKS Port (i.e. not the Control Port)? Kind regards

Hello! Probably some abuse from Pavonis, for example a massive amount of automated requests toward Google. We'll keep an eye on it. Kind regards

Hello! Our OpenVPN servers DHCP-push to your OpenVPN client addresses in the ranges here reported: https://airvpn.org/specs Each server can't assign more than 65534 addresses for each listening port (i.e. well beyond the number of clients structural limit that a single OpenVPN server can handle). It's absolutely not a privacy concern, under no circumstance. They are private IP addresses inside our private network and it's just how OpenVPN in routing mode (with a NAT) works. We are curious, why do you think they can imply a privacy concern? Kind regards It's not a a privacy concern on the outside but on the inside of the vpn if a user always has the same 10x address if would be a way to keep track of each user. Hello! How would that be any different from having a different VPN IP at each connection (anyway VPN IP addresses are dynamic)? A malignant VPN administrator can do that in any case: having a static or a dynamic private IP does not change anything, it does not make it any easier or any harder. Kind regards

What a scrap... it's hardly possible to take it seriously. Such a statement must be from a competetive service-provider. In last time there are too many trolls here... Hello! True, Air growth is causing more and more trolls to infest the forum. Most spam is filtered either automatically or by the moderators, anyway we'll harden moderation to maintain the forum to its purpose, i.e. technical support and ideas/information/discussions exchanges between users, customers and administrators. Kind regards

Hello! Does the same problem occur if your router connects to a TCP port? Kind regards

Hello! Our OpenVPN servers DHCP-push to your OpenVPN client addresses in the ranges here reported: https://airvpn.org/specs Each server can't assign more than 65534 addresses for each listening port (i.e. well beyond the number of clients structural limit that a single OpenVPN server can handle). It's absolutely not a privacy concern, under no circumstance. They are private IP addresses inside our private network and it's just how OpenVPN in routing mode (with a NAT) works. We are curious, why do you think they can imply a privacy concern? Kind regards