Errors trying to connect PC directly to ONT

Forums › Spark New Zealand (including Skinny and BigPipe) › Errors trying to connect PC directly to ONT

1 | 2

michaelmurfy

meow
13581 posts

Uber Geek
+1 received by user: 10914

Moderator

ID Verified

Trusted

Lifetime subscriber

#2424283 19-Feb-2020 22:50

My diagnosing of the issue has just been running tracerts and winMTR to the oceanic wow server ip and seeing latency spikes to certain hops, including the last hop at times. I have tried running ping in cmd and noticed dropped packets at times where the connection is particularly bad. I see this on all devices on my network when packet loss is occurring.

This is just what I posted in my first link. It is normal to see spikes on a traceroute, as-long as your end destination is what you call acceptable then you're fine.

What Fibre plan are you on? You mentioned it is only at these specific times, do you have something like a Torrent app running chewing up all your upstream bandwidth?

Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)

Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.

xolu

25 posts

Geek
+1 received by user: 1

#2424299 20-Feb-2020 02:21

michaelmurfy:
My diagnosing of the issue has just been running tracerts and winMTR to the oceanic wow server ip and seeing latency spikes to certain hops, including the last hop at times. I have tried running ping in cmd and noticed dropped packets at times where the connection is particularly bad. I see this on all devices on my network when packet loss is occurring.

This is just what I posted in my first link. It is normal to see spikes on a traceroute, as-long as your end destination is what you call acceptable then you're fine.

What Fibre plan are you on? You mentioned it is only at these specific times, do you have something like a Torrent app running chewing up all your upstream bandwidth?

I have gigabit fibre. We have a plex library that is occasionally accessed remotely, other than that I can think of anything that would be using significant bandwidth. I do live in a flat with other heavy internet users, but we havent had any problem with the connection for the past year and a half and noones usage habits have changed recently.

I would not call the latency im seeing to the end destination acceptable. If i run a ping to the end route i can see semi regular spikes from the normal 40ms to 80-150 on some returns. Its very noticeable in games, and I can match lag in game to results on the ping.

K8Toledo

1018 posts

Uber Geek
+1 received by user: 311

#2424307 20-Feb-2020 06:53

xolu:

I have gigabit fibre. We have a plex library that is occasionally accessed remotely, other than that I can think of anything that would be using significant bandwidth. I do live in a flat with other heavy internet users, but we havent had any problem with the connection for the past year and a half and noones usage habits have changed recently.

I would not call the latency im seeing to the end destination acceptable. If i run a ping to the end route i can see semi regular spikes from the normal 40ms to 80-150 on some returns. Its very noticeable in games, and I can match lag in game to results on the ping.

I would often see the ping spike from 50ms to 80-100ms intermittently . The effect in game is very noticeable when this occurs.

In all honesty a ping spike of ~50ms is gonna be unnoticeable. There must be another issue.

Have you played WoW offline yet - if not that's a good place to start the process of elimination. Also as @michaelmurfy said we really need other info such as hardware specs/OS/other running/installed apps etc....

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#2424310 20-Feb-2020 07:23

You're not gaming over WiFi are you?

xolu

25 posts

Geek
+1 received by user: 1

#2424382 20-Feb-2020 10:52

sbiddle:

You're not gaming over WiFi are you?

xolu

25 posts

Geek
+1 received by user: 1

#2424425 20-Feb-2020 10:56

K8Toledo:

In all honesty a ping spike of ~50ms is gonna be unnoticeable. There must be another issue.

Have you played WoW offline yet - if not that's a good place to start the process of elimination. Also as @michaelmurfy said we really need other info such as hardware specs/OS/other running/installed apps etc....

I don't know what you consider noticeable, I can only tell you what I consider noticeable. The latency spikes I am experiencing are very noticeable in game.

In terms of hardware, its a windows 10 pc built in 2015 or 2016 can't remember which. intel 4690k, gtx 970, that sort of age of components. I have tried closing just about every app on my system bar the one game I am attempting to play, but still experience latency spikes. There is no offline version of these games for me to try.

Lenovo

Shop now for Lenovo laptops and other devices (affiliate link).

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#2424451 20-Feb-2020 11:54

It's pretty hard for anybody to really offer anything else in the way of advice when you haven't provided any hard diagnostic evidence of issues.

Where and how are you seeing the added latency and how are you testing this?

Tracertoute / MTR increased latency on intermediate hops means nothing - it's how things work.

xolu

25 posts

Geek
+1 received by user: 1

#2425186 21-Feb-2020 21:51

