Ping Problems

[n3mooce]

So I am having a problem with my network. Randomly my ping will spike which could last a few seconds to a few minutes. In my testing I was able to reach a ping of 3812ms delay to when performing a ping command to the address (ping-oce.ds.on.epicgames.com). When performing a traceroute to the link mentioned before the first hop was <1 ms then it jumped. I have tried to use a VPN with no avail, My pc is on ethernet and also has wifi, the problem is consistent on all devices, I have rebooted the router and am at a dead end as I have no idea what to do. 

Any help would be greatly appriciated

[david64]

Hi @n3mooce . You need to check that no device is doing periodic uploads or downloads. The router might be able to display activity on connected devices. Windows has Task Manager Networking tab. It also has Performance tab to show what CPUs are doing.

In tracert, the first address is the router's local address; always around 1 ms. 

Are you saying that the response time to the router jumps to high value? OR, does the response time to the second address jump. Can you copy in your tracert showing long response time.

Use the ethernet computer for the following:

in a command window, do:      ping -t 192.168.1.1

Let it run until response time jumps. Use Control C to stop.

[n3mooce]

This is the completed traceroute whilist the ping to the server was high.

Tracing route to ping-oce.ds.on.epicgames.com [3.25.159.51]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 332 ms 334 ms 339 ms 10.20.23.10
3 499 ms 518 ms 515 ms 60-240-241-22.static.tpgi.com.au [60.240.241.22]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 197 ms 116 ms 111 ms 15.230.210.74
10 38 ms 42 ms 30 ms 15.230.210.65
11 462 ms 417 ms 448 ms 15.230.210.144
12 548 ms 582 ms 580 ms 15.230.211.28
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 22 ms 22 ms 22 ms ec2-3-25-159-51.ap-southeast-2.compute.amazonaws.com [3.25.159.51]

Trace complete.

[david64]

@n3mooce . There is something wrong in the NBN network. The response to 2nd address should be a few ms.

Can you do the ping -t to the 2nd address. Let it run until the jump occurs and then drops back. Copy and paste into your reply. The moderator will need this as proof.

Can you check there is no other activity on your computer or other devices.

What type of NBN connection do you have? And what model router?

[n3mooce]

Reply from 10.20.23.10: bytes=32 time=10ms TTL=254
Reply from 10.20.23.10: bytes=32 time=38ms TTL=254
Reply from 10.20.23.10: bytes=32 time=11ms TTL=254
Reply from 10.20.23.10: bytes=32 time=11ms TTL=254
Reply from 10.20.23.10: bytes=32 time=11ms TTL=254
Reply from 10.20.23.10: bytes=32 time=16ms TTL=254
Reply from 10.20.23.10: bytes=32 time=11ms TTL=254
Reply from 10.20.23.10: bytes=32 time=11ms TTL=254
Reply from 10.20.23.10: bytes=32 time=22ms TTL=254
Reply from 10.20.23.10: bytes=32 time=33ms TTL=254
Reply from 10.20.23.10: bytes=32 time=11ms TTL=254
Reply from 10.20.23.10: bytes=32 time=18ms TTL=254
Reply from 10.20.23.10: bytes=32 time=18ms TTL=254
Reply from 10.20.23.10: bytes=32 time=110ms TTL=254
Reply from 10.20.23.10: bytes=32 time=213ms TTL=254
Reply from 10.20.23.10: bytes=32 time=783ms TTL=254
Reply from 10.20.23.10: bytes=32 time=1140ms TTL=254
Reply from 10.20.23.10: bytes=32 time=623ms TTL=254
Reply from 10.20.23.10: bytes=32 time=483ms TTL=254
Reply from 10.20.23.10: bytes=32 time=133ms TTL=254
Reply from 10.20.23.10: bytes=32 time=208ms TTL=254
Reply from 10.20.23.10: bytes=32 time=779ms TTL=254
Reply from 10.20.23.10: bytes=32 time=305ms TTL=254
Reply from 10.20.23.10: bytes=32 time=97ms TTL=254
Reply from 10.20.23.10: bytes=32 time=16ms TTL=254
Reply from 10.20.23.10: bytes=32 time=13ms TTL=254
Reply from 10.20.23.10: bytes=32 time=141ms TTL=254
Reply from 10.20.23.10: bytes=32 time=20ms TTL=254
Reply from 10.20.23.10: bytes=32 time=13ms TTL=254
Reply from 10.20.23.10: bytes=32 time=111ms TTL=254
Reply from 10.20.23.10: bytes=32 time=12ms TTL=254
Reply from 10.20.23.10: bytes=32 time=508ms TTL=254
Reply from 10.20.23.10: bytes=32 time=440ms TTL=254
Reply from 10.20.23.10: bytes=32 time=663ms TTL=254
Reply from 10.20.23.10: bytes=32 time=377ms TTL=254
Reply from 10.20.23.10: bytes=32 time=283ms TTL=254
Reply from 10.20.23.10: bytes=32 time=14ms TTL=254
Reply from 10.20.23.10: bytes=32 time=12ms TTL=254
Reply from 10.20.23.10: bytes=32 time=216ms TTL=254
Reply from 10.20.23.10: bytes=32 time=11ms TTL=254
Reply from 10.20.23.10: bytes=32 time=14ms TTL=254
Reply from 10.20.23.10: bytes=32 time=31ms TTL=254

