Jump to content
Not connected, Your IP: 3.22.249.158

Staff

Staff
  • Content Count

    10594
  • Joined

    ...
  • Last visited

    ...
  • Days Won

    1759

Everything posted by Staff

  1. Hello! Your system did not use the VPN server DNS: speedtest.air is resolved only by them. Can you please send us the output of "ipconfig /all" while your computer is connected to a VPN server? Kind regards
  2. Hello! Although unlikely (since all the other servers work fine with your client) can you please check whether it's a DNS problem? http://code.google.com/p/tunnelblick/wiki/cConnectedBut#If_OpenVPN_is_connected_to_the_server_but_you_can%27t_access Kind regards
  3. Hello! When you define that rule, in the "Destination Port" tab of the Network Control Rule just select "A Single Port", specify 53, and tick the "Exclude" box (i.e. the "NOT" Comodo operator). Please note that your real IP address must NOT be visible, regardless of Comodo usage or not, when you're connected to a VPN server. Please send us your client logs if you have this problem. Kind regards
  4. Hello! You need to delete "route add -p 85.17.123.26 mask 255.255.255.255 192.168.67.2 metric 1" To achieve your purpose to prevent leaks in case of unexpected VPN disconnection and prevent any leak while connected, you may set up the appropriate firewall rules in your VM (assuming that it's in bridge mode). You may also consider to change the approach: connect your host machine to the VPN, connect the guest with NAT (instead of bridging). This will allow you to connect multiple VMs with just one Air account (used by the host). Finally, secure the connection with a firewall only on the host. Kind regards
  5. Hello! Yes, that route addition allows OpenVPN client connection to Leonis but prevents any communication inside the VPN. Kind regards
  6. Hello! The logs look just fine. Are the devices which connect to the router forced to use some particular DNS? EDIT: please also check this, just in case: http://www.dd-wrt.com/phpBB2/viewtopic.php?p=680573 Kind regards
  7. Hello! It's very important that you follow step 1. Adding highly customized global rules with the stealth port wizard is not possible. The Global Rules can be added, deleted and edited in the Global Rules tab. The Network Zones can be added, deleted and edited in the Network Zone tab. Again, you should follow step 1. It's just so easy to use Comodo firewall and set rules that most of the doubts come out just because step 1 has not been followed. The rules are exactly as reported in the guide, word by word. A screenshot will show you the very same rules, word by word. Kind regards
  8. Hello! Obviously but unfortunately this is not possible. Anyway, before dismissing Vega we are urging the provider to detect and solve the problem. Kind regards
  9. Hello! It does not seem normal. Do you experience the same with other servers? Did you test a connection on a TCP port? Can you please send us the logs of your client? Kind regards
  10. Hello! That's correct, however please note that you will also lose the ability to communicate with devices in your home network and you will prevent permanently DNS resolution on your computer when not connected to the VPN. Also, be aware that option -p will make the route permanent, so it will survive a reboot. Most importantly, it will prevent any connection to any of our servers. That's normal: each Air server has an entry-IP and and an exit-IP address. The servers accept connections from OpenVPN client only on the entry-IP. In your case, you have the routing table with an exit-IP (Leonis'). Leonis entry-IP is 85.17.123.26. The Air client connects to airvpn.org to allow your login and display the list of servers (only if you have set in your hosts file resolution for airvpn.org), then launches OpenVPN which can't establish a connection (not even if you choose Leonis) because of the routing table. Please check the central bottom box in our web pages (restart the browser if necessary): only if it's green your device is connected. Kind regards
  11. Hello! You can use pfctl. http://www.openbsd.org/faq/pf/config.html Kind regards
  12. Hello! Thank you for the information, we're glad to know that the problem is solved. Can you please tell us if you changed anything in your system? Kind regards
  13. Hello! Can you please make sure that you start Transmission AFTER you have established a VPN connection? Also, can you please test with completely disabled LittleSnitch and firewall? Kind regards
  14. Hello! Please make sure that Transmission listens to the correct port (the port number must match the remotely forwarded port number) and that this port is forwarded both for TCP and UDP (various modern p2p clients use both protocols). Kind regards
  15. Hello! It is opinion of this admin that a pre-configured .cfgx Comodo file containing global rules meant to prevent any leak represents a security risk for our customers and would need anyway to be highly customized (too many variables seem to make impossible to cover all cases). It is also opinion of this admin that a basic knowledge of a firewall is an essential requisite for a person really interested in network security and privacy. The guides and Comodo manuals are perfectly suitable to master all the Comodo firewall free edition features. Our guide is designed precisely to be unlinked to a particular Comodo firewall version: all the rules are reported in text format and care to avoid references to specific menus, options etc. has been used in order to provide maximum flexibility. However we will discuss internally about this option. Kind regards
  16. Hello! The ports are correctly forwarded to you by the server you're currently (at the moment of this writing) connected to. Those error messages are normal if you open ports while you're not running the services which have to listen to those ports. When you open/close a port, you don't need to disconnect and re-connect, but you have to wait some tens of seconds to allow the server to receive and apply the changes. About the UDP red token, please make sure that you have not forwarded on your router that port. If you are sure of that, then it's just a false positive which may occur with UDP. If you have still issues, please do not hesitate to contact us. Kind regards
  17. Hello! We suggest the following solution. Please note that it will work only if you have at least two physical network interfaces in your computer. The PS3 will need to use a LAN cable, so if you have just one LAN card you can anyway connect your computer to your router via your WiFi card, if available. This solution is suitable for Windows 7 and any other Windows system supporting ICS (Internet Connection Sharing) as well. It will work also with XBox consoles and in general with any other device with similar or higher networking abilities. 1) Configure the PS3 IP networking. IP address: same subnet of your Vista system BUT not the same IP address of your router and/or Vista system Subnet Mask: this depends on your home network configuration, usually 255.255.255.0 is a safe choice, anyway if you have issues please try 255.255.0.0 Default router/Gateway: The IP address of your Vista system Primary and secondary DNS servers: IP address of your Vista system 2) Connect the PS3 to your computer via cable 3) Connect your computer to your router via WiFi 4) Connect your computer to an Air VPN server 5) In your Vista system, go to your Control Panel->Network/Internet Setup, locate the TAP-Win32 Adapter V9 card, select its "Properties" and click on tab "Sharing". Enable (tick) the option "Allow other network users to connect through this computer's Internet Connection". In the drop down list under "Home networking connection", select the PS3 connection to the Vista computer LAN interface (probably "Local Area Connection" or similar). 6) Disconnect from AirVPN, then reset the LAN card. In order to do so, the quickest way is selecting your LAN interface (probably "Local Area Connection" or similar), disable it, wait a few seconds and then re-enable it. 7) Re-connect your Vista system to AirVPN After about a minute your PS3 should use your Vista system as a "gateway" and therefore use transparently AirVPN. Kind regards
  18. Hello! Vega problems are getting bigger instead of getting resolved. We will be working with the ISP to determine exactly the nature of the problem which is still puzzling us. If the problems will not be solved within a reasonable period of time we will replace Vega with a new server. In the meantime, it is possible that you will get same or better performance with our Phoenix (Arizona) server Arietis, can you please test it? In order to check status of our server you can browse here: https://airvpn.org/status Kind regards
  19. Hello! Mac OS X is based on UNIX-compliant OpenBSD, which is probably the strongest feature of the OS. The recommended firewall is pf, which is one of the best packet filtering tools currently existing in the world together with iptables. There is no reason for which a Mac user should be intimidated by some of the finest software in the world, don't be afraid, as well as there is no reason for which a Mac user should be afraid of using for real his/her own system, i.e. a UNIX-like system. pf is available by default on OS 10.8 because it is pre-installed by Apple so you will not need any installation. jessez has prepared instructions and ready-to-use script which are Mac OS users friendly: https://airvpn.org/index.php?option=com_kunena&func=view&catid=3&id=1713&limit=6&limitstart=36&Itemid=142#2532 Kind regards
  20. Hello! The logs show that initially you had a packet authentication failure (method is HMAC SHA-160). The failure may be caused by various factors: - high packet loss/latency - WiFi problems (is your computer connected to your router via WiFi?) - a replay attack https://airvpn.org/index.php?option=com_kunena&func=view&catid=3&id=3773&Itemid=142#3784 About the last above point, if your computer is connected to your router via WiFi, can you please tell us which encryption and authentication are implemented? Please try to change server and also try to connect to TCP ports in order to make a comparison. We're looking forward to hearing from you. Kind regards
  21. Hello! Please see step 3: set it to "Custom Policy". Correct. Unfortunately not: you should not block all incoming connections if you wish to use our remote port forwarding system. You need remote port forwarding only if you want some service (a web server, a p2p client etc.) to be reachable from the Internet behind our VPN servers. Please see also here: https://airvpn.org/faq This will define the firewall behavior on an application basis. Nothing wrong, but it will not secure your connection against leaks in case of unexpected VPN disconnection: you will have to set the global rules anyway. Please do not hesitate to contact us for any additional support. Kind regards
  22. Hello! Maybe a corrupt archive? Can you please try to re-generate and re-download it? Kind regards
  23. Hello! As far as we know OpenVPN can't run on a PS3. Therefore you need a gateway, like a DD-WRT router or a computer which connects to AirVPN and shares the connection with the PS3. For additional instructions about the latter case, can you please tell us the OS of the computer which might share the connection? Kind regards
  24. Hello! Please see our previous message to determine the non-Leaseweb servers. You can obtain the IP addresses you need by contacting us through the "Contact us" form (or by using the configuration generator, menu "Member Area"->"Access without our client"), because we are reluctant to publish them in the forum. Kind regards
  25. Hello! You can use any of your favorite torrent clients. It's not necessary. It may be a courtesy to us as it might help us receive less bogus copyright infringement notices. However PeerBlock efficiency is so low that it does not really make a significant difference. Also, please be aware that some PeerBlock blocklists are so badly written that they will block some of our servers as well. First of all, you must never use two firewalls simultaneously. They will interfere with each other with unpredictable outcomes. DNS leaks are not a concern when you do p2p. The real concern is preventing your real IP leak in case of unexpected VPN disconnection. We would recommend you to get rid of any firewall and install Comodo firewall (the free version is just fine), OR to translate the Comodo rules for your favorite firewall (please be aware that it's not possible to do that fully with the Windows firewall). With the recommended Comodo rules you will prevent not only DNS leak, but any leak. Variable latency is normal on the Internet. The best approximation you can obtain with short-time speed tests is with speedtest.air, because the test is performed internally, inside the Air server you're connected to, without relying on another server. Unfortunately we are still unable to find an Asian provider which complies with our requirements about security, privacy, peering, bandwidth and traffic. All these factors together, in addition to privacy legal frameworks, represent a hard selection which cuts out a lot of providers (privacy-hostile legal frameworks force us to discard whole countries in Asia). We are not willing to sacrifice privacy and security for better marketing. Our research anyway is ongoing. Kind regards
×
×
  • Create New...