Pinging 103.4.115.248 with 32 bytes of data:
Reply from 103.4.115.248: bytes=32 time=51ms TTL=243
Reply from 103.4.115.248: bytes=32 time=80ms TTL=243
Reply from 103.4.115.248: bytes=32 time=72ms TTL=243
Reply from 103.4.115.248: bytes=32 time=76ms TTL=243
Reply from 103.4.115.248: bytes=32 time=57ms TTL=243
Reply from 103.4.115.248: bytes=32 time=53ms TTL=243
Request timed out.
Reply from 103.4.115.248: bytes=32 time=60ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=47ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=43ms TTL=243
Reply from 103.4.115.248: bytes=32 time=45ms TTL=243
Reply from 103.4.115.248: bytes=32 time=57ms TTL=243
Reply from 103.4.115.248: bytes=32 time=54ms TTL=243
Reply from 103.4.115.248: bytes=32 time=64ms TTL=243
Reply from 103.4.115.248: bytes=32 time=42ms TTL=243
Reply from 103.4.115.248: bytes=32 time=74ms TTL=243
Reply from 103.4.115.248: bytes=32 time=57ms TTL=243
Reply from 103.4.115.248: bytes=32 time=75ms TTL=243
Reply from 103.4.115.248: bytes=32 time=74ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=83ms TTL=243
Request timed out.
Reply from 103.4.115.248: bytes=32 time=74ms TTL=243
Reply from 103.4.115.248: bytes=32 time=68ms TTL=243
Reply from 103.4.115.248: bytes=32 time=59ms TTL=243
Reply from 103.4.115.248: bytes=32 time=73ms TTL=243
Reply from 103.4.115.248: bytes=32 time=47ms TTL=243
Reply from 103.4.115.248: bytes=32 time=75ms TTL=243
Reply from 103.4.115.248: bytes=32 time=48ms TTL=243
Reply from 103.4.115.248: bytes=32 time=58ms TTL=243
Reply from 103.4.115.248: bytes=32 time=80ms TTL=243
Reply from 103.4.115.248: bytes=32 time=67ms TTL=243
Reply from 103.4.115.248: bytes=32 time=84ms TTL=243
Request timed out.
Reply from 103.4.115.248: bytes=32 time=75ms TTL=243
Reply from 103.4.115.248: bytes=32 time=62ms TTL=243
Reply from 103.4.115.248: bytes=32 time=74ms TTL=243
Reply from 103.4.115.248: bytes=32 time=75ms TTL=243
Reply from 103.4.115.248: bytes=32 time=62ms TTL=243
Reply from 103.4.115.248: bytes=32 time=77ms TTL=243
Reply from 103.4.115.248: bytes=32 time=56ms TTL=243
Reply from 103.4.115.248: bytes=32 time=70ms TTL=243
Reply from 103.4.115.248: bytes=32 time=79ms TTL=243
Request timed out.
Reply from 103.4.115.248: bytes=32 time=77ms TTL=243
Reply from 103.4.115.248: bytes=32 time=74ms TTL=243
Reply from 103.4.115.248: bytes=32 time=84ms TTL=243
Reply from 103.4.115.248: bytes=32 time=76ms TTL=243
Reply from 103.4.115.248: bytes=32 time=80ms TTL=243

Here is a sample of me pinging the oceanic wow server. When the connection was stable, I would be averaging 41ms with 1-2ms ping jitter. Ping like this is making the game unplayable.

xolu

25 posts

Geek
+1 received by user: 1

#2425191 21-Feb-2020 22:14

After turning my router and ONT off, I get results like the following:

Pinging 103.4.115.248 with 32 bytes of data:
Reply from 103.4.115.248: bytes=32 time=45ms TTL=243
Reply from 103.4.115.248: bytes=32 time=46ms TTL=243
Reply from 103.4.115.248: bytes=32 time=43ms TTL=243
Reply from 103.4.115.248: bytes=32 time=43ms TTL=243
Reply from 103.4.115.248: bytes=32 time=48ms TTL=243
Reply from 103.4.115.248: bytes=32 time=49ms TTL=243
Reply from 103.4.115.248: bytes=32 time=55ms TTL=243
Reply from 103.4.115.248: bytes=32 time=48ms TTL=243
Reply from 103.4.115.248: bytes=32 time=42ms TTL=243
Reply from 103.4.115.248: bytes=32 time=42ms TTL=243
Reply from 103.4.115.248: bytes=32 time=42ms TTL=243
Reply from 103.4.115.248: bytes=32 time=48ms TTL=243
Reply from 103.4.115.248: bytes=32 time=42ms TTL=243
Reply from 103.4.115.248: bytes=32 time=48ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=47ms TTL=243
Reply from 103.4.115.248: bytes=32 time=42ms TTL=243
Reply from 103.4.115.248: bytes=32 time=43ms TTL=243
Reply from 103.4.115.248: bytes=32 time=46ms TTL=243
Reply from 103.4.115.248: bytes=32 time=43ms TTL=243
Reply from 103.4.115.248: bytes=32 time=45ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=42ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=43ms TTL=243
Reply from 103.4.115.248: bytes=32 time=40ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=43ms TTL=243
Reply from 103.4.115.248: bytes=32 time=42ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=45ms TTL=243
Reply from 103.4.115.248: bytes=32 time=49ms TTL=243
Reply from 103.4.115.248: bytes=32 time=43ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=46ms TTL=243
Reply from 103.4.115.248: bytes=32 time=42ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=40ms TTL=243
Reply from 103.4.115.248: bytes=32 time=43ms TTL=243
Reply from 103.4.115.248: bytes=32 time=46ms TTL=243
Reply from 103.4.115.248: bytes=32 time=42ms TTL=243
Reply from 103.4.115.248: bytes=32 time=42ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=43ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=46ms TTL=243
Reply from 103.4.115.248: bytes=32 time=40ms TTL=243
Reply from 103.4.115.248: bytes=32 time=40ms TTL=243
Reply from 103.4.115.248: bytes=32 time=42ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=43ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=40ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243
Reply from 103.4.115.248: bytes=32 time=53ms TTL=243
Reply from 103.4.115.248: bytes=32 time=49ms TTL=243
Reply from 103.4.115.248: bytes=32 time=41ms TTL=243

