Lag: Difference between revisions
→Ping and Packet loss
(justify text) |
|||
Line 74:
==== Command line tools ====
<div align="justify">
* To monitor the ping, you can open terminal and use the following command `ping -t <your server IP or domain name>`. This will continuously check send ping requests to the server.
* To get the detailed route your packets are following to reach the server, run `tracert <your server IP or domain name>` on windows, or `traceroute <your server IP or domain name>` This will give you the nodes your traffic is going through, as well as your ping between you and them during the traceroute. Handy to find if there is a troublesome node ruining your traffic. If you see some nodes being named `*` it's normal, some nodes are configured to ignore ping requests (what does the traceroute behind the scenes) for security or performance reasons.
* on Linux, you can install MTR, for Matt's TraceRoute, it's a tool being a bit more precise than ping+traceroute combo, as it also gives the packet loss rate to each node. to use it, simply run `mtr <your server ip or domain name>`
</div>
==== GUI software ====
[[File:WinMTR interface.png|alt=The interface of WinMTR|thumb|The interface of WinMTR]]
<div align="justify">
* On windows, you can use WinMTR, it's basically an interface for the MTR program. Nodes configured to ignore ping requests will always labeled with a packet loss rate of 100% and this is normal.
* VPNs can help you avoid troublesome nodes by being rerouted to the exit point of the VPN before trying to reach the server. This can work, but you need to monitor your connection with a MTR like software, and keep switching to other VPN endpoints until you find one. This technique is advised if you have a very low ping by default, as the VPN increases the length of the route, which increases the ping. It can be worth to have a higher ping but with no packet loss, as regular packet loss is worth than high ping. '''There is a flaw to this method: if the faulty node is too close to you or to the server, no matter what VPN you use, you'll end up going through the faulty node.'''
</div>
=== Server load ===
| |||