Jump to content
Not connected, Your IP: 3.235.236.13

go558a83nk

Members2
  • Content Count

    1904
  • Joined

    ...
  • Last visited

    ...
  • Days Won

    26

Posts posted by go558a83nk


  1. This server has the third worst latency for the Asian region.

     

    When are you going to add more asian servers for the Asian region ?

     

    I'm sure there are customers in this region frustrated like me.

     

    latency is a description of the path to the server, not an indicator of the health of the server itself.  please keep in mind that AirVPN and the datacenters they use can NOT affect internet peerage, IP transit agreements and overall routing though I'm sure they wish they could so that all customers were happy.


  2.  

    If I recall correctly the 4 servers were 100 mbit/s each.  The 1 now is 1gbit/s. 

     

    Latency is a descriptor of the path to the server, not of the server itself.  In other words, if you are seeing latency problems, blame your ISP peerage/routing/IPtransit agreements or perhaps a fault in a line somewhere. 

     

    I use 4 different 4G LTE and a number of ADSL and fibre connections. They all have problems with the SG server. I conclude the server has poor routing for the Asian region. In fact the usa servers have better latency.

     

    Ever heard of load balancing ?

     

    The previous 100 mbits servers were much better and were balanced across 4 servers.

     

    1 gbits server isn't as good as the previous 4.

     

    I agree - routing to Leaseweb Singapore seems to be lacking.


  3.  

    if you are seeing latency problems, blame your ISP peerage/routing/IPtransit agreements or perhaps a fault in a line somewhere.

     

    I think there were five. They also had a quite bad reputation, mostly because of their latency. I think it's Singapore's lines' fault.

     

    4 or 5, 100mbit/s.  they actually worked quite well for me.  my ISP routing to that datacenter was nice.  most of the time routing to Leaseweb Singapore takes me to USA first, then back to Singapore. LOL


  4. If I recall correctly the 4 servers were 100 mbit/s each.  The 1 now is 1gbit/s. 

     

    Latency is a descriptor of the path to the server, not of the server itself.  In other words, if you are seeing latency problems, blame your ISP peerage/routing/IPtransit agreements or perhaps a fault in a line somewhere. 


  5. when running VPN on the router you do NOT use the port forwarding built into router firmware GUI.

     

    you must do a DNAT as the IP tables linked to by Staff do.

     

    SSH into the router and paste those lines into the command line, editing them to suit your setup.

     

    to get a forwarded port, just go into your client area of this web page, forwarded ports section, and click the add button.  You will be assigned a port.  That port is what goes into the IP tables.


  6.  

     

    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.

     

    Hello!

     

    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?


  7.  

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

     

    Hello,

     

    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.


  8. 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.


  9. 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.

×
×
  • Create New...