Jump to content
Not connected, Your IP: 216.73.216.120

Staff

Staff
  • Content Count

    11575
  • Joined

    ...
  • Last visited

    ...
  • Days Won

    2059

Everything posted by Staff

  1. Hello! Is the RDP listening to a port which has been remotely forwarded on our servers? This is necessary to allow incoming connections. You can then reach your remote desktop behind the VPN to : You can also remap the remote port to a different local port for your convenience from your web control panel (menu "Member Area"->"Forwarded Ports"). Kind regards
  2. Hello! About TLS auth: leave it inactive. You imported both the server certificate (ca.crt) and the client certificate (user.crt), right? Do you have the (attempted) connections logs? Kind regards
  3. Hello! Did you already follow the instructions here: https://airvpn.org/faq#p2p If so, please also make sure that uTorrent UPnP and random port at each start are unticked. Please verify that uTorrent listens to the correct port. Kind regards
  4. Hello! Wait, the admin meant the iptables rules for your DD-WRT router, according to the instructions. Kind regards
  5. Hello! It seems that you're trying to run your router as an OpenVPN server. Is it possible to set it in client mode? Also, you need to change the auth mode to server/client certificates and client key. In the archive prepared by the configuration generator you find them with the names ca.crt, user.crt and user.key. While from your message certificates appear to have been pasted, your key does not. You should find a field to insert also your key (user.key). Kind regards
  6. Hello! You can use the same rules with the addition of an unconditional "allow" rule toward port 443, in order to let the TOR proxy communicate in the TOR network. This adds a risk, i.e. letting communications toward port 443 TCP (so https, for example) in any case. In case of unexpected disconnection for example a browser will continue to be able to communicate with https web sites. The "last 3 characters" you refer to are mandatory: they are an integral part of the routing prefix expressed in CIDR notation (accepted by ipfw): http://en.wikipedia.org/wiki/Netmask Kind regards
  7. Hello! We have never arrived to that stage. We first ask technical proof of their claims, which implies a competent, technical and exhaustive explanation about how the IP collection and processing happens, before we evaluate anything else. Nobody has, so far, answered. Kind regards
  8. Hello! You can use any server you like. Sharing CC licensed content is perfectly legal and no false positive or deranged persons madness can change that. Of course you will not be bothered in any case, regardless of the server you pick, this is a part of our job and you don't have to worry about anything. Kind regards
  9. Hello! It looks like Microsoft or the hardware vendor omitted to run by default some essential services, although we have reports that this is not the case in some Windows 8 versions. In this case, you might have a Windows 8 version which does not run (at the startup) the Netman service. Try to launch the service before launching the Air client or OpenVPN. Please see here: https://forums.openvpn.net/topic10013.html#p22546 Kind regards
  10. Hello! Please send us the client logs. Kind regards
  11. Hello! You need OpenVPN 2.3_rc1 and (optionally) the Air client for Windows 8: https://airvpn.org/index.php?option=com_kunena&func=view&catid=3&id=5827&Itemid=142#5834 We will soon publish the new package for Windows 8 in the Windows page, in the meantime please use the link above to download everything you need. Please note that you might like to uninstall OpenVPN 2.2.2 or older before installing 2.3_rc1. Kind regards
  12. Hello! dd-wrt.v24-18774_NEWD-2_K2.6_openvpn.bin is reported as working. Before re-flashing, please check your iptables rules (just in case...). You might also like to read this thread: https://airvpn.org/index.php?option=com_kunena&func=view&catid=3&id=3948&limit=6&limitstart=12&Itemid=142#4002 Kind regards
  13. Hello! From the logs, it appears that you have one of the bugged DD-WRT OpenVPN firmwares. A re-flash of a different firmware version should solve the problem, what is you router model? Kind regards
  14. Hello! Of course, please connect with account "Wamir". Kind regards
  15. Hello! OpenVPN can't find the files: ca.crt user.crt user.key Please make sure you have pasted them all in the Tunnelblick configuration directory. Kind regards
  16. Hello! Is the above the complete logs output by Tunnelblick...? Nothing else? Kind regards
  17. Hello! Tunnelblick 3.2.8 is not compatible with Mac OS X 10.8.x. Please upgrade to an appropriate version: http://code.google.com/p/tunnelblick/wiki/DownloadsEntry?tm=2 Kind regards
  18. Hello! Please send us the complete Tunnelblick logs at your convenience. Kind regards
  19. Hello! Actually your account IS connected to some server since some hours ago and it is exchanging successfully data. Kind regards
  20. Hello! As you may have seen from the linked instructions, Comodo says "MAC Any" when you select "Any IP Address". Yes, that's the way to tell Comodo to generate logs for a rule when that rule is fired. Yes, DNS leaks are a typical Windows problem, because Windows lacks the concept of global DNS. Maybe you need to re-read the global rules tutorial and guide? Also, please send us the screenshots of your Comodo global rules and network zones. Kind regards
  21. Hello! In order to change DNS on Windows 7 please see here: http://www.sevenforums.com/tutorials/15037-dns-addressing-how-change-windows-7-a.html The DNS IP addresses you need to set on your physical interface after the connection to the VPN are: 10.4.0.1 10.5.0.1 About ESET, if you just wish to block ONLY your torrent client, maybe you can replicate a block rule for your p2p client, blocking for it any connection NOT coming from the IP range 10.4.0.0-->10.9.255.255. Kind regards
  22. Hello! Yes, it's in the XML configuration file (you can see its name and path through the logs). The displayed order is fixed by the server. The next release of the client will address this and also several little issues. Kind regards
  23. Hello! The problem has been addressed. Normal connectivity should be totally restored. Please do not hesitate to write here or contact us if you still experience issues. Kind regards
  24. We are experiencing an issue with the backend servers and we are working to solve it. Kind regards
  25. Hello! Apparently Tunnelblick/OpenVPN receives the OpenVPN server push but does not execute the route commands. Please see here for some considerations: http://code.google.com/p/tunnelblick/wiki/cConnectedBut If everything else fails, please try to uninstall Tunnelblick and upgrade to Tunnelblick 3.3beta21: http://code.google.com/p/tunnelblick/wiki/DownloadsEntry?tm=2 Kind regards
×
×
  • Create New...