Default gateway
Description
The default gateway (often the router) is usually the first hop that a client sends network packets to. The default gateway test pings this network hop to measure the speed and reliability of the connection. A slow or lossy connection to the default gateway affects all connections of the client and is likely the root cause for experienced internet issues.
Parameters
Parameter | Value |
---|---|
Method | ICMP |
Target | Default gateway (taken from system profile) |
Number of measurements | 5 |
Warning threshold | 10 |
Critical threshold | 50 |
Status percentage | 21% |
Troubleshooting
Locate the issue
A bad connection can have many root causes and also be the cause for many other issues. Therefore, narrow down where and when issues occur. Use the general troubleshooting guide and try to answer these questions:
- Is it a client-specific or local issue?
- Are there other clients with a bad default gateway connection at the same location?
- Are there other related services with issues?
- Does performance issues relate to peaks in the device performance?
- Is the client using WiFi?
- How is the WiFi signal strength of this client?
If you find other services with issues also look at their test documentations.
Possible causes (status warning/critical):
WiFi signal bad
In case the client uses WiFi to connect to the default gateway the signal might be disturbed.
- Check if the WiFi signal strength test reports issue. If yes, look for solutions there.
WiFi interference
Sometimes the general signal strength is good, but there are many devices in your environment using WiFi and influencing each other.
- If possible use an ethernet cable to connect to the default gateway. Compare the measurements to see if the issues disappear.
Route to default gateway broken
In case the client uses an ethernet cable the cable or other components on the way to the router might be damaged.
- Change the connection to your default gateway (e.g. replace the ethernet cable or switch to WiFi). If that enhances the performance, test the network components on the way to the default gateway for damages.
Default gateway congested
Also the default gateway might be overloaded or has a lot of ongoing background tasks.
- Restart your default gateway and check if it improves the connection.
Possible causes (status error)
If the default gateway test errors then either the connection to the default gateway or the default gateway itself are responsible for that. This is unlikely to be influenced by other components or services.
No default gateway
If the device does not even know a default gateway, there is also no connection possible to it.
-
Check if there is a default gateway listed on the system profile. If there is none then the client is not connected to a default gateway.
-
To establish a connection make sure the default gateway (router) is running, your ethernet cable should be correctly mounted or your device should find and connect to the WiFi network of your default gateway (router).
-
Check the DHCP server and settings whether the client gets a valid configuration.
Default gateway does not answer
Althoug the address of the default gateway is known it might be the case that the default gateway is not answering to ICMP (ping) requests. Especially if your have an internet connection (so the other tests do not fail) this is likely to be the cause of this error.
-
Open
cmd
and ping your default gateway (take the deafault gateway ip address from the system profile). If the default gateway does not respond the connection to it can currently not be measured. Please report this to us. -
Consider allowing ICMP requests on your default gateway (if configurable) ot enhance the monitoring.