NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
itsthelag
Apr 21, 2020Aspirant
DoS Attacks - from varying sources and ports.
Hi There, Since all the working from home started - I've noticed sporadic interruptions while using Video conferencing and while gaming. I will get ping spikes for about 3-5 mins and then it's prett...
itsthelag
Apr 21, 2020Aspirant
Thank you for the advice - checking that won't leave me open to other security issues?
I downloaded a tool called ping plotter, and I really just don't know what i'm looking at - are these ping/latency spikes unusual?
FURRYe38
Apr 21, 2020Guru - Experienced User
No, those are not good
Did you test pings with a wired PC connected directly connected to the modem? Not with the RBR connected.
Have the ISP check the signal and line quality UP to the modem.
Be sure there are not coax cable line splitters in the between the modem and ISP service box.
Be sure your using good quality RG6 coax cable up to the modem.
- itsthelagApr 21, 2020Aspirant
Unfortunately, I don't have a way to connect a PC to the modem directly, I use a Surface book pro, which doesn't have an ethernet port. Does it look like the ISP is causing the issue?
I had XFINITY refresh the gateway signal - I will try to get them to look at this more in depth. No coax splitters - direct from the wall into the modem. Everything was working fine until last week when this started happening. I've never had these issues before.
- FURRYe38Apr 21, 2020Guru - Experienced User
Does your Surface have a USB port? If so, you might check into getting a USB to LAN adapter. Then you can connect it to the ISP Modem and test again. Need to rule out the RBR or modem.
If this was not a problem up to that point, then possible something on the ISP side.
- itsthelagApr 21, 2020Aspirant
I connected my dock to the Orbi satellite and pinged 8.8.8.8, got flawless results - removed that and right back to ping spikes - could that be an indicator of issues? still would not explain the ping spikes i'm seeing on console because it's connected to the satellite as well. I also pinged my WAN IP and got similar results.
ping -n 36 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data
Reply from 8.8.8.8: bytes=32 time=21ms TTL=53
Reply from 8.8.8.8: bytes=32 time=19ms TTL=53
Reply from 8.8.8.8: bytes=32 time=21ms TTL=53
Reply from 8.8.8.8: bytes=32 time=21ms TTL=53
Reply from 8.8.8.8: bytes=32 time=18ms TTL=53
Reply from 8.8.8.8: bytes=32 time=19ms TTL=53
Reply from 8.8.8.8: bytes=32 time=19ms TTL=53
Reply from 8.8.8.8: bytes=32 time=19ms TTL=53
Reply from 8.8.8.8: bytes=32 time=18ms TTL=53
Reply from 8.8.8.8: bytes=32 time=19ms TTL=53
Reply from 8.8.8.8: bytes=32 time=18ms TTL=53
Reply from 8.8.8.8: bytes=32 time=23ms TTL=53
Reply from 8.8.8.8: bytes=32 time=21ms TTL=53
Reply from 8.8.8.8: bytes=32 time=17ms TTL=53
Reply from 8.8.8.8: bytes=32 time=18ms TTL=53
Reply from 8.8.8.8: bytes=32 time=18ms TTL=53
Reply from 8.8.8.8: bytes=32 time=23ms TTL=53
Reply from 8.8.8.8: bytes=32 time=18ms TTL=53
Reply from 8.8.8.8: bytes=32 time=18ms TTL=53
Reply from 8.8.8.8: bytes=32 time=24ms TTL=53
Reply from 8.8.8.8: bytes=32 time=19ms TTL=53
Reply from 8.8.8.8: bytes=32 time=17ms TTL=53
Reply from 8.8.8.8: bytes=32 time=17ms TTL=53
Reply from 8.8.8.8: bytes=32 time=23ms TTL=53
Reply from 8.8.8.8: bytes=32 time=20ms TTL=53
Reply from 8.8.8.8: bytes=32 time=19ms TTL=53
Reply from 8.8.8.8: bytes=32 time=18ms TTL=53
Reply from 8.8.8.8: bytes=32 time=21ms TTL=53
Reply from 8.8.8.8: bytes=32 time=19ms TTL=53
Reply from 8.8.8.8: bytes=32 time=18ms TTL=53
Reply from 8.8.8.8: bytes=32 time=23ms TTL=53
Reply from 8.8.8.8: bytes=32 time=20ms TTL=53
Reply from 8.8.8.8: bytes=32 time=19ms TTL=53
Reply from 8.8.8.8: bytes=32 time=18ms TTL=53
Reply from 8.8.8.8: bytes=32 time=21ms TTL=53
Reply from 8.8.8.8: bytes=32 time=19ms TTL=53Ping statistics for 8.8.8.8:
Packets: Sent = 36, Received = 36, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 24ms, Average = 19msDisconnected results:
ping -n 36 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data
Reply from 8.8.8.8: bytes=32 time=24ms TTL=53
Reply from 8.8.8.8: bytes=32 time=22ms TTL=53
Reply from 8.8.8.8: bytes=32 time=19ms TTL=53
Reply from 8.8.8.8: bytes=32 time=20ms TTL=53
Reply from 8.8.8.8: bytes=32 time=24ms TTL=53
Reply from 8.8.8.8: bytes=32 time=19ms TTL=53
Reply from 8.8.8.8: bytes=32 time=20ms TTL=53
Reply from 8.8.8.8: bytes=32 time=24ms TTL=53
Reply from 8.8.8.8: bytes=32 time=22ms TTL=53
Reply from 8.8.8.8: bytes=32 time=230ms TTL=53
Reply from 8.8.8.8: bytes=32 time=195ms TTL=53
Reply from 8.8.8.8: bytes=32 time=367ms TTL=53
Reply from 8.8.8.8: bytes=32 time=20ms TTL=53
Reply from 8.8.8.8: bytes=32 time=88ms TTL=53
Reply from 8.8.8.8: bytes=32 time=19ms TTL=53
Reply from 8.8.8.8: bytes=32 time=19ms TTL=53
Reply from 8.8.8.8: bytes=32 time=21ms TTL=53
Reply from 8.8.8.8: bytes=32 time=21ms TTL=53
Reply from 8.8.8.8: bytes=32 time=19ms TTL=53
Reply from 8.8.8.8: bytes=32 time=19ms TTL=53
Reply from 8.8.8.8: bytes=32 time=18ms TTL=53
Reply from 8.8.8.8: bytes=32 time=25ms TTL=53
Reply from 8.8.8.8: bytes=32 time=21ms TTL=53
Reply from 8.8.8.8: bytes=32 time=22ms TTL=53
Reply from 8.8.8.8: bytes=32 time=167ms TTL=53
Reply from 8.8.8.8: bytes=32 time=125ms TTL=53
Reply from 8.8.8.8: bytes=32 time=295ms TTL=53
Reply from 8.8.8.8: bytes=32 time=20ms TTL=53
Reply from 8.8.8.8: bytes=32 time=21ms TTL=53
Reply from 8.8.8.8: bytes=32 time=21ms TTL=53
Reply from 8.8.8.8: bytes=32 time=22ms TTL=53
Reply from 8.8.8.8: bytes=32 time=19ms TTL=53
Reply from 8.8.8.8: bytes=32 time=19ms TTL=53
Reply from 8.8.8.8: bytes=32 time=21ms TTL=53
Reply from 8.8.8.8: bytes=32 time=19ms TTL=53
Reply from 8.8.8.8: bytes=32 time=22ms TTL=53Ping statistics for 8.8.8.8:
Packets: Sent = 36, Received = 36, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 367ms, Average = 57ms