Jump to content
Not connected, Your IP:


  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by go558a83nk



    Maybe it is some problem in 2.8RC1.


    I am using 2.9.2 experimental


    >>Network Lock (even if IPv6 remains enabled) should prevent that, can you confirm?


    No. I am always using NL and it is leaking as well.




    Can you please confirm that:


    - "Force DNS" is ticked

    - "Network Lock" is active

    - IPv6 is enabled

    - no firewall other than Windows Firewall is running

    and under these conditions you have DNS leaks in your Windows system with Eddie 2.9.2 Experimental?


    Can you send us the output of the command "ipconfig /all" (issued from a command prompt) while the system is connected to the VPN with the aforementioned settings?


    Kind regards



    IPv6 should be *disabled*, no?


    Staff, I don't usually disagree with you but what about the point of the fast speeds to another VPN provider?




    how can you know whether the other provider provides connections to the same ports with the same ciphers and same protocol tried on our servers by ddrnewb or not? And even if it did, you can't assume that ddrnewb tested exactly under the same conditions both services. Actually ddrnewb did not specify anything about that, so it's not correct to make such an assumption. And as you can see from the results he/she posted, we were right, either his/her ISP is performing traffic shaping or it's his/her system to do that.


    Kind regards


    I didn't assume as much as you think.


    1) the OP says he doesn't like TCP, so I deduced that he would NOT have used TCP for the other VPN provider.

    2) from what I can see IPvanish employs no special obfuscation techniques.

    3) I think it's a big assumption to say that the speed difference shown is due to protocol.  it could just be because of the different time of day and all the many other things that determine internet quality.  I believe that point is made in the third speed test posted, where the speed is back down to being similar to the first even though it was an SSL tunnel test.

  3. If what Staff says is true regarding your OS and use of tunnelblick, that it ignores the DNS push from AirVPN (no reason to doubt it), then it means that if you set nicproject DNS manually in your OS you'll still be using nicproject DNS even when connected to VPN.  this isn't a bad thing.  All DNS requests will go through the tunnel, but will go to nicproject servers, not Air DNS.

  4. Air will assign you a random port that will be forwarded to you: client area > forwarded ports > click the add button.


    Insert that port into your P2P client in the listening port area.


    And go.  Simple as that.  Of course, you must be connected to an Air server and you must be running the P2P client for the port check to say the port is open.


    Turn UPnP and NAT-PMP and randomize port off.  You can turn UPnP off on your router too unless you need it for something else.


    Does it mean that for example I use port 16621 for my torrent client, tixati. So I should disable port forwarding for port 16621 in my router ? 


    Yes or use, for your torrent client, any other port like 16622 that is closed in your router but you had set it to forward in AirVPN config. You don't have to open any port in your router for  p2p when you are connected to the VPN, just set it on port forwarding


    to be clear, if you are using an openvpn client, such as AirVPN's eddie, on your computer, then it's bad to open ports on you router.


    but, if you run VPN from your router, then you do need to forward ports in the router.

  • Create New...