Staff

blknit wrote: Hello! Thanks. Can you please also check that ufw is disabled, or its status? Kind regards AirVPN admins

blknit wrote: Hello! Probably you have already considered the following, anyway: according to your network configuration, it may be necessary to enable IP forwarding on your box. Usually IP forwarding is disabled by default in the kernels of the distros,, and surely it is disabled in Ubuntu 11.10. You can do that, in order to test, on the fly: echo 1 > /proc/sys/net/ipv4/ip_forward or sysctl -w net.ipv4.ip_forward=1 Looking forward to hearing from you. Kind regards AirVPN admins

balthazett wrote: Hello! Just tested uTorrent running in a Windows client connected to Vega. It works just fine. We tested DHT, connection to some public trackers, initial seeding, dl/ul. Results are satisfactory and consistent with those of any other server. Perhaps something in your configuration blocking Vega IP addresses in uTorrent? Kind regards AirVPN admins

@boom Hello! Can you tell us which version of Windows and .NET framework you're using? If you can connect through the OpenVPN client, the OpenVPN installation is ok. Can you confirm that you're able to connect to the servers with OpenVPN (we are unsure from your message)? Feel free to give as many information as possible, so that the client programmers can support you with more accuracy. Kind regards AirVPN admins

blknit wrote: Hello! Thank you very much for those tests. They show that the problem is not on the VPN server side. We must concentrate on Linux distros. What version of Ubuntu and Arch are you using? Kind regards AirVPN admins

@balthazett Hello! Vega server has a 1 Gbit/s dedicated port, so a 30% usage of Sigma is the equivalent of just 3% usage of Vega. The wrong geolocation of Vega is a Google mistake. Other USA services correctly see Vega IP as from the USA (Pandora, Hulu etc.). We'll investigate on the issue you report about uTorrent connections and keep you posted as soon as possible. Thank you for your feedback! Kind regards AirVPN admins

@2394john Hello! Before proceeding further, can you please test if ports are reachable in the host? For example, if you connect the host to one of the VPN servers, run a torrent client in the host (outside Wine, for example Transmission) and have it listen to port 43612, is it reachable? Just to ascertain or rule out whether it is a problem in TUN/TAPWine port forwarding. It has been possible to determine that the other pf problem reported in the forum is not related to the servers through a particular simulation (however, to perform the simulation we need your authorization, please contact us in private if interested). Looking forward to hearing from you. Kind regards AirVPN admins

DonkNet wrote: Hello! Very well! Glad to hear that. Please do not hesitate to contact us for any further information. Kind regards AirVPN admins

DonkNet wrote: Hello! You don't need to do anything, just like with any other program. Just make sure, as usual, that you launch irssi or mIRC *after* the connection to the VPN servers has been established. Once the connection is established, all the traffic is routed through the encrypted tunnel, no need to configure any application. Please do not hesitate to contact us for any further information. Kind regards AirVPN admins

triad575 wrote: Hello! We have checked that port forwarding works correctly. Which server do you connect to? At your convenience, please feel free to contact us in private so that we can run simulations exactly with your account configuration (to do that, we need your explicit authorization). On Windows 7, the built-in firewall may keep different configurations for different networks. When you enter the virtual network, it will be correctly considered a completely new one. We have noticed that Windows 7 firewall, by default, blocks incoming connection for eMule, even if it is an authorized application on other networks. You should please check the behaviour of the firewall in the VP Network and make sure that eMule is not blocked there: we have had some similar cases in the past. Looking forward to hearing from you. Kind regards AirVPN admins

allanmills wrote: Hello! Ok and thank you. Please feel free to send us the requested information if you wish a deeper investigation on the issue. Kind regards

triad575 wrote: Hello! Ok, we are going to check your ports for you to make sure everything is ok on the server side. In the meantime, can you tell us your OS and which (if any) firewall you use? Kind regards AirVPN admins

