View All Products
Compute
Storage
Databases
Networking
Developer Tools
Delivery
Security
Services
Industries
Pricing
Community
Engage With Us
Community ▶ Questions ▶ VPN Routing and Gaming Issues
Log in to Ask a Question

VPN Routing and Gaming Issues

general

I have some issues with routing my vpn services to linode Atlanta Hub I am using Ubuntu 16.04 LTS and I followed these directions ~~[https://www.digitalocean.com/community/tutorials/how-to-set-up-an-openvpn-server-on-ubuntu-16-04 " target="_blank">](https://www.digitalocean.com/community/ … ntu-16-04 ">https://www.digitalocean.com/community/tutorials/how-to-set-up-an-openvpn-server-on-ubuntu-16-04]( at the moment i have things working but question if I can play around with the MTU settings and what exactly should i set it too?

Here is currently what i see from my home to the Linode server

[LOREN.DESKTOP-L5MI72F] ➤ tracert 0.0.0.155

Tracing route to unknown.members.linode.com [0.0.0.155]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.9.1
  2     *        *        *     Request timed out.
  3    10 ms     9 ms    11 ms  host-24-100-53-85.newwavecomm.net [24.100.53.85]
  4    22 ms    20 ms    21 ms  ipl-edge-03.inet.qwest.net [63.151.216.117]
  5    24 ms    25 ms    24 ms  chp-brdr-03.inet.qwest.net [67.14.8.194]
  6    28 ms    27 ms    27 ms  ae3.cr7-chi1.ip4.gtt.net [173.205.63.229]
  7    35 ms    35 ms    35 ms  xe-0-3-0.cr1-atl1.ip4.gtt.net [89.149.128.21]
  8    83 ms    36 ms    36 ms  ip4.gtt.net [173.205.39.138]
  9    34 ms    34 ms    37 ms  74.207.239.7
 10    34 ms    36 ms    50 ms  unknown.members.linode.com [0.0.0.155]

Trace complete.

Here is ping test from my home to linode..

[LOREN.DESKTOP-L5MI72F] ➤ ping -t 0.0.0.155

Pinging 0.0.0.155 with 32 bytes of data:
Reply from 0.0.0.155: bytes=32 time=41ms TTL=53
Reply from 0.0.0.155: bytes=32 time=40ms TTL=53
Reply from 0.0.0.155: bytes=32 time=47ms TTL=53
Reply from 0.0.0.155: bytes=32 time=35ms TTL=53
Reply from 0.0.0.155: bytes=32 time=34ms TTL=53
Reply from 0.0.0.155: bytes=32 time=34ms TTL=53
Reply from 0.0.0.155: bytes=32 time=34ms TTL=53
Reply from 0.0.0.155: bytes=32 time=34ms TTL=53
Reply from 0.0.0.155: bytes=32 time=33ms TTL=53
Reply from 0.0.0.155: bytes=32 time=37ms TTL=53
Reply from 0.0.0.155: bytes=32 time=34ms TTL=53
Reply from 0.0.0.155: bytes=32 time=35ms TTL=53
Reply from 0.0.0.155: bytes=32 time=35ms TTL=53
Reply from 0.0.0.155: bytes=32 time=39ms TTL=53
Reply from 0.0.0.155: bytes=32 time=34ms TTL=53
Reply from 0.0.0.155: bytes=32 time=35ms TTL=53
Reply from 0.0.0.155: bytes=32 time=33ms TTL=53

Here is from my home to 8.8.8.8

[LOREN.DESKTOP-L5MI72F] ➤ ping -t 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=20ms TTL=56
Reply from 8.8.8.8: bytes=32 time=19ms TTL=56
Reply from 8.8.8.8: bytes=32 time=20ms TTL=56
Reply from 8.8.8.8: bytes=32 time=19ms TTL=56
Reply from 8.8.8.8: bytes=32 time=18ms TTL=56
Reply from 8.8.8.8: bytes=32 time=19ms TTL=56
Reply from 8.8.8.8: bytes=32 time=32ms TTL=56
Reply from 8.8.8.8: bytes=32 time=18ms TTL=56
Reply from 8.8.8.8: bytes=32 time=30ms TTL=56

Now this is from Linode to 8.8.8.8 from vpn

[LOREN.DESKTOP-L5MI72F] ➤ tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

  1   154 ms    36 ms    34 ms  10.8.0.1
  2    34 ms    34 ms    35 ms  23.92.28.3
  3    34 ms    37 ms    35 ms  74.207.239.6
  4   106 ms    35 ms    38 ms  74.207.239.8
  5    36 ms    36 ms    99 ms  aix.pr1.atl.google.com [198.32.132.41]
  6     *        *        *     Request timed out.
  7    74 ms    87 ms    65 ms  216.239.63.133
  8    35 ms   110 ms    37 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.

Here is the ping to 8.8.8.8 under vpn

[LOREN.DESKTOP-L5MI72F] ➤ ping -t 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=37ms TTL=58
Reply from 8.8.8.8: bytes=32 time=38ms TTL=58
Reply from 8.8.8.8: bytes=32 time=37ms TTL=58
Reply from 8.8.8.8: bytes=32 time=35ms TTL=58
Reply from 8.8.8.8: bytes=32 time=35ms TTL=58
Reply from 8.8.8.8: bytes=32 time=35ms TTL=58
Reply from 8.8.8.8: bytes=32 time=93ms TTL=58
Reply from 8.8.8.8: bytes=32 time=40ms TTL=58
Reply from 8.8.8.8: bytes=32 time=35ms TTL=58
Reply from 8.8.8.8: bytes=32 time=93ms TTL=58
Reply from 8.8.8.8: bytes=32 time=41ms TTL=58
Reply from 8.8.8.8: bytes=32 time=36ms TTL=58
Reply from 8.8.8.8: bytes=32 time=46ms TTL=58
Reply from 8.8.8.8: bytes=32 time=74ms TTL=58
Reply from 8.8.8.8: bytes=32 time=73ms TTL=58
Reply from 8.8.8.8: bytes=32 time=74ms TTL=58
Reply from 8.8.8.8: bytes=32 time=72ms TTL=58
Reply from 8.8.8.8: bytes=32 time=77ms TTL=58
Reply from 8.8.8.8: bytes=32 time=94ms TTL=58
Reply from 8.8.8.8: bytes=32 time=103ms TTL=58
Reply from 8.8.8.8: bytes=32 time=130ms TTL=58

Here is from the linode box it self to google

root@localhost:~/client-configs# ping google.com
PING google.com (216.58.193.142) 56(84) bytes of data.
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=1 ttl=58 time=0.739 ms
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=2 ttl=58 time=0.869 ms
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=3 ttl=58 time=0.849 ms
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=4 ttl=58 time=0.865 ms
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=5 ttl=58 time=0.859 ms
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=6 ttl=58 time=0.860 ms
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=7 ttl=58 time=0.867 ms
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=8 ttl=58 time=1.24 ms

--- google.com ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7009ms
rtt min/avg/max/mdev = 0.739/0.893/1.242/0.142 ms
root@localhost:~/client-configs# ping google.com
PING google.com (216.58.193.142) 56(84) bytes of data.
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=1 ttl=58 time=1.04 ms
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=2 ttl=58 time=0.871 ms
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=3 ttl=58 time=0.875 ms
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=4 ttl=58 time=1.04 ms
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=5 ttl=58 time=0.889 ms
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=6 ttl=58 time=3.01 ms
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=7 ttl=58 time=0.852 ms
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=8 ttl=58 time=0.855 ms
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=9 ttl=58 time=0.838 ms
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=10 ttl=58 time=0.821 ms
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=11 ttl=58 time=0.892 ms
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=12 ttl=58 time=1.24 ms
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=13 ttl=58 time=0.839 ms
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=14 ttl=58 time=0.829 ms
64 bytes from atl14s08-in-f14.1e100.net (216.58.193.142): icmp_seq=15 ttl=58 time=0.927 ms

--- google.com ping statistics ---
15 packets transmitted, 15 received, 0% packet loss, time 14138ms
rtt min/avg/max/mdev = 0.821/1.055/3.016/0.536 ms

Here is a trace route from linode vps to 8.8.8.8

root@localhost:/etc/openvpn# traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  23.92.28.3 (23.92.28.3)  0.851 ms  0.813 ms  0.858 ms
 2  74.207.239.6 (74.207.239.6)  0.617 ms 74.207.239.2 (74.207.239.2)  0.729 ms  0.726 ms
 3  aix.pr1.atl.google.com (198.32.132.41)  0.692 ms 74.207.239.8 (74.207.239.8)  0.701 ms aix.pr1.atl.google.com (198.32.132.41)  0.656 ms
 4  aix.pr1.atl.google.com (198.32.132.41)  0.635 ms  0.621 ms 108.170.249.65 (108.170.249.65)  0.583 ms
 5  216.239.63.167 (216.239.63.167)  0.957 ms * *
 6  209.85.254.185 (209.85.254.185)  0.590 ms 216.239.56.91 (216.239.56.91)  0.687 ms 216.239.63.157 (216.239.63.157)  0.882 ms
 7  google-public-dns-a.google.com (8.8.8.8)  0.509 ms  0.485 ms  0.482 ms
root@localhost:/etc/openvpn#

So why is it i have so much latency while connected up to the vpn?? Is this an MTU issue? The only thing this server is doing is providing me with a vpn as a test I already rent a server from So You Start and it does the exact same thing.. I am using 443 for the vpn and tcp instead of udp.

Is it possible that maybe Linode is routing vpn traffic differently?

4 Replies

I figured some one might have an opinion on this by now..

You're expecting an answer within 24 hours of your post on Christmas Day? You might need to wait a bit longer - this is a community forum.

First off, trying to play games over a VPN is just silly. There's literally no good reason to do it unless you're trying to avoid bans, in which case I don't condone it at all.

Second, VPN by its very nature introduces delays. Packet authentication, encryption and decryption costs. You also add additional routing and fragmentation and reassembly into the mix. Moreover, you create a longer network path, because your packets are diverted via Linode to your destination.

Third, using 8.8.8.8 as a measure is a terrible idea to begin with, because Google likes to tap into national WAN exchanges and do MPLS voodoo with points of presence and caching and whatever other crap; 8.8.8.8 is a special magic IP address and when you send packets to it from two geographically different gateways there is a very good chance they arrive to different boxes in different countries, if not hemispheres.

t;dr a) don't do this b) if you do this don't expect good results c) your metrics is skewed because you're using a magic Google IP

@emestee:

First off, trying to play games over a VPN is just silly. There's literally no good reason to do it unless you're trying to avoid bans, in which case I don't condone it at all.

Second, VPN by its very nature introduces delays. Packet authentication, encryption and decryption costs. You also add additional routing and fragmentation and reassembly into the mix. Moreover, you create a longer network path, because your packets are diverted via Linode to your destination.

Third, using 8.8.8.8 as a measure is a terrible idea to begin with, because Google likes to tap into national WAN exchanges and do MPLS voodoo with points of presence and caching and whatever other crap; 8.8.8.8 is a special magic IP address and when you send packets to it from two geographically different gateways there is a very good chance they arrive to different boxes in different countries, if not hemispheres.

t;dr a) don't do this b) if you do this don't expect good results c) your metrics is skewed because you're using a magic Google IP

First off I don't condone hacking….

Next the reason for the vpn while gaming is for two reasons first issues with my internet service provider in the way they route traffic.. The traffic routing they do to bring me to the server seems to go through a location where i get 50 to 60% packet loss.. However i can avoid this under the vpn.. I think i got my problem figured out and things are working like they should it just sucks i have to use a vpn just to game……… Yes latency sucks..

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Log in to Reply
Community Code of Conduct