Menu
Reply
  • 16
  • 0
  • 0
TimmHield
Joining in
467 Views
Message 1 of 17
Flag for a moderator

Unstable Ping Wired Connection

I've had a lot of problems with online gaming in Battlefield 1. I've called Tech Support 7 or 8 times and had numerous power level tweaks, reset the router, identified some SNR issues etc etc. I had an engineer out on Monday who replace some wiring in the cabinet and replaced my SH2 with a SH3. It hasn't helped. I called again yesterday and was put through to 2nd level support who thought the issue might be with EA servers or the route to them. The tracert shows fine sometimes and others it's high. He didn't think it was to do with Virgin media network though. I've since run several tracerts and found high ping levels in the first 2-3 hops too so I'm not convinced it's beyond Virgin network. 

I've run pingplotter and a graph is shown here https://share.pingplotter.com/3itqojy7QQH 

Broadband QM is here but this was before the SH3 was replaced.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/ee846051bca74871830fa9232bf16a73019395f3-23-10-2017

Called Support again and the first level tech didn't understand what I was saying. He then said he'd put me through to 2nd level and I got the suspicion he was going to hang up.. and he did.

This is week 3 now and I can't play online without rubberbanding and feeling like I'm running through gravy.

HELP

https://www.thinkbroadband.com/broadband/monitoring/quality/share/ee846051bca74871830fa9232bf16a73019395f3-23-10-2017

Microsoft Windows [Version 10.0.15063]

(c) 2017 Microsoft Corporation. All rights reserved.

 

C:\Users\timmh>tracert 159.153.34.188

 

Tracing route to eu1bf1prgm0549.ea.com [159.153.34.188]

over a maximum of 30 hops:

 

  1     2 ms     2 ms     1 ms  192.168.0.1

  2    12 ms    14 ms    12 ms  10.216.68.1

  3    12 ms    14 ms    12 ms  leed-core-2b-xe-003-0.network.virginmedia.net [62.252.232.237]

  4     *        *        *     Request timed out.

  5     *        *        *     Request timed out.

  6    17 ms    14 ms    17 ms  nrth-ic-1-ae1-0.network.virginmedia.net [62.254.42.218]

  7    19 ms    24 ms    19 ms  m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]

  8    27 ms    48 ms    21 ms  ldn-b1-link.telia.net [213.248.84.25]

  9    28 ms    18 ms    21 ms  ldn-bb3-link.telia.net [62.115.114.234]

 10    35 ms    29 ms    29 ms  dln-b1-link.telia.net [62.115.119.243]

 11    27 ms    29 ms    29 ms  bioware-ic-147166-dln-b3.c.telia.net [80.239.192.78]

 12    34 ms    29 ms    46 ms  159.153.72.14

 13    29 ms    36 ms    28 ms  eu1bf1prgm0549.ea.com [159.153.34.188]

 

Trace complete.

 

C:\Users\timmh>tracert 159.153.34.188

 

Tracing route to eu1bf1prgm0549.ea.com [159.153.34.188]

over a maximum of 30 hops:

 

  1     2 ms     2 ms     1 ms  192.168.0.1

  2    14 ms     9 ms    12 ms  10.216.68.1

  3    11 ms    14 ms     9 ms  leed-core-2b-xe-003-0.network.virginmedia.net [62.252.232.237]

  4     *        *        *     Request timed out.

  5     *        *        *     Request timed out.

  6    20 ms    13 ms    19 ms  nrth-ic-1-ae1-0.network.virginmedia.net [62.254.42.218]

  7    20 ms    18 ms    21 ms  m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]

  8    25 ms    23 ms    24 ms  ldn-b1-link.telia.net [213.248.84.25]

  9    23 ms    16 ms    19 ms  ldn-bb3-link.telia.net [62.115.114.234]

 10    36 ms    29 ms    28 ms  dln-b1-link.telia.net [62.115.119.243]

 11    30 ms    34 ms    27 ms  bioware-ic-147166-dln-b3.c.telia.net [80.239.192.78]

 12    34 ms    30 ms    29 ms  159.153.72.14

 13    31 ms    30 ms    34 ms  eu1bf1prgm0549.ea.com [159.153.34.188]

 

Trace complete.

 

 

