Linux

64338 readers

672 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

rsync - same application version, but different protocol versions? (lemmy.ml)

submitted 20 hours ago by cyberwolfie@lemmy.ml to c/linux@lemmy.ml

15 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] JasonDJ@lemmy.zip 1 points 17 hours ago* (last edited 17 hours ago)

In OpenWRT, I believe it's in the settings for the "primary" ssid on each radio, which is usually the first one in the list (per radio) on the wireless settings page.

Openwrt also has options to block multicast or convert to unicast. Also make sure you are disabling lower speeds on the radio. That will reduce your max range, but devices that communicate slowly are another killer.

Broadcast and multicast both have to go at the ssid basic rate...the slowest speed supported by the AP. That could be 1Mbps. And then the AP has to repeat it. And depending on the type of traffic, this may also initiate more broadcasts from other devices on the network.

So if you can reduce broadcast/multicast, or increase the minimum speed, you'll have significantly more time. Since wireless is a shared medium, "time" is really the most critical resource.