Staff

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

Hello! Can you please send us a screenshot of your DD-WRT OpenVPN configuration web page? What is your router model? Kind regards

Hello! We're sorry, the referral program is momentarily closed for new referrers, it will be re-opened in the next weeks, after we have changed several pieces of software pertaining to accounts handling and more in our system. Kind regards

Hello! OpenVPN over PPTP should pose no problem with our servers configuration and push. About DNS, if your ISP DNS is public, from your Windows systems you can tunnel DNS queries through our servers by setting the ISP DNS IP addresses in the tun interface (TAP-Win32 Adapter), while on Linux systems you can simply force them as first nameserver(s) in /etc/resolv.conf In this way your ISP DNS servers will receive queries from our servers, not from your system. Kind regards

CBS and Pandora are not working anymore from Crucis. Could you check please ? Best regards Hello! Thank you for having notified us about the problem. We are investigating. Kind regards

Hello! The problem was caused by momentary failure of our secondary frontend caused by the datacenter provider. Now, if you have in your hosts file the line: 85.17.207.151 airvpn.org you force resolution of airvpn.org to the secondary frontend. In order to allow your system to access the primary frontend in case of failure of the secondary (and viceversa), keep in your hosts file the lines: 85.17.207.151 airvpn.org 212.117.180.25 airvpn.org so that your system will first resolve airvpn.org to 85.17.207.151 (secondary frontend). In case of failure your system will resolve airvpn.org to 212.117.180.25 (primary frontend) transparently in a matter of a few seconds. Both frontends are absolutely identical, since they get data from a clustered database which resides in our backend servers. If you don't keep any line in your hosts file, airvpn.org will be resolved according to DNS (currently 212.117.180.25). Kind regards

Hello! We had a minor problem in one of our frontends which caused an approx. 2 minutes inaccessibility to the web site (only from that frontend). Kind regards

Hello! Ok! Kind regards

Hello! Performance reasons. Kind regards