F5F Stay Refreshed Power Users Networks Data transmission errors

Data transmission errors

Data transmission errors

X
xXJay_BugXx
Senior Member
559
02-01-2023, 03:00 PM
#1
Yea,so yesterday i posted that i might've been Dos'd,turns out i have huge packet loss. Anyone know how to deal with that. I installed ping locator, and here are the lossess
X
xXJay_BugXx
02-01-2023, 03:00 PM #1

Yea,so yesterday i posted that i might've been Dos'd,turns out i have huge packet loss. Anyone know how to deal with that. I installed ping locator, and here are the lossess

L
LoganChester
Junior Member
1
02-06-2023, 11:16 AM
#2
Check for packet loss within your local network or across the internet. If it’s over the internet, contact your ISP. Otherwise, inspect your network equipment. For example, run a ping to your router and observe the loss rate: ping -t 192.168.1.1 (replace with real IP). Stop the ping with Ctrl+C and note the number of lost packets. If it’s normal, test a stable external server, such as Google’s DNS ping at -t 8.8.8.8. Repeated loss suggests reaching out to your ISP.
L
LoganChester
02-06-2023, 11:16 AM #2

Check for packet loss within your local network or across the internet. If it’s over the internet, contact your ISP. Otherwise, inspect your network equipment. For example, run a ping to your router and observe the loss rate: ping -t 192.168.1.1 (replace with real IP). Stop the ping with Ctrl+C and note the number of lost packets. If it’s normal, test a stable external server, such as Google’s DNS ping at -t 8.8.8.8. Repeated loss suggests reaching out to your ISP.

A
Alterfuse
Member
67
02-06-2023, 07:34 PM
#3
Checking your router is a smart move. You should usually notice less than 1ms, ideally no more than 2ms over a wired link. If you exceed that or see "No Response," the issue is likely local. Once confirmed fine, visit packetlosstest.com to investigate further with your ISP and determine if the problem lies there. I recently faced this with my ISP—it turned out there was corrosion on a connection port.
A
Alterfuse
02-06-2023, 07:34 PM #3

Checking your router is a smart move. You should usually notice less than 1ms, ideally no more than 2ms over a wired link. If you exceed that or see "No Response," the issue is likely local. Once confirmed fine, visit packetlosstest.com to investigate further with your ISP and determine if the problem lies there. I recently faced this with my ISP—it turned out there was corrosion on a connection port.

S
SausageFrog
Member
151
02-14-2023, 12:34 AM
#4
ICMP offers limited value; heavy systems may discard it under high CPU use. It looks like your initial hop is failing, pointing to congestion or other issues. Using a device that monitors interfaces is often more effective because it lets you instantly track traffic levels.
S
SausageFrog
02-14-2023, 12:34 AM #4

ICMP offers limited value; heavy systems may discard it under high CPU use. It looks like your initial hop is failing, pointing to congestion or other issues. Using a device that monitors interfaces is often more effective because it lets you instantly track traffic levels.