C:\Users\timmh>tracert 159.168.0.1

 

Tracing route to 159.168.0.1 over a maximum of 30 hops

 

  1     1 ms     2 ms     2 ms  192.168.0.1

  2   104 ms    12 ms    18 ms  10.216.68.1

  3   194 ms   192 ms   139 ms  leed-core-2a-xe-800-0.network.virginmedia.net [62.252.232.101]

  4     *        *        *     Request timed out.

  5     *        *        *     Request timed out.

  6     *        *        *     Request timed out.

  7    23 ms    24 ms    18 ms  tcl5-ic-5-ae0-0.network.virginmedia.net [62.254.84.66]

  8    25 ms    19 ms    37 ms  linx-2.init7.net [195.66.236.175]

  9    28 ms    44 ms    19 ms  r1lon2.core.init7.net [82.197.168.42]

 10    72 ms    70 ms    71 ms  r1bsl1.core.init7.net [77.109.128.102]

 11    41 ms    44 ms    42 ms  gw-litecom.init7.net [77.109.145.126]

 12    40 ms    44 ms    39 ms  83.144.193.17

 13    81 ms    68 ms    73 ms  159.168.0.1

 

Trace complete.

 

C:\Users\timmh>tracert 159.168.0.1

 

Tracing route to 159.168.0.1 over a maximum of 30 hops

 

  1     3 ms     4 ms     9 ms  192.168.0.1

  2    18 ms    17 ms    12 ms  10.216.68.1

  3    93 ms    96 ms    98 ms  leed-core-2a-xe-800-0.network.virginmedia.net [62.252.232.101]

  4     *        *        *     Request timed out.

  5     *        *        *     Request timed out.

  6     *        *        *     Request timed out.

  7    20 ms    18 ms    19 ms  tcl5-ic-5-ae0-0.network.virginmedia.net [62.254.84.66]

  8    23 ms    21 ms    24 ms  linx-2.init7.net [195.66.236.175]

  9    28 ms    24 ms    29 ms  r1lon2.core.init7.net [82.197.168.42]

 10    76 ms    48 ms    48 ms  r1bsl1.core.init7.net [77.109.128.102]

 11   164 ms   163 ms   168 ms  gw-litecom.init7.net [77.109.145.126]

 12    42 ms    41 ms    44 ms  83.144.193.17

 13    46 ms    44 ms    41 ms  159.168.0.1

 

Trace complete.

 

C:\Users\timmh>tracert 159.168.0.1

 

Tracing route to 159.168.0.1 over a maximum of 30 hops

 

  1     4 ms     1 ms     2 ms  192.168.0.1

  2    17 ms    18 ms    18 ms  10.216.68.1

  3    18 ms    11 ms    14 ms  leed-core-2a-xe-800-0.network.virginmedia.net [62.252.232.101]

  4     *        *        *     Request timed out.

  5     *        *        *     Request timed out.

  6     *        *        *     Request timed out.

  7    27 ms    21 ms    26 ms  tcl5-ic-5-ae0-0.network.virginmedia.net [62.254.84.66]

  8    38 ms    24 ms    24 ms  linx-2.init7.net [195.66.236.175]

  9    60 ms    24 ms    21 ms  r1lon2.core.init7.net [82.197.168.42]

 10    44 ms    43 ms    48 ms  r1bsl1.core.init7.net [77.109.128.102]

 11    53 ms    47 ms    46 ms  gw-litecom.init7.net [77.109.145.126]

 12    46 ms    44 ms    46 ms  83.144.193.17

 13    44 ms    42 ms    41 ms  159.168.0.1

 

Trace complete.

 

C:\Users\timmh>tracert 159.168.0.1

 

