Jump to content
Not connected, Your IP: 34.201.11.222

Staff

Staff
  • Content Count

    8836
  • Joined

    ...
  • Last visited

    ...
  • Days Won

    1275

Everything posted by Staff

  1. 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
  2. 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
  3. Hello! Can you please send us the connection logs? Kind regards
  4. Hello! The private IP address assigned to the client is related to the connection port. For example, clients connecting to port 443 UDP obtain an IP address in the range 10.4.0.0 - 10.4.255.255 (Net: 10.4.0.0/16, in CIDR notation). This means that there are (2^16-2)=65534 IP addresses per port per server available to the clients. This limit is clearly more than enough, since a server capacity is exhausted much, much before. Anyway, we would love to face the problem to accommodate more than 65534 clients per port. Please do not hesitate to contact us for any further information. Kind regards
  5. Hello! Connections over http or over SOCKS proxy are a smart feature of OpenVPN. http://openvpn.net/index.php/open-source/documentation/howto.html#http The method we suggest in our example can be used successfully in Linux Liberte as well. https://airvpn.org/tor Please do not hesitate to contact us for any further information. Kind regards
  6. Hello! You will receive soon the answer in italian in private, since this is an english only forum. Kind regards
  7. Hello! The problem is only with Google which considers Vega's exit IP in China and redirects you to their .hk pages. USA geo-discriminatory services anyway recognize Vega IP as an USA IP address, granting therefore access. There's nothing we can do, it's just a Google mistake (Vega is in Oregon). You could use the server Sirius, in the USA, to solve the problem. Please do not hesitate to contact us for any further information. Kind regards
  8. Hello! Check your inbox for our support in reply to your previous e-mail. Kind regards
  9. Hello! We would need additional information to give you proper support. Can you please send us: - the connection log - the output of the command ifconfig -a when you're disconnected and when you're connected (in private, if it may compromise your privacy). We're looking forward to hearing from you. Kind regards
  10. Hello and thank you for your choice! A TCP port is mandatory to connect over TOR (or over any SOCKS and http proxy). Quickest solution: edit your air.ovpn configuration file and change the line proto udp to proto tcp. Also, make sure that the socks-proxy line is included with the proper settings. In case of doubt, re-generate your configuration with our configuration generator available here: https://airvpn.org/index.php?option=com_air&view=access&Itemid=100 and make sure to select the appropriate proxy type and its IP address and port number. For AirVPN over TOR connections detailed example, please see also https://airvpn.org/index.php?option=com_content&view=article&id=64&Itemid=122 Please do not hesitate to contact us for any further information. Kind regards
  11. Hello! Very well! Here the parameters for your Tomato: Interface Type: TUN Server Address: find it with our configuration generator, according to your preferences Server Port: 53 TCP or 53 UDP or 80 TCP or 80 UDP or 443 TCP or 443 UDP Authorization mode: TLS Extra HMAC authorization (tls-auth): yes Create NAT on tunnel: Unclear, try both options Accept DNS configuration: Strict Encryption cypher: AES-256-CBC Compression: LZO (pick adaptive) Certificate Authority: paste ca.crt content in it ((from -----BEGIN CERTIFICATE to END CERTIFICATE----- included)) Client Certificate: paste user.crt content in it (from -----BEGIN CERTIFICATE to END CERTIFICATE----- included) User key: paste user.key content in it You will find ca.crt, user.crt and user.key in the air.zip package generated by our configuration generator (you need to be a subscriber). Please do not hesitate to contact us for any further information. Kind regards
  12. Hello! No worries, you're welcome. Support has been moved to e-mail for faster feedbacks. Kind regards
  13. Hello! Support has already been given to you, but we received no feedback from our suggestions. Did you perform any of the steps we recommended? We kindly invite you to re-read the instructions on how to use the system, to send us the connection logs and follow the recommendations we gave you. We have very many happy Linux customers and we also use Linux to connect to our servers 24h/24. Everything works fine, so please don't stay with the assumption that it's a server side problem, consider the option that there might be some problem in your system. There are NO automated answers from our customer and support service. Since we strongly support freedom of expression against any censorship, we can only say that this is your right. Personal customer support has been given to you, as well as to any other customer and NON customer in need of support. About your refund request, you already sent it twice via the "Contact us" form, you already had the proper reply and the full refund will be delivered according to our Terms of Service that you accepted. Kind regards
  14. Hello! Could you please send us the connection logs? Have you tested different servers? You can obtain different performance on different servers for several reasons (see our FAQ). Also, try to switch port, just in case your ISP is capping bandwidth on the connection port you're currently using. Try 80 TCP, 53 UDP and 53 TCP. We're looking forward to hearing from you. Kind regards
  15. Hello! We don' support IPv6 at the moment. For additional security, how to disable IPv6 in Windows 7: [EDIT: link removed - see next message in this thread] How to disable IPv6 in Linux: https://wiki.archlinux.org/index.php/Disabling_IPv6 Please do not hesitate to contact us for any further information. Kind regards
  16. Hello! Thanks for the bug info, the Air client programmer will be informed. Can you please tell us which special characters created problems? Did you use Air v. 1.6? Kind regards
  17. Hello! Thank you for your subscription! We need some further information to support you properly. Can you please tell us your OS and if you use the AirVPN client or OpenVPN client? Also, could you please send us the logs of a failed connection? If you use OpenVPN, you will find the logs on the "log" directory where OpenVPN is installed. If you use the AirVPN client, after a failed connection attempt, please right-click on the dock icon and select "Logs". A window will open up. Select "Copy to clipboard", then paste in the message. Kind regards
  18. Hello! You need a router which supports the OpenVPN client. Most routers where you can install DD-WRT firmware support OpenVPN. If you don't have a compatible router, don't worry, you can as usual connect with any computer or device which runs Linux, Windows, Android or MacOSX. To see a list of compatible DD-WRT router: http://www.dd-wrt.com/wiki/index.php/Supported_Devices Please do not hesitate to contact us for any further information. Kind regards
  19. Hello! They will not interfere with the anonymity layer of your computer. AirVPN will protect only your computer. However, if the router is connected to an ISP, and the subscription to this ISP is yours, liability for anything done online by the other users may be charged to you. You should check the laws in your country. Please do not hesitate to contact us for any further information. Kind regards
  20. Staff

    DNSCrypt

    Hello! When you're connected to our VPN server, your DNS requests are already encrypted, and a DNS server IP address is pushed (see also https://airvpn.org/index.php?option=com_content&view=article&id=74&Itemid=141). If you need to use DNSCrypt in conjunction with OpenVPN, you may try to send the DNS queries outside the encrypted tunnel and check whether DNSCrypt disables itself or not. We recommend you to ask for support to OpenDNS too, since our setup is a typical hardened security OpenVPN setup. Please do not hesitate to contact us for any further information. Kind regards
  21. Hello! Wait, in the FAQ we wrote that your router must support OpenVPN. This is incompatible with PPTP. We don't support PPTP for security reasons (see http://en.wikipedia.org/wiki/Pptp#Security_of_the_PPTP_protocol). Does your router support OpenVPN? If not, you may have additional accounts for your different devices in order to connect to VPN servers simultaneously. No logs are kept in any VPN server. Also, no VPN server has any database account information. If you fear that USA servers may be wiretapped in real time without our knowledge you may use them over TOR. See https://airvpn.org/index.php?option=com_content&view=article&id=64&Itemid=122 USA servers are anyway helpful to keep our project sustainable, because we have several requests to access geo-discriminatory (legal) USA services like Hulu, Pandora and Netflix. We're looking forward to hearing from you. Kind regards
  22. Thanks! So it is probable that deadfix blacklisted Omicron exit-IP address. Please use our Netherlands servers (Lyra and Leonis) or USA servers (Sirius and Vega) to access it while we look into the issue. Kind regards
  23. Hello! Grooveshark should block ALL German IP addresses, there is an official statement. Can you please check at your convenience? Kind regards
  24. Hello! It's the other way round: it's those sites which block German IP addresses. We don't block ANY website. Please try our Netherlands servers. Kind regards
  25. Hello! Ok. No, the configurations are identical on all servers. The times are high but normal for a WiMax ISP. Yes, Vega is really in the USA (in Oregon). It has IP addresses belonging to a block which has been spread throughout different countries, probably this is the cause for Google mistake. Anyway, US geodiscriminatory services correctly detect Vega IP as an american IP address (therefore Hulu, Pandora etc. work just fine). Also, please use Sirius if you want Google to detect you come from the USA. This does not cause problems. At worst, it might only introduce slightly higher latency. The real problem is WiMax. We have noticed that several WiMax providers cap bandwidth on anything except http connections when they detect volumes of traffic on certain ports. This would explain why at the beginning (trial period) your connection was fast, and now it is not. So, if it's your case (if you wish, can you tell us, in private of course, the name of your ISP?) when you connect with OpenVPN, your bandwidth is capped by your ISP. Please connect to port 80 TCP to try to circumvent the cap. We are also preparing a technical solution that will help to circumvent such caps. As soon as it is ready, we'll provide all the information in the forum. It should be a matter of days. In the meantime, we are very much looking forward to hearing from you whether connections on port 80 TCP (also try port 53 UDP and 53 TCP) mitigate the problem. Kind regards
×
×
  • Create New...