ping spikes

If you’re talking about the game-server time, I’d want to isolate that to the WiFi network first, to be sure that it’s not something related to the router-ISP connection or a network issue even further out. You can do something like run mtr (which does repeated traceroutes) to see at what hop the latency starts increasing. Or leave ping running pinging your router’s IP address, the first hop you see if you run a traceroute or mtr. If it’s your WiFi connection, then the latency should be spiking specifically to your router, at the first hop, and you might see packet loss. If it’s an issue further down the network, then that’s where you’ll start seeing latency increase and packet loss.

You might need to install mtr — I don’t know whether Fedora has it installed by default.

Please help. I don’t want to go beneath house to run cat6. It’s dark and there are spiders.

Honestly, I think that everyone should use wired Ethernet unless they need their device to be able to move around, as it maintains more-consistent and lower network latency, provides higher bandwidth, and keeps the Ethernet traffic off the air; 2.4 GHz is used for all sorts of other useful things, like gamepad controllers (I have a Logitech F710 that uses a proprietary 2.4GHz protocol, and at some point, when some other 2.4GHz device showed up, it caused loss of connectivity for a few seconds, which was immensely frustrating). And you have interference from stuff like microwaves and all that at the same frequency range. Avoids some security issues; we’ve had problems discovered with wireless protocols.

But, all right. I won’t lecture. It’s your network.

If you think that it’s Fedora and maybe your driver is at fault, one thing you might check is your kernel logs. If the driver is hitting some kind of problem and then recovering by resetting the interface, that might cause momentary drop-outs. After it happens, take a gander at $ journalctl -krb which will show your kernel log for the current boot in reverse order, with the most-recent stuff up top. If you have messages about your wireless driver, that’d be pretty suspicious.

If the driver is at fault, I probably don’t have a magic fix, unless you want to try booting into an older kernel, which may still be viable; if you still have it installed and GRUB, the bootloader that Linux distros typically use, is set up to show your list of kernels at boot, then you can try choosing that older kernel and see if it works with your newer distro release and if the problem goes away. I don’t know if Fedora defaults to showing such a list or hides it behind some splash screen; it used to do so, but I haven’t used Fedora in quite some years. You might want to whack Shift or an arrow key during boot to get boot to stop at GRUB. If you discover that it’s a regression in the driver, I’d submit a bug report (“no problems with kernel version X, these messages and momentary loss of connectivity with kernel version Y”) which would probably help get it actually fixed in an update.

You might also try just using a different wireless Ethernet interface, like a USB wireless Ethernet interface, and seeing if that magically makes it go away. Inexpensive USB interfaces are maybe $10 or $15. I’d probably look for some indication that it’s a driver problem before doing that.