much better, and I can actually play games with this, but even the slightly latency is noticeable at times, particularly if it gets back to the state of the test above. I don't have another router lying around to test with.

I'm not really sure if this indicates that my local network is struggling for some reason or whether its a problem on bigpipes end. Any other tests you can suggest I'm more than glad to try them.

michaelmurfy

meow
13581 posts

Uber Geek
+1 received by user: 10914

Moderator

ID Verified

Trusted

Lifetime subscriber

#2425211 22-Feb-2020 01:06

It would help if you would simply provide more information about your network, router type etc as asked on here.

Likely your router is simply just not up to the task...

K8Toledo

1018 posts

Uber Geek
+1 received by user: 311

#2425213 22-Feb-2020 01:23

xolu:

K8Toledo:

In all honesty a ping spike of ~50ms is gonna be unnoticeable. There must be another issue.

Have you played WoW offline yet - if not that's a good place to start the process of elimination. Also as @michaelmurfy said we really need other info such as hardware specs/OS/other running/installed apps etc....

I don't know what you consider noticeable, I can only tell you what I consider noticeable. The latency spikes I am experiencing are very noticeable in game.

In terms of hardware, its a windows 10 pc built in 2015 or 2016 can't remember which. intel 4690k, gtx 970, that sort of age of components. I have tried closing just about every app on my system bar the one game I am attempting to play, but still experience latency spikes. There is no offline version of these games for me to try.

I mean the lag may be caused by an underlying undetected problem with the local machine, possibly faulty hardware or low resources & the spikes are a result of this underlying problem.

The 50ms spikes on their own won't cause the lag which you describe.

Mighty Ape

Shop now at Mighty Ape (affiliate link).

xolu

25 posts

Geek
+1 received by user: 1

#2425219 22-Feb-2020 03:36

michaelmurfy:

It would help if you would simply provide more information about your network, router type etc as asked on here.

Likely your router is simply just not up to the task...

Its a netgear nighthawk r7000. Its been chugging along on this connection just fine for the past year and a half, but it may be ageing these days. I'm not sure what the expected lifespan of a router is, I've had this one for 6 years. It hasn't had any latency issues over the last year and a half on this bigpipe connection. I have been planning on replacing this router with something more capable. We have one switch connected to the router.

My home network consists of 5 moderate to heavy users all on ethernet connections. The ping issues are evident on all of our PCs when they are occurring, so I don't think it is an issue with any one person's PC. If there's any other relevant information that can help narrow this down please let me know. I have tried contacting bigpipe and the email replies I get just talk about slow connection speed, and suggest connecting directly to the ONT, hence this thread. Perhaps if I had some more specific measurements I can get some more direct help.

If I do connect to the ONT and still measure this same sort of latency jitter, on multiple PCs, will that narrow it down to whether it is a local network or bigpipe issue?

xolu

25 posts

Geek
+1 received by user: 1

#2426052 23-Feb-2020 21:56

I took this ping test from a PC that was directly connected to the ONT.

Pinging 103.4.115.248 with 32 bytes of data:
Reply from 103.4.115.248: bytes=32 time=50ms TTL=244
Reply from 103.4.115.248: bytes=32 time=56ms TTL=244
Reply from 103.4.115.248: bytes=32 time=48ms TTL=244
Reply from 103.4.115.248: bytes=32 time=46ms TTL=244
Reply from 103.4.115.248: bytes=32 time=49ms TTL=244
Reply from 103.4.115.248: bytes=32 time=41ms TTL=244
Reply from 103.4.115.248: bytes=32 time=48ms TTL=244

does this ping instability indicate that there is something wrong with the connection between me and bigpipe? I don't know if it is normal to see this sort of ping jitter when directly connected to the ONT. When I run this same test on my work connection (also gigabit fibre) there is no ping jitter at all.

michaelmurfy

meow
13581 posts

Uber Geek
+1 received by user: 10914

Moderator

ID Verified

Trusted

Lifetime subscriber

#2426065 23-Feb-2020 22:59

Your problem is the Nighthawk R7000 - it is too underpowered for your connection and usecase and not to mention it is an old router now.

Get a better router. Look at the Ubiquiti Dream Machine (https://www.pbtech.co.nz/product/NETUBI2200/Ubiquiti-UniFi-Dream-Machine) or buy a router from BigPipe.

No point posting anything more until you've solved the root cause. It is not a problem with BigPipe. It is your router.

Edit: Also a connection straight to your ONT will have some instabilities. In my experience the Windows PPPoE stack just isn't that good. Sort your router out instead, it isn't a problem with BigPipe as I've said multiple times now.

1 | 2