Jump to content
Not connected, Your IP: 18.226.166.121

Staff

Staff
  • Content Count

    11321
  • Joined

    ...
  • Last visited

    ...
  • Days Won

    1945

Everything posted by Staff

  1. Hello! Instructions are given in the second message of the valid link we gave you. The invalid link you cite is reported in the third message and you can safely ignore it. Re-installing Tunnelblick can not solve your problem, because with uninstallation you don't delete the old confiiguration directory, so Tunneblick will continue to see old configuration and certificates. If you need further details: http://code.google.com/p/tunnelblick/wiki/cConfigT#Modifying_a_Tunnelblick_VPN_Configuration For your comfort we copy & paste the relevant content which can solve your problem in a matter of seconds: If you follow step 1 ("edit your OpenVPN configuration file"), you just need to modify the IP address reported in line: remote 174.140.166.91 <port> with (in this example we assume you will connect to Sirius, an american server, on port 443): remote 108.59.8.147 443 Of course you can insert any server IP address you like (see their entry-IP with our configuration generator). Valid ports are 53, 80 and 443. To switch between UDP and TCP (see the FAQs about their differences), locate the line proto <protocol> and set it to proto udp if you wish UDP, or proto tcp if you wish TCP. Please do not hesitate to contact us for any further information. Kind regards
  2. Hello! Probably your problem can be solved with removal of old configuration. Please see here for all the details: http://groups.google.com/group/tunnelblick-discuss/browse_thread/thread/3ebde520b606dfd4 Let us know if this fixes the problem. Kind regards
  3. Hello! The problem seems to lie here: Can you please make sure that Tunnelblick can access the certificate files (user.crt and ca.crt) and the key (user.key)? Also, please to connect to another port (for example 80 TCP). We're looking forward to hearing from you. Kind regards
  4. Hello and welcome back! You need to re-generate your files (menu "Member"->"Access without our client"). You probably have an old certificate which is no more valid, but above all you are trying to connect to a server which is not in our infrastructure anymore (it has been replaced by two 1 Gbit/s servers, dedicated line/port). As you will see from the configurator, there are now 3 servers in Holland (100 Mbit/s each, dedicated), 1 in Sweden (1 Gbit/s, dedicated), 1 in Germany (100 Mbit/s dedicated) and 2 in the USA (1 Gbit/s each, dedicated). The server you try to connect too is Sigma, which could no more sustain the load and has been dismissed. Please do not hesitate to contact us for any further information. Kind regards
  5. Hello! Very well. Thank you for your time! Kind regards
  6. I have a tunnel terminated at my router so that my OS (WinXP) thinks I have a native IPv6 connection and gives me a public IP address through stateless autoconfig. That public IP was visible at whatismyipv6.com when the VPN was active. I'd say the risk is far more than non-zero. Hello! It seems just fine. It's PPTP that tunnels your real IPv4 address in the IPv6, not OpenVPN. Please confirm that when you say "public IP was visible at whatismyipv6" you refer to the generated IPv6 address, not to your real IPv4 address. If whatismyipv6.com could see your real IPv4 public address (instead of the IPv4 address of the VPN server), please warn us as soon as possible. Kind regards
  7. Hello! You're right, OpenVPN is not affected by the vulnerability discovered on PPTP. The IPv6 contains either your true IPv4 or your MAC address. If you point for example to a web site using an IPv6 address, with PPTP your REAL IPv4 address will be tunneled over PPTP, disclosing it to a malicious entity. OpenVPN does not have this vulnerability. Also, your IPv6 address is generated by the IPv4 address assigned to you. The IPv6 loopback interface never get out of your network card (think of it as the equivalent of 127.0.0.1 IPv4), it can only communicate on the local machine. Currently we don't support IPv6 at all. When the time will come, support to IPv6 will be added with the usual security standards. To answer to your question, the probability is therefore near-zero ("near" because in the security field it is theoretically impossible to state a 100% security under most circumstances). Please do check here while connected to an Air server: http://whatismyv6.com/ You should be able to see ONLY the IPv4 exit-IP of the VPN server you're connected to. Connection to their IPv6 web site should fail. Kind regards
  8. Hello! We're going to add it in the FAQ too. Kind regards
  9. Hello! The exit-IP addresses are static and shared. There is 1 exit-IP address per server. Additional exit-IP addresses may be used but only when strictly necessary. Please do not hesitate to contact us for any further information. Kind regards
  10. Hello! If you have asked for a trial, you should have received a code and the instructions on how to use it in order to activate your account to premium status. Your account is currently and correctly on "Free member" since you did not follow the procedure. If you have not received the instructions, please do not hesitate to contact us (menu "Support"->"Contact us"). You need a valid e-mail address to receive code and instructions. Kind regards
  11. Hello! Of course they can. A "trial account" is just a label, "trial accounts" are full premium accounts for 4 days, there's absolutely no difference. Linux users can use OpenVPN directly or any OpenVPN GUI they like. Please do not hesitate to contact us for any further information. Kind regards
  12. Hello! VPNetMon works with OpenVPN, and on a Win7 system has been successfully tested with AirVPN. That said, this solution is not optimal, furthermore proprietary solutions that interferes with the OS should be carefully peer-reviewed. At the moment we don't recommend a solution based on forced shutdown of programs. One of the problems is in the forced shutdown time of the applications, which may allow some packets to get out of the tunnel anyway. Another potential problem is the risk of data loss which may happen with a forced shutdown (for example, if you're compiling a form with a browser, or executing a script). We recommend a much cleaner and safer solution, that is properly set firewall rules. According to your firewall and OS, we may help you to set the rules to prevent "data leakage" in case VPN connection drops. You can already find various instructions on the forum. Kind regards
  13. Hello! We're very glad to inform you that a new 1 Gbit/s server located in Sweden is available: Draconis. 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/certificate/key generator (menu "Member"->"Access without our client"). The server accepts connections on port 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
  14. Hello! Our configuration/certificates generator works only for premium members. You need to subscribe to access the VPN servers. Please do not hesitate to contact us for any further information. Kind regards
  15. Hello! Very well! Probably you will be able to establish successfully a connection on any server just using port 80 TCP. Kind regards
  16. Hello! This is because outgoing port 25 is blocked. Please switch to SSL/TLS SMTP on port 465 or 587 (or any other port supported by your smtp server). In general, it is a very bad idea, under a security point of view, sending e-mails through smtp on port 25 without any encryption on negotiation and sending. Please do not hesitate to contact us for any further information. Kind regards
  17. What do you mean by "traffic"? Do you mean the contents of the message? Tor both encrypts and decrypts "traffic" sent through its servers/nodes. This information is obtained from Tor's official website. Hello! "Traffic" is meant as the total amount of packets, including contents of messages. In the case of TOR over AirVPN, a malicious TOR node can see your traffic (unless you further encrypt it) because when the packets get out of our servers they are no more encrypted by OpenVPN, obviously. Anyway any TOR node will not be able to see your real IP (in the worst case, it will see the exit-IP of the Air server you're connected to). TOR over Air and Air over TOR therefore provide very different scenarios. Pick the one that is most suitable for your security needs. Please do not hesitate to contact us for any further information. Kind regards
  18. Hello! We're very glad to inform you that a new 100 Mbit/s server located in the Netherlands is available: Orionis. The AirVPN client will show automatically this new server, while if you use the OpenVPN client you can generate all the files to access it through our configuration/certificate/key generator (menu "Member"->"Access without our client"). The server accepts connections on port 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
  19. Hello! Your logs look ok. Since everywhere else the connection is fine, it is possible that there's something in your home line which is the issue. First of all, try to connect to a different server and to a TCP port (for example 80 TCP) in order to ascertain whether it's a line (quality, latency...) issue with Vega. Also, check your browser settings. Test also some other protocol (for example FTP, bittorrent) to determine if the issue lies in the browser. We're looking forward to hearing from you. Kind regards
  20. Hello! If you do so, you will have TOR over AirVPN. You will be visible on the Internet with the final TOR exit-node IP address when you use a browser proxied to TOR. Air server will be able to see your real IP and TOR nodes will see the Air server exit-IP address. Traffic through TOR nodes will be already decrypted by our servers. For a different setup, consider AirVPN over TOR: https://airvpn.org/index.php?option=com_content&view=article&id=64&Itemid=122 In this case, Air server will not be able to see your real IP address, but will see the IP address of the TOR relay. TOR node you connect to (OpenVPN over SOCKS or over http proxy) will see your real IP address but all TOR nodes will see packets encrypted by OpenVPN. You will be visible on the Internet with the Air server exit-IP address. Please do not hesitate to contact us for any further information. Kind regards
  21. Hello! MacOSX does not have, by default, OpenVPN functionalities. Tunnelblick is an open source GUI for OpenVPN which is provided pre-packaged with OpenVPN itself. Another GUI for MacOSX is Viscosity. It's not open source, though. Please do not hesitate to contact us for any further information. Kind regards
  22. @climbxz Hello! From the logs it appears that the problem is on your local proxy 127.0.0.1:8080 which refuses connections. What proxy is it? Can you please check that it is running and accepting connections? Did you configure properly OpenVPN to connect over a proxy? Also, you might test a direct connection to our VPN servers without a proxy. Feel free to send us your air.ovpn configuration file. We're looking forward to hearing from you. Kind regards
  23. Hello! Glad to know the issue is fixed. For a while, check whether you're really connected for additional security, and feel free to send us the connection logs. Kind regards
  24. Hello! We allow connections on port 53 UDP on every server. Please ask your public WiFi provider about the issue. Maybe they disrupt OpenVPN connections. Kind regards
  25. Hello! Can you please send us the connection logs? Kind regards
×
×
  • Create New...