triad575 wrote: Hello! Can you please check that eMule listens and responds to the correct ports? Launch eMule, make it "connect", then run a port scan on the TCP port you have configured for it. You can quickly do that even with this tool: http://www.t1shopper.com/tools/port-scan When the web page opens, it will automatically detect your VPN exit-IP address. Type in the TCP port and click "scan". If everything is ok, you will receive the message in red " is responding on port ". Kind regards AirVPN admins

@triad575 Hello! We have checked and your account has no forwarded ports. In order to forward ports: - log in the website - pick menu "Member"->"Forwarded port" - choose a port number (or let the system pick random ports for you with the "Auto" option) and click "+" (the green + symbol) to add, and "-" (red) to remove a forwarded port. Take note of the port numbers. If you use the AirVPN client for Windows, you can do the same by right-clicking the dock icon and selecting "Ports". In this case disconnection and reconnection to the VPN servers may be necessary to update forwarded ports. After that, configure your eMule client to listen to the same ports you have forwarded. Kind regards AirVPN admins

triad575 wrote: Hello! When you are connected to the VPN, it does not matter that you forward those ports on the router, but it's important that ports used by emule (which must be configured from emule prefs & options) match with the ports you have forwarded on the VPN servers. Kind regards AirVPN admins

blknit wrote: Hello! Can you please send us the kernel IP routing table (netstat -nr) and the status of all your interfaces (ifconfig -a) when you are connected to a VPN server and you have both tun0 and tun1 (feel free to delete privacy weakening info)? Kind regards AirVPN admins

@blknit Hello! Just checked that port 17019 is correctly forwarded for your account and that port forwarding on Omicron works as expected. Are you running any software firewall on your Linux box? Kind regards AirVPN admins

andla wrote: Hello! OpenVPN runs under Windows (Windows 2000 or later). You can setup either a server or a client on your Windows VPS. Anyway you might seriously consider a Linux or *BSD solution to run an OpenVPN server. Kind regards AirVPN

triad575 wrote: Hello! Please make sure that you remotely forward ports and that you configure your client to use those same ports. In order to forward ports, login and pick menu "Member"->"Forwarded port". Please do not hesitate to contact us for any further information. Kind regards AirVPN admins

Hello! Thank you very much to you all for the wonderful feedback, we appreciate it a lot and we'll keep on improving the service! Kind regards AirVPN admins

@allanmills Hello! The logs seem ok. Please, can you send us the outpout of the following commands, before and after a VPN connection? netstat -nr route -n ifconfig tap0 ifconfig wlan0 ifconfig eth0 cat /etc/resolv.conf While you are connected to the VPN server, can you send any packet out? Does DNS resolution work? Try: ping 72.14.203.106 ping google.com and let us know. Also, does anything change if you try the connection directly with OpenVPN (assuming you haven't already done so), for example: sudo openvpn air.ovpn Looking forward to hearing from you. Kind regards AirVPN admins

seranoxa wrote: Hello! Vega and Sigma are both located on the West Coast. You might also try Lyra (Netherlands), which is in a datacenter with a good peering with several USA based providers. Kind regards AirVPN admins

@allanmills Hello! Can you please send us the OpenVPN connection logs when you try the connection on the open WiFi network and on your mobile broadband card? Have you tried to connect to port 53 too? Kind regards AirVPN admins

gward wrote: Hello! There are some methods to do that. We would recommend to set appropriate firewall rules for uTorrent (or any other program), probably it is the "cleanest" solution. An alternative is using small programs like VPNLifeGuard, VPNCheck or VPNetMon. They will forcefully kill the programs you tell them if the VPN connection is not active, or even if it accidentally drops. Kind regards AirVPN admins

EDIT: PROBLEM SOLVED - LYRA UP AND RUNNING Hello! Server Lyra (Netherlands) is facing serious connectivity problems and we have been forced to put it down. In the last few hours cable and switch port have been replaced. Unfortunately these actions only mitigated the problem without solving it. It seems there's a connectivity issue in (some part of) the datacenter network, a technician is investigating. We will keep you posted. Kind regards AirVPN admins