Tracing route to 159.168.0.1 over a maximum of 30 hops

 

  1     2 ms     1 ms     4 ms  192.168.0.1

  2    13 ms    11 ms    18 ms  10.216.68.1

  3   186 ms   169 ms    19 ms  leed-core-2a-xe-800-0.network.virginmedia.net [62.252.232.101]

  4     *        *        *     Request timed out.

  5     *        *        *     Request timed out.

  6     *        *        *     Request timed out.

  7    52 ms   100 ms    72 ms  tcl5-ic-5-ae0-0.network.virginmedia.net [62.254.84.66]

  8    93 ms    26 ms    23 ms  linx-2.init7.net [195.66.236.175]

  9   152 ms   166 ms   181 ms  r1lon2.core.init7.net [82.197.168.42]

 10    47 ms    79 ms    43 ms  r1bsl1.core.init7.net [77.109.128.102]

 11   175 ms   171 ms    96 ms  gw-litecom.init7.net [77.109.145.126]

 12    48 ms    43 ms    44 ms  83.144.193.17

 13   171 ms    39 ms    47 ms  159.168.0.1

 

Trace complete.

 

C:\Users\timmh>

C:\Users\timmh>tracert 159.168.0.1

 

Tracing route to 159.168.0.1 over a maximum of 30 hops

 

  1     1 ms     2 ms     1 ms  192.168.0.1

  2    11 ms     9 ms    14 ms  10.216.68.1

  3   144 ms   140 ms   151 ms  leed-core-2a-xe-800-0.network.virginmedia.net [62.252.232.101]

  4     *        *        *     Request timed out.

  5     *        *        *     Request timed out.

  6     *        *        *     Request timed out.

  7   144 ms   132 ms   139 ms  tcl5-ic-5-ae0-0.network.virginmedia.net [62.254.84.66]

  8    24 ms    26 ms    21 ms  linx-2.init7.net [195.66.236.175]

  9    90 ms   153 ms   159 ms  r1lon2.core.init7.net [82.197.168.42]

 10   189 ms    50 ms    50 ms  r1bsl1.core.init7.net [77.109.128.102]

 11   215 ms   189 ms    93 ms  gw-litecom.init7.net [77.109.145.126]

 12    41 ms    40 ms   187 ms  83.144.193.17

 13   191 ms    88 ms    44 ms  159.168.0.1

 

Trace complete.

C:\Users\timmh>tracert 159.168.0.1

 

Tracing route to 159.168.0.1 over a maximum of 30 hops

 

  1     6 ms     1 ms     2 ms  192.168.0.1

  2    44 ms    14 ms    16 ms  10.216.68.1

  3   101 ms    98 ms    94 ms  leed-core-2a-xe-800-0.network.virginmedia.net [62.252.232.101]

  4     *        *        *     Request timed out.

  5     *        *        *     Request timed out.

  6     *        *        *     Request timed out.

  7    23 ms    19 ms    18 ms  tcl5-ic-5-ae0-0.network.virginmedia.net [62.254.84.66]

  8    25 ms    24 ms    23 ms  linx-2.init7.net [195.66.236.175]

  9    23 ms    21 ms    26 ms  r1lon2.core.init7.net [82.197.168.42]

 10    40 ms    51 ms    51 ms  r1bsl1.core.init7.net [77.109.128.102]

 11    43 ms    39 ms    41 ms  gw-litecom.init7.net [77.109.145.126]

 12    44 ms    44 ms    43 ms  83.144.193.17

 13    43 ms    41 ms    44 ms  159.168.0.1

 

Trace complete.

 

C:\Users\timmh>tracert 159.153.34.188

 

Tracing route to eu1bf1prgm0549.ea.com [159.153.34.188]

over a maximum of 30 hops:

 

  1     1 ms     4 ms     6 ms  192.168.0.1

  2    22 ms    12 ms    16 ms  10.216.68.1

  3   111 ms   109 ms   109 ms  leed-core-2b-xe-003-0.network.virginmedia.net [62.252.232.237]

  4     *        *        *     Request timed out.

  5     *        *        *     Request timed out.

  6    29 ms    18 ms    22 ms  nrth-ic-1-ae1-0.network.virginmedia.net [62.254.42.218]

  7   176 ms   166 ms   140 ms  m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]

  8    19 ms    19 ms    17 ms  ldn-b1-link.telia.net [213.248.84.25]

  9    18 ms    19 ms    28 ms  ldn-bb3-link.telia.net [62.115.114.234]

^C

C:\Users\timmh>

 

C:\Users\timmh>tracert 159.153.34.188

 

Tracing route to eu1bf1prgm0549.ea.com [159.153.34.188]