Ping statistics for 10.20.23.10:
Packets: Sent = 346, Received = 346, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 1140ms, Average = 33ms

I dont think there is any activity on the router, I am using 2 Orbi RBR50 routers connected in a mesh network. I believe we have FTTN. 

[david64]

@n3mooce . You need to connect your computer to the main router directly to rule out the Orbis.

What model is the main router?

FTTN means the main router connects to telephone wall socket (no NBN box).

The router should be able to display DSL statistics showing the performance of the telephone line to the node: number of errors.

[n3mooce]

I believe that the other router isnt set up as a router but a stand alone modem. I checked the orbi view and there were no number of errors. Is there anything that I can try or am I out of luck.

[david64]

@n3mooce . I still don't understand your setup.

If you really are on FTTN, you must have a router with an RJ11 port (eg. VR1600) to connect to the telephone wall socket. This router would normally operate in Bridge mode so the Orbi router would control your local network (does DHCP, NAT, wifi, etc). The Orbi Internet port connects to a LAN port on main router.

In this mode, the Orbi never sees any link errors because they're all handled by the main router.

If this is your setup, you must connect your ethernet computer to the Orbi router to do any testing. This eliminates any wifi issues between Orbi units.

(With this setup, you assume there is no problem between Orbi router and main router. To properly test, the main router would have to be restored to normal wireless router mode. You can then access its DSL statistics. But you might not want to go that far.)

The Orbi router has port statistics: Advanced, Internet Port, Show Statistics. It shows activity on WAN and LAN ports. Monitor the WAN port for a few minutes; check there is no large data being sent or received.

Then run the ping -t command until response time jumps.

With FTTN, it's possible there is a fault on the telephone line back to the node.

[n3mooce]

I Am using a Tp link VR1600V VER:2.0, my dad has set up all of the modem and routing, there is a cable plugged into the dsl port on the back aswell as a cable plugged into the yellow part of the modem. How would I go about being able to view all of the statistics and if it turns out to be a problem with the cable how would I get it fixed. If not the modem could having ipv6 disabled cause problems like this?

[david64]

@n3mooce . TPG network doesn't use IPv6 so keep it disabled.

If testing proves it to be a line fault back to node, TPG will organise with NBNCo for them to fix.

Suggest to create a new thread summarising situation. You can include a link back to this thread.

The VR1600 is in bridge mode. Orbi router does PPPoE.

Do these tests on ethernet computer connected to Orbi router.

tracert -h 3 tpg.com.au

Just to check the address on line 2 in case it has changed in the last few days.

Open 2 command windows. In one, do     ping -t 192.168.1.1

This response time should stay around 1 ms.

In the other, do    ping -t  <address in line 2>

Let them run side by side until you get the long response time and then goes back to normal.

Copy and paste the long response time output into the thread.

You should check again there is no other activity. Turn off remote Orbi. Check the Orbi router WAN port statistics. These should be only minor activity if no-one is doing anything.

Indicate that there's no other activity.