Staff

Hello! Thank you for the information. We confirm we have still some issues with port forwarding on Cygni. We're working on it in order to detect the problem. Kind regards

Hello! We have received some excellent feedback from California, for example: https://airvpn.org/index.php?option=com_kunena&func=view&catid=3&id=5296&Itemid=142#5587 Kind regards

Hello! If you capture traffic on the tun/tap adapter you can see unencrypted packets. If you capture traffic on the physical interface you must see all encrypted packets to/from the Air server, except those to/from your internal network, otherwise there's something wrong: check your routing table after the VPN server push. Kind regards

Hello! Our OpenVPN servers don't listen to port 1194, they listen to ports 53, 80 and 443 (TCP and UDP). Kind regards

Hello! Ports 137, 138, 139 and 445 are closed and clients within the virtual network can't communicate with each other (inside the network), so your shared resources can't be accessed, at least through the VPN. In general, a client on the VPN has all ports closed, in order to open them the client owner must explicitly forward ports remotely. There is a way to overcome this security limitation, it requires remote port forwarding with remap to the above mentioned local ports. Just don't do it and you are secure on the VPN side. Kind regards

Hello! We're confident about that: the provider has been thoroughly informed about our activity. Of course things in real life may be different, we rely both on the correctness of the provider and on our customers' respect of AirVPN Terms of Service. Kind regards Hello! We have not detected any problem with the server during these first days. We would be more than glad to receive any feedback especially from Asian customers about this server. Kind regards

Hello! We're very glad to inform you that a new 1 Gbit/s server located in Sweden is available: Cygni. The AirVPN client will show automatically the new server, while if you use the OpenVPN client you can generate all the files to access it through our configuration/certificates/key generator (menu "Member Area"->"Access without our client"). The server accepts connections on ports 53, 80 and 443 UDP and TCP. 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 admins

Hello! Assuming that your RDP server is running behind an Air server, you can reach it from the Internet at : The listening port needs to be remotely forwarded. Please note: - the entry-IP and exit-IP of our servers are different - the forwarded port may be different form the RDP server listening port, as long as you remap it to the correct local port For example: - your RDP server runs in a machine where an OpenVPN client is connected to an Air server - the RDP server listens to port 3389 - the remotely forwarded port is 32604 remapped to local port 3389, Then you can reach the RDP at: :32604 Alternatively, you can change (if possible) the RDP server listening port to 32604 and NOT remap 32604 to any local port. Kind regards

Hello! Some hints and hopefully possible solutions: http://forum.vuze.com/thread.jspa?messageID=187588 Kind regards

Hello! Yes, you are right, that was Pegasi with another provider who could not handle the stress of copyright alleged infringement notices and/or did not respect its contract with us. Our totally neutral policy involves an ongoing, perpetual "war" against copyright trolls in Germany and in the USA. Furthermore, if the provider is unable to respect the agreements with us, we leave it. We'll be looking for additional North America locations in the near future. Kind regards

Hello! It is an IP geo-location mistake by that website. Sirius is in Virginia (USA). Kind regards

Hello! The TOR Browser Bundle is useful to you to launch the TOR proxy, but of course you can use any other bundle you like. TBB also includes Aurora. After the TOR proxy is running and has established a circuit, connect OpenVPN over the TOR proxy according to the instructions, finally browse with any browser NOT configured to connect over a proxy (not Aurora, therefore). The browser (and any other program) will transparently connect over OpenVPN which is connected over the TOR proxy, therefore you have a connection over OpenVPN over TOR. When you have that setup use a browser not configured to connect over a proxy in order to connect it over AirVPN over TOR. Kind regards

Hello! Can you please send us your client logs when the issue occurs? Kind regards

Hello! Yes, of course, that was clear. The instructions in the previous admin post were meant exactly for this purpose. Do not use the TOR browser because if you use it with the above setup it will be tunneled over the same proxy OpenVPN connects to and the final host will see a TOR exit-node IP address. Just use any browser which is not configured to connect to a proxy so that it will connect over OpenVPN over TOR. The final host will see the Air server exit-node and the Air server will not see your real IP address. The TOR nodes will see encrypted by OpenVPN traffic. Kind regards

Hello! You can find here the TOR Browser Bundle in the TOR Project website. It requires no installation (just decompress it), so it should be perfect for you, especially if Ubuntu-lucid is on a pen drive. Direct link: https://www.torproject.org/download/download-easy.html.en Once you have it, your goal can be achieved with connections over OpenVPN over TOR. Instructions are available here: https://airvpn.org/tor Kind regards

Hello! Anyway, your key and certificates are unique, the same for every server. Additionally, you can download all the possible configuration files in just one hit with our configuration generator (just select simultaneously all the servers, ports and protocols). Kind regards

Hello! Yes, please access the configuration generator and generate the appropriate configuration. Download the archive, copy and paste the .ovpn file into the OpenVPN configuration directory, just like you did before, on your host. Kind regards

Hello! Do you have the rules that are specified in step 9 of our guide? Allow IP In/Out From In [Loopback Zone] to MAC Any Where Protocol Is Any Allow IP In/Out From MAC Any To In [Loopback Zone] Where Protocol Is Any where [Loopback Zone] is [127.0.0.0 - 255.0.0.0] If you use the TOR Browser Bundle: - Proxy Type: socks - Proxy IP: 127.0.0.1 - Port: 9050 Also, connection over a proxy can ONLY be TCP. Remember to select a TCP port. Kind regards

Hello! Correct, in this case you need only one account. Kind regards

Hello! As you probably know, you can check anytime the servers status here: https://airvpn.org/status Kind regards

Hello! You can use the Air client both on your host and guest OS. Please note that you can't use the same account for two simultaneous connections. You need to know the proxy type, IP and listening port of the proxy you're using. You can discover them from inside the proxy interface and its documentation. Kind regards

Hello! We can confirm we have plans for one additional Swedish server. However we are currently unable to provide you with a date. Please note that currently Serpentis bandwidth is permanently under usage, with only 25% peaks. Kind regards

So to acheive this I will: 1. Now install the new windows VM 2. Then download and install Tor and the windows AirVPN client on the VM and then am assuming Im good to go pretty much 3. OR are there any special settings to make the "Tor over VPN part of the connection on normal windows" (HM its called right?) routes to the VM correctly? Hello! That's correct, there are no additional requirements. However, the previous admin post forgot to specify an important detail, that is the VM must be connected to the host via NAT in order to render the setup effectively working (i.e. no bridging). This is the default configuration in VirtualBox (just make sure that "NAT" is selected in "Settings"->"Connections") so you should not worry about it, the virtualization program will take care transparently of all NATting. Correct. About point b, remember to configure OpenVPN to connect to an Air server over your TOR proxy. The configuration generator or the Air client will take care of it, just select the appropriate options for Proxy Type, Proxy IP and Proxy Port. The rules should already allow these type of connections because, when you connect OpenVPN over TOR, OpenVPN will communicate with 127.0.0.1 (your local proxy address), which is explicitly allowed in some rule. Additionally remember, when Comodo will prompt you about that, to allow any communication from/to the Virtual Machine (i.e. take care not to block the virtualization program NAT). If you have any issue on this matter please do not hesitate to contact us, a Comodo expert will support you. Kind regards

Hello! About Windows and Comodo yes, absolutely, the recommended rules prevent DNS leaks. About Linux, it does not suffer DNS leaks, which is a typical Windows problem basically related to the fact that Windows lacks the concept of global DNS. So just set your favorite DNS servers (for example by editing /etc/resolv.conf if you don't have resolvconf installed) and OpenVPN will tunnel them. Only obvious exception: nameserver in which case DNS queries will be sent to your router and the the router will send them out unencrypted. Kind regards

Hello! Currently the infrastructures in Singapore and Italy do not provide a 1 Gbit/s dedicated port with 1 Gbit/s lines (even shared, best effort) as a viable solution for our requirements. They just can't provide enough traffic. About the Netherlands servers, the old 100 Mbit/s have a dedicated line, which is burstable up to 200 Mbit/s, while the 1 Gbit/s servers have a dedicated 1 Gbit/s port connected to multiple shared lines capable to provide up to 1 Gbit/s 95% of the time. Since the 100 Mbit/s NL servers are in a different network than the Gbit NL servers, we prefer anyway to keep them for access redundancy. Kind regards