over a maximum of 30 hops:

 

  1     3 ms     2 ms     1 ms  192.168.0.1

  2    12 ms    14 ms     9 ms  10.216.68.1

  3    11 ms    14 ms     8 ms  leed-core-2b-xe-003-0.network.virginmedia.net [62.252.232.237]

  4     *        *        *     Request timed out.

  5     *        *        *     Request timed out.

  6    19 ms    14 ms    54 ms  nrth-ic-1-ae1-0.network.virginmedia.net [62.254.42.218]

  7    19 ms    19 ms    19 ms  m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]

  8    16 ms    19 ms    19 ms  ldn-b1-link.telia.net [213.248.84.25]

  9    25 ms    19 ms    21 ms  ldn-bb3-link.telia.net [62.115.114.234]

 10    34 ms    29 ms    28 ms  dln-b1-link.telia.net [62.115.119.243]

 11    30 ms    29 ms    29 ms  bioware-ic-147166-dln-b3.c.telia.net [80.239.192.78]

 12    29 ms    29 ms    36 ms  159.153.72.14

 13    33 ms    28 ms    29 ms  eu1bf1prgm0549.ea.com [159.153.34.188]

 

Trace complete.

 

0 Kudos
Reply
  • 16
  • 0
  • 0
TimmHield
Joining in
432 Views
Message 2 of 17
Flag for a moderator

Re: Unstable Ping Wired Connection

Called again this morning. Was put through to Gadget Support (really?) who transferred me back. While explaining my problem yet again to tech support they transferred me again to Gadget Support as I was telling him my issue. I was pleasant and polite. 

Made a complaint.

0 Kudos
Reply
  • 514
  • 27
  • 121
deviousiphone
Rising star
428 Views
Message 3 of 17
Flag for a moderator

Re: Unstable Ping Wired Connection

By having your hub 2 replaced they have now actually made your problem worse. The CPU fault in the hub 3 itself causes latency and jitter problems in excess of 200ms, so add that to your previous fault and it really isn’t ideal at all.
0 Kudos
Reply
  • 514
  • 27
  • 121
deviousiphone
Rising star
420 Views
Message 4 of 17
Flag for a moderator

Re: Unstable Ping Wired Connection

Just as an observation by looking at your graph do you have anything hammering your upload? It looks like you may be saturating your upstream and this in itself causes latency problems, anything like p2p or game video broadcasting? Twitch or similar is what I mean.
0 Kudos
Reply
  • 16
  • 0
  • 0
TimmHield
Joining in
417 Views
Message 5 of 17
Flag for a moderator

Re: Unstable Ping Wired Connection

No. Nothing like that.

0 Kudos
Reply
  • 16
  • 0
  • 0
TimmHield
Joining in
416 Views
Message 6 of 17
Flag for a moderator

Re: Unstable Ping Wired Connection

PingPlotter.png

This is PingPlotter which I ran for a while last night. Hop 2 shows an average of 35ms which just isn't right.

0 Kudos
Reply
  • 9.01K
  • 759
  • 1.88K
Superuser
Superuser
382 Views
Message 7 of 17
Flag for a moderator

Re: Unstable Ping Wired Connection

First of all your tracerts are fine and will not explain any gaming lag, however, tracerts only show you what is happening in a split second of time and are only useful in showing where the congestion is happening. I have included an explaination on how tracerts work below.

Are you playing with a devices connected to the hub by ethernet cable or wirelessly?

The BQM is interesting. The section before 12pm shows occasional lag spikes which I think can be attributed to the Puma 6 issue with the Hub 3.

The section between 12 and 4pm looks like the connection has been hammered as cje85 suspects as it has clearly defined edges, might be you or a neighbour, or there was a local shortlived SNR fault.

As a sanity check, it would be worth posting the hub's power levels and network logs.

The section after 4pm shows the lag spikes getting more frequent and an increase of average latency. This can be espected during evening peak when your local node will be busier and maybe congested enough to disrupt online gaming somewhat, your pingplotter graph is going into the yellow and red suggesting the ping is high enough to cause lag.it maybe worth doub;e clicking on a area of the time graph where the ping is going into the yellow to see what affect it has on the route trace.

A VM Forum Team member should be able to advise you on the traffic levels on your local node when they pick up the thread.

 

Tracerts

A Source computer will send a series of ICMP packets to a Target server with a ICMP Timeout Echo Request and a Time to Live Value.

The first series of ICMP packets will be sent with a TTL value of 1.

The first server on the route will decrease the TTL value by 1.

So, once the first series of ICMP packets reach the first server the TTL balue is reduced by 1 to 0 and the packets time out. The server at hop 1 is a polite server and responds to the source with a ICMP Timeout echo containing a timestamp when the packets timed out. From the time the source sent the packets and the timestamp contained in the Timeout Echo the Source can work out the Round Time Trip.

The Source now sends a second set of ICMP packets which reach the server at Hop 1 which reduces the TTL value by 1 and sends the packets on their merry way towards the Target.

The Server at Hop 2 reduces the TTL value by 1 so the new TTL value is 0 and the packet times out. This time though, the Server is busy and as ICMP packets are low priority as they carry no data, the Server at Hop 2 takes it's time replying to the Timeout Echo Request as it is doing more important things like making the coffee.

Once the Source has recieved the Timeout Echo from the Server at Hop 2 the Source sends another series of ICMP packets increasing the TTL value to 3. The ICMP packets make their way to the Target Server through the Servers at Hop 1 and Hop 2 which reduce the TTL by 1 to the Server at Hop 3 which reduces the TTL value by 1so the TTL value is 0 again and the packets time out. This time the Server is configured to ignore ICMP Timeout Echo Requests and does not reply to the Source. The Source does not receive a reply and times out showing a star for that Hop.

The Source now sends another series of ICMP packets to the target with a TTL value of 4. This time the Server at Hop 4 replies to the ICMP Timeout Echo Request in a timely manner.

The Source will carry on sending ICMP packets to the Target Server with increasing TTL values until the Target Server is reached (or the Max Hop Value)

It is the last hop that is important.

For example, taking the tracerts you have highlighted in red you noticed a high ping at Hop 3, ok that might be a problem, but on further inspection of the route the end hop has a much lower ping and do all other susequent hops along the route. So, this indicates the Server at Hop 3 is configured to treat ICMP Timeout Echo requests as low priority.

In your last post you again noticed a high ping at Hop 3. This time though all susequent pings are higher and more importantly the last hop is as well. This time you have diagnosed the tracert perfectly. However, I do not think the ping time at the end of the trace is high enough to cause any problems with online gaming.

0 Kudos
Reply
  • 16
  • 0
  • 0
TimmHield
Joining in
326 Views
Message 8 of 17
Flag for a moderator

Re: Unstable Ping Wired Connection

Thanks for your post Griffin. Just a few points below.

I'm playing via PC and Ethernet 1m from the superhub.

The BQM was while I had the SH2 rather than the replaced SH3.

The problem is the same on SH2 & SH3.

I've played Battlefield 1 since release in October 2016 at the same times of day on the same PC and it's been absolutely fine. Whatever's happened has happened in the past fortnight. I only use the PC for this and nothing else and haven't installed anything new on it or changed it.
0 Kudos
Reply
  • 9.01K
  • 759
  • 1.88K
Superuser
Superuser
323 Views
Message 9 of 17
Flag for a moderator

Re: Unstable Ping Wired Connection

The distance from the hub has no bearing when connected to the hub by ethernet cable, you are only governed by the length of ethernet cable connecting the PC to the hub.

When did you get the Hub 3?

Have you had a good gaming experience with the Hub 3 all times of day in the past?

A Ping plot during the day would be handy for comparison against the pingpot during the evening.

It will stil be useful to post the power levels and logs to see if there is an obvious circuit impairment.

As  said previously a VM Forum team membercan advise on the level of traffic on your local node. it could be an increase in local traffic componding the Puma 6 to a level where the ping spikes cause lag.

0 Kudos
Reply
  • 16
  • 0
  • 0
TimmHield
Joining in
291 Views
Message 10 of 17
Flag for a moderator

Re: Unstable Ping Wired Connection

I got the SH3 last Wednesday (6 days ago) following the engineer coming to see if he could find a problem. So I've not had a good gaming experience with the SH3 at all or with the SH2 in the past fortnight.

I'll look at the power levels tonight and post them.
0 Kudos
Reply