I have a setup that involves syncing files from my laptop to a server regularly. This has been working pretty well for a long time, apart from the odd verification failures. Both machines are WiFi-connected, so when I attempt to sync from a room far away from the WAP, the failure rates for larger files are higher, I would guess due to packet losses.
Today, I am sitting at the same spot I usually do this successfully with no issues, and I get errors after errors after errors. The odd one will go through after multiple tries, but generally it is just not working properly. I also got a broken pipe today during one attempt. This is not the first time it happens, and I feel crazy for thinking it is correlated to do bad weather, as if that should somehow affect my indoor WiFi quality…
Anyways, I tried to look at the rsync versions on the sender and receiver, and noticed that while both are the same application version number (3.2.7), they operate on different protocol versions (sender: 31, receiver: 32). I found this a bit odd, and I was unable to figure out how I would force my laptop to also use protocol version 32. I know I can pass a --protocol=NUM argument, but that seems to be used to force the sender to use an older version in case the receiver only has an older version, which is the opposite of my current situation.
And what is the likelihood that this is the cause of my woes?
Other people’s wifi can affect yours, and vice versa, if they are occupying the same channel(s).
Most likely something on that channel is spamming multicast. That kills most consumer wifi routers (in default settings). Usually something like a sonos or Google home broadcast group.
Could also be a camera that’s constantly transmitting, also occupying the channel for a long time.
But really, it could be anything.
Use an app like PingTools (Android) that can graph what is on each wifi channel. Check to find the cleanest channels in your area and configure your router to use that channel.
Failing that, if it’s on your network and you don’t know what it is…change your Wi-Fi password to kick everything off, then slowly re-add devices with the new password until you find the culprit.
If you’re curious and technically-minded, I highly recommend this write up: https://www.wiisfi.com/
I might (i.e. I definitely do) have a non-ideal setup at home that contributes to this, with the router/WPA, a RPi running HA with a Zigbee antenna just next to it, my server in the shelf next over and a Sonos above it. Worst of all, the server is running on WiFi and it is sat in immediate vicinity to my router. Why? Because I could not for the life of me make the ethernet transfer speeds be more than somewhere around 1-5 MiB/s, so I gave up. But considering these issues are so infrequent from this location I assume it is mostly due to outside interference.
And adding to that, …
… this scan shows that all discovered networks are occupying the same channels (98-114 it looks like). I have still not figured out what OpenWRT option to go for (the OpenWRT One, which I had originally planned, quickly became very expensive with imports and tolls that I ended up not buying, despite having decided to go for it). So I am using the stock ISP router, which I assume everyone else in my building are as well. And I have been unable to locate an option to change channels in its interface.
That is a resource I didn’t know I needed! Thanks :)