7 replies to this topic

[asperatus]

Hi
Some time ago I found out about software like wtfast and pingzapper. I was sceptic, but in my case they reduce ping tremedeusly
So I thought that maybe I can improve things without relying on 3rd party software like this. I did 2 trace routes: one with pingzapper on, and one off, simply launching ragnarok.

This is route when I launch ragnarok through pingzapper vpns

Spoiler

  1     9 ms     9 ms    12 ms  10.216.0.1
  2     9 ms    11 ms     7 ms  192.168.216.1
  3    13 ms    14 ms    13 ms  host-217-172-225-117.gdynia.mm.pl [217.172.225.117]
  4    17 ms    15 ms    14 ms  89.228.6.37
  5    18 ms    14 ms     *     89.228.6.38
  6    16 ms    16 ms    32 ms  war-b1-link.telia.net [213.248.66.205]
  7    45 ms    87 ms    37 ms  ffm-bb1-link.telia.net [62.115.135.192]
  8    40 ms    46 ms    37 ms  ffm-b10-link.telia.net [62.115.137.221]
  9    40 ms    38 ms    37 ms  twitter-ic-308239-ffm-b10.c.telia.net [62.115.49.94]
 10    40 ms    38 ms    39 ms  192.133.76.28
 11   122 ms   125 ms   121 ms  xe-3-0-1.iad1-cr1.twttr.com [199.16.159.127]
 12   129 ms   121 ms   122 ms  xe-0-1-1.iad1-cr2.twttr.com [199.16.159.57]
 13   388 ms   142 ms   158 ms  ae53.atl1-er1.net.twttr.net [199.16.159.75]
 14   138 ms   139 ms   136 ms  199.16.156.120

And this is how it looks like when I have pingzapper turned off

Spoiler

1    10 ms     8 ms     9 ms  10.216.0.1
  2    11 ms    14 ms    10 ms  192.168.216.1
  3    15 ms    14 ms    68 ms  host-217-172-225-117.gdynia.mm.pl [217.172.225.117]
  4    17 ms    14 ms    14 ms  89.228.6.32
  5    16 ms    37 ms    32 ms  xe-5-0-0.waw11.ip4.gtt.net [141.136.100.45]
  6    33 ms    33 ms    31 ms  xe-0-1-1.fra61.ip4.gtt.net [89.149.186.85]
  7    34 ms    32 ms    32 ms  as2914.fra61.ip4.gtt.net [77.67.82.10]
  8    34 ms    30 ms    32 ms  ae-3.r20.frnkge04.de.bb.gin.ntt.net [129.250.3.93]
  9     *        *        *     Upłynął limit czasu żądania.
 10     *        *        *     Upłynął limit czasu żądania.
 11   198 ms   194 ms   208 ms  ae-2.r05.lsanca03.us.bb.gin.ntt.net [129.250.5.86]
 12     *      195 ms   203 ms  xe-0-0-0-15.r05.lsanca03.us.ce.gin.ntt.net [198.172.90.170]
 13   194 ms   196 ms   203 ms  ragnarok.demarcation.gravityus.com [128.241.92.6]
 14   203 ms   196 ms   203 ms  valkyrie-z13.1.online.ragnarok.warpportal.net [128.241.92.112]

Difference of 70ms is no laughing matter. Any suggestions on what to do?
 

Edited by asperatus, 08 April 2015 - 02:38 AM.

[renouille]

11   122 ms   125 ms   121 ms  xe-3-0-1.iad1-cr1.twttr.com [199.16.159.127]
 12   129 ms   121 ms   122 ms  xe-0-1-1.iad1-cr2.twttr.com [199.16.159.57]
 13   388 ms   142 ms   158 ms  ae53.atl1-er1.net.twttr.net [199.16.159.75]
 14   138 ms   139 ms   136 ms  199.16.156.120

First traceroute isn't RO.

[asperatus]

First traceroute isn't RO.

 

After launching pingzapper and using netstat command RO leads to IP of 127.0.0.1
I thought I'll use tracert command using pingzapper IP instead
If i picked wrong IP, then I'm out of ideas. I have literally only those 2 applications listed after using netstat command

[Killcycler]

Im going to refer to Pingzapper as a VPN just by the description of the service.

 

Ive never actually seen a VPN and wouldn't expect it to EVER reduce latency, but i wouldn't be shocked if maybe you were being tricked as in what you're looking at in your first trace route is only the connection from your comptuter to your vpn host. All traffic beyond the host is often done on their level and not seen by your traceroute hence why it seem likes it would be faster.

 

Basically without that your connection looks like this:

home--8 hops-->RO

with it:

home--8 hops-->VPN>--8 additional hops-->RO

                                         (invisible to you)

 

Your VPN is giving you the address 127.0.0.1 which is localhost (LOCAL!!!!) and your end is being fooled into thinking this is RO when it isn't and not only that the "Reduced latency" your seeing is merely the connection to the VPN which....yes, would most likely be faster, but the 8 other hops you're not seeing result in almost twice the latency then just connecting directly.

 

The only time a service like this will benefit you is if you're trying to trick a server into thinking you have typical HSI pings (30ms) when you actually have dial-up/satellite (200ms+) so that you can play the game when they have a latency cap. Though you'll still die in say battlefield for example because your reaction isn't going to be as fast as the server thinks you can react.

 

EDIT: i forgot to mention i traced the above xe-3-0-1.iad1-cr1.twttr.com [199.16.159.127] to Dyn.com which has the alias dinect.net....This is definatley a part of your pingzapper VPN

Edited by Killcycler, 08 April 2015 - 11:07 AM.

[asperatus]

Well, it has some effect. Big enough to be noticeable, mostly in character movement(character is not stuttering like usual) and during fights(game doesnt "cough" damage numbers in chunks, faster updates on character position after being hit by monster during movement)

Is it caused by pingzapper? No idea. There is no difference in , for example, path of exile when I switch it on/off and check latencu with in-game tools. So it may be placebo effect

[Killcycler]

Im guessing that would be because the connection to the VPN from RO is a relatively short distance/fast and the VPN relays this to you in a decent fashion so your client doesn't hiccup quite like your used to.

 

It also looks like it might be going around a small degree of packet loss at the end of the link:

 

  9     *        *        *     Upłynął limit czasu żądania.

 10     *        *        *     Upłynął limit czasu żądania.

 

...​You're in poland?

[asperatus]

 

You're in poland?

Yup

Tried to launch game with different VPNs but unfortunately, RO doesn't let me(play button doesnt appear, I get "failed to connect to server" or "disconnected from server" messages)

[Tribe]

Any suggestions on what to do?

 

Keep using Pingzapper! Also get some friends to use it and abuse the refer a friend system.