Jump to content
Not connected, Your IP: 18.225.72.161

Staff

Staff
  • Content Count

    11046
  • Joined

    ...
  • Last visited

    ...
  • Days Won

    1867

Everything posted by Staff

  1. @ruffnekk Please try what suggested in the previous message. Testing the server#1 in the top 10 speeds could make no sense. Also perform more reliable speed tests with normal usage, few-seconds tests when available bandwidth is high and with the bias of a 3-rd party server, like in your case, can easily be misleading. Kind regards
  2. Hello! Sure it is (look at the top 10 users speed table). We take care to run servers only in datacenters with excellent connectivity (PoP to tier1 providers, redundant uplink ports). Try to change servers connection ports: if you record 16 Mbit/s with every and each server in different datacenters, it looks like a precise bandwidth cap, because the likelihood to get the same performance from several, different servers in different datacenters with different providers is remarkably low. Please test all connection ports to make a comparison. Kind regards
  3. Hello! It can't be ruled out. Anyway we have seen this very same behavior on Windows systems running Kaspersky, ZoneAlarm... can you please try to disable any packet filtering tool and check whether the problem remains or not (over UDP), if you run Windows? Also, it's worth to check for (and disable for testing purposes) firewall/packet filtering-inspection tools on the router as well. Kind regards
  4. Hello! Please try to re-generate the configuration in the following way, just in case it's a name resolution problem. Enter the Configuration Generator and: - tick "Advanced Mode" - tick "Resolved hosts in .ovpn file" - tick "All servers for area or region" We're looking forward to hearing from you. Kind regards
  5. Hello, yes, you should be able to see that. If you can't, please feel free to re-submit your trial request at your convenience. Answers to customers support tickets vary from a few minutes to some hours, according to the complexity of the request and the procedures required to verify and reproduce the problem (anyway the customer is kept informed about them). Tickets opened by non-customers with question or questions already in the FAQ have lowest priority and anyway are not processed until all the tickets from customers have been properly addressed. Trial requests have no definite answer time and we reserve the right not to deliver trial coupons under some circumstances: multiple requests, scam attempts etc. In case you are in a hurry we have a 1 EUR plan for 3 days which can be, as usual, fully refunded. Kind regards
  6. Hello! Thanks for the information about your DNS. In China, OpenVPN connections are disrupted through OpenVPN fingerprint identification, therefore OpenVPN over SSH/SSL is mandatory. In your case, it was a completely different problem: your DNS does not resolve *.airdns.org names. You can connect directly with OpenVPN (you do not need OpenVPN over SSL). We thought it was a problem limited to OpenDNS but if you don't use OpenDNS then we were wrong. Kind regards
  7. Hello! A possible solution is allowing total access to inbound port 22, protocol TCP: iptables -A INPUT -p tcp --dport 22 -j ACCEPT In this case make sure to harden sshd security! Kind regards
  8. Hello! Both your landlord router and the Cisco VPN (if disabled!) will not interfere with remote port forwarding. Feel free to keep us informed. Kind regards
  9. @buga If you're running the Air client, please click on the "Modes" tab to select a TCP port, then click "Enter". For any other client, in the Configuration Generator, please tick "Advanced Mode" to display all the possible connection ports (including TCP ones). Since you see a huge performance difference between two computers on the same network, we suggest that you check on the "slow" computer for any packet filtering tool or security suite that might slow down an UDP flow. Kind regards
  10. EDIT: the DNS problem with OpenDNS and AT&T public DNS has been resolved. Hello! It seems that your system can't resolve europe.vpn.airdns.org. Just for our records, which DNS are you using (OpenDNS is known to break our *.airdns.org names). Also, if that's the only reported error, your installation of .ovpn files was just correct. In order to solve the issue, in the Configuration Generator please: - tick "Advanced Mode" - tick "Resolved hosts in .ovpn file" - tick "All servers for area or region" In this way the CG will generate files that contain only IP addresses, solving the problem at its roots. Kind regards
  11. Hello! The CF by default generates .ovpn configuration files that are embedded with key and certificates. If you wish separate files (but with Tunnelblick you don't need them), please tick "Advanced Options" then tick "Separate certs/keys from .ovpn files". Please see the Configuration Generator instructions (click on "More help") for all CF options and information. Once you have downloaded a configuration file please follow the instructions here: https://airvpn.org/macosx, i.e. create any folder on the Desktop, put the .ovpn file inside it, rename the folder with a ".tblk" extension. At this point the folder icon should change to a VPN Tunnelblick icon. Double-click on the folder icon to install the configuration contained inside the folder. Kind regards
  12. Hello! In this case, please uninstall OpenVPN and re-install it according to the indications in the following thread: https://airvpn.org/topic/9645-openvpn-tap-windows-81-adapter-problem Kind regards
  13. Hello! Please try to re-generate the configuration files in the following way: - tick "Advanced Mode" - tick "Resolved hosts in .ovpn files" - tick "All servers for area or region" If it's a DNS problem in *.vpn.airdns.org resolution, the above will fix it, because the Configuration Generator will generate files containing only IP addresses and not host names. Kind regards
  14. Hello! It might be a Windows 8 problem, which has been reported rarely (while it is reported frequently on Windows 8.1 Preview). Please see here, it could solve your issue: https://airvpn.org/topic/9645-openvpn-tap-windows-81-adapter-problem/ Kind regards
  15. Hello! The second link that is confusing you is from 2010 and therefore refers to very old Tunnelblick versions. Ignore 3 years old instructions threads, the updated instructions are always in the instructions pages. Please follow the updated instructions in the "Enter" page: https://airvpn.org/macosx Also, please publish your Tunnelblick logs: from your description it seems that you installed correctly the configurations but the problem looks different. Kind regards
  16. Hello! As you can see: it seems that it's your node to reject the packets that are correctly forwarded by our server, as we previously verified as well. Can you please check again any possible packet filtering tool in your system? Kind regards
  17. Hello! The problem is here: 8/25/2013 - 3:31 PM There are no TAP-Windows adapters on this system. You should be able to create a TAP-Windows adapter by going to Start -> All Programs -> OpenVPN -> Add a new TAP-Windows virtual ethernet adapter. Perhaps something went wrong during OpenVPN installation. Try to add the adapter (the virtual network interface used by OpenVPN) as specified in that log entry, making sure that you launch the script with administrator privileges (right-click and select "Run as administrato"). If the script fails and/or the error persists, please uninstall OpenVPN and re-install it, making sure to authorize the driver installation. Kind regards
  18. Hello! Please see here (assuming that you run the Windows firewall): https://airvpn.org/topic/9798-windows-7-8-windows-firewall-prevent-leaks-thanks-to-omniferum That will prevent any leak (i.e. not only DNS leaks) and Omniferum also provided a "quick switch". If you use the Comodo Firewall, please see here: https://airvpn.org/topic/3405-windows-comodo-prevent-leaks You can have "quick switches" with the Comodo firewall as well (just save different configurations, and switch to the one you wish). Kind regards
  19. @Royee Yes, actually they are planned in Eddie, the next client release for Windows, Linux+Mono and OS X. Traffic splitting is not planned though. At this point it's unclear whether you need leaks prevention or traffic splitting. The first will take just one minute configuration, the latter can be very simple or quite complex according to how you wish to split traffic (for example, the NaDre solution, which at the beginning seemed what you needed, will take just a couple of minutes - not considering basic network knowledge acquisition, that vary of course, but the guide is in itself a good lesson/course on the matter as well). Kind regards
  20. Hello, if you don't need to split traffic just start the p2p client after you have connected to a VPN server. @Royee That's trivial and requires one minute, but yuppicide seemed to ask a very different thing, that is splitting traffic on an application basis, which has nothing to do with the options you cite. Maybe yuppicide can clarify if that was (or not) the meaning of the question. Kind regards
  21. @13rice Getting advantage of the fact that you are now connected to some Air server, we have checked that packets are correctly forwarded to your VPN IP, to both ports you have currently forwarded remotely, can you confirm? Kind regards
  22. Hello, please run OpenVPN directly. If the problem persists, can you please post both stunnel and OpenVPN output? Kind regards
  23. Hello, can you please check your firewall and run the PortListener for a second test? https://airvpn.org/topic/9315-port-forwarding-tester While the PortListener is running and listening to one of your forwarded ports on IP 10.*.*.*, please start the check from your web panel and look whether incoming packets reach it or not. Kind regards
  24. Hello! Really? In this moment the top 10 clients speeds are: Not public. Aquilae 90.07 Mbit / sec 21h 10m 42s ago Not public. Lyncis 66.06 Mbit / sec 1h 3m 27s ago Not public. Corvi 63.22 Mbit / sec 1h 20m 17s ago Not public. Ophiuchi 44.19 Mbit / sec 6d 16h 47m ago Not public. Cygni 43.94 Mbit / sec 2d 5h 1m ago Not public. Corvi 39.5 Mbit / sec 42m 45s ago Not public. Cephei 34.25 Mbit / sec 1d 4h 24m ago Not public. Sirius 32.83 Mbit / sec 17h 59m 9s ago Not public. Columbae 32.13 Mbit / sec 1d 2h 5m ago Not public. Cygni 29.77 Mbit / sec 1d 12h 42m ago Of course the likelihood that you get higher speed from a server in a datacenter than from an ISP residential line is much higher. This is due to the fact that several western countries ISPs are applying such wild and extensive overselling on residential lines that their declared "peak" bandwidth to your node can be achieved only in very particular conditions (only in short bursts, only with some allowed protocols). Kind regards
  25. Hello! That's correct, because 10.*.0.1 are VPN IP addresses: they can be accessed only from within the private network, they are not public. You need a public DNS to resolve domain names while your system is disconnected from the VPN (except OpenDNS which is currently breaking *.vpn.airdns.org resolutions for unknown reasons). Alternatively: - select "Advanced Options" in the Configuration Generator - tick both "Resolved hosts in .ovpn file" and "All servers for area or region" In this way the CG will generate files which contain only IP addresses, solving the problem at its roots. Kind regards
×
×
  • Create New...