Topic on Talk:Troubleshooting guide/Network and multiplayer problems
This page shows the changes between two versions of a post by Mirh in the topic "Lag checklist" on Talk:Troubleshooting guide/Network and multiplayer problems.
You can see other versions of this post at its history page.
Line 1: | Line 1: | ||
− | 1. Check for physical layer problems (including exquisite [https://www.phoronix.com/scan.php?page=news_item&px=Intel-Linux-Radio-RFIM voodoo] like | + | 1. Check for physical layer problems (including exquisite [https://www.phoronix.com/scan.php?page=news_item&px=Intel-Linux-Radio-RFIM voodoo] like [https://www.smallnetbuilder.com/wireless/wireless-features/crappy-wireless-performance-it-could-be-your-laptop/ cpus] or [https://old.reddit.com/r/technology/comments/136g7y/usb_30_has_been_found_to_cause_interference_that/ USB 3] interfering with [https://www.pcmag.com/opinions/wireless-witch-the-truth-about-usb-30-and-wi-fi-interference wifi], or bugged devices flooding the [https://nitter.net/crazysim/status/1521738425396695040 internet] ''or'' [https://www.sciencetimes.com/articles/27435/20200924/old-tv-wipes-out-villages-broadband-telephone-service-more-18.htm electrical] network, or just [https://www.smallnetbuilder.com/wireless/wireless-features/wi-fi-ping-spikes-causes-and-fixes/ unluck]), e.g. if at least LAN operations are stable. |
− | 2. Do the usual speedtest | + | 2. Do the usual speedtest basic counterchecks. Though contrarily to the expectations they usually work with, latency (and in particular jitter) are more important than bandwidth. |
3. Make sure there are no lost packets. To be the most fair this should be done against whatever your server IP is, but usually <code>ping -t www.google.com</code> for a minute or two is just enough already. | 3. Make sure there are no lost packets. To be the most fair this should be done against whatever your server IP is, but usually <code>ping -t www.google.com</code> for a minute or two is just enough already. | ||
4. Last and perhaps least, maybe there's some [[Glossary:Port forwarding|NAT/port]] trickery going on. | 4. Last and perhaps least, maybe there's some [[Glossary:Port forwarding|NAT/port]] trickery going on. |