9d425b0588
Before: - Local discovery on Android 10+ is broken. The phone receives local discovery packets from other devices running Syncthing on the same network, e.g. a computer. But it doesn't send its own local discovery packets. - Startup of the beacon/broadcast.go and beacon/multicast.go "services" subsequently fail, see the log entries of "service.go" with "2 of 2 failures, backing off". Root cause: - Android 10+ restricts determining the network interfaces for privacy reasons. The interfaces and IP addresses cannot be determined. - There's a bug in the go "net" library. I can actually get the interfaces, but the fix was not implemented by the go team. Workaround: - The "community" found a workaround by creating a light wrapper around "net" called "anet" library. - "anet" adjusts the behaviour on Android 10+ and gets the interfaces plus their IP addresses, as required by Syncthing. After: - By using the "anet" lib, Syncthing is able to get the interface ip addresses and put them into the "AllAddresses" string array. - The "AllAddresses" string array is then announced on the local discovery multicast and broadcast packets, if enabled in Syncthing's config. - By correctly getting the interfaces and IP addresses using "anet" in "beacon/broadcast.go" and "beacon/multicast.go", the services start up fine again. Verification: - I've built "libSyncthingNative.so" with this PR applied for Android and put it into Syncthing-Fork v1.29.7.5 for testing. My two phones, Android 10 and Android 15 (arm64-v8a) immediately discovered each other using local discovery. - I can see the "sent XX bytes" and "recv XX bytes" on both phones in the log filtering for "SyncthingNativeCode" :-). Personal note: - Please go light on me, and, if it's not demanded too much of your time, please help me on this. I am no go programmer. Most things you think are easy or common sense aren't part of my knowledge set. I'd just like to help and hope we somehow can drive this home together to fix the problem. ---- ref: https://github.com/Catfriend1/syncthing-android/pull/1501 ref: https://github.com/Catfriend1/syncthing-android/issues/1500 ref: https://github.com/wlynxg/anet/blob/main/interface.go & https://github.com/wlynxg/anet/blob/main/interface_android.go With that fix, I can see the broadcast/multicast lines again and my phone can be discovered by other phones running the Syncthing app which wasn't possible before on Android 10+. ``` [ET76H] .346892 broadcast.go:107: DEBUG: sent 185 bytes to 192.168.x.255:21027 [ET76H] .347114 multicast.go:86: DEBUG: sent 185 bytes to [ff12::8384]:21027 on wlan0 ``` --------- Co-authored-by: Marcus B Spencer <marcus@marcusspencer.us>
Goals
Syncthing is a continuous file synchronization program. It synchronizes files between two or more computers. We strive to fulfill the goals below. The goals are listed in order of importance, the most important ones first. This is the summary version of the goal list - for more commentary, see the full Goals document.
Syncthing should be:
-
Safe From Data Loss
Protecting the user's data is paramount. We take every reasonable precaution to avoid corrupting the user's files.
-
Secure Against Attackers
Again, protecting the user's data is paramount. Regardless of our other goals, we must never allow the user's data to be susceptible to eavesdropping or modification by unauthorized parties.
-
Easy to Use
Syncthing should be approachable, understandable, and inclusive.
-
Automatic
User interaction should be required only when absolutely necessary.
-
Universally Available
Syncthing should run on every common computer. We are mindful that the latest technology is not always available to every individual.
-
For Individuals
Syncthing is primarily about empowering the individual user with safe, secure, and easy to use file synchronization.
-
Everything Else
There are many things we care about that don't make it on to the list. It is fine to optimize for these values, as long as they are not in conflict with the stated goals above.
Getting Started
Take a look at the getting started guide.
There are a few examples for keeping Syncthing running in the background on your system in the etc directory. There are also several GUI implementations for Windows, Mac, and Linux.
Docker
To run Syncthing in Docker, see the Docker README.
Getting in Touch
The first and best point of contact is the Forum. If you've found something that is clearly a bug, feel free to report it in the GitHub issue tracker.
If you believe that you’ve found a Syncthing-related security vulnerability, please report it by emailing security@syncthing.net. Do not report it in the Forum or issue tracker.
Building
Building Syncthing from source is easy. After extracting the source bundle from
a release or checking out git, you just need to run go run build.go and the
binaries are created in ./bin. There's a guide with more details on the
build process.
Signed Releases
Release binaries are GPG signed with the key available from https://syncthing.net/security/. There is also a built-in automatic upgrade mechanism (disabled in some distribution channels) which uses a compiled in ECDSA signature. macOS and Windows binaries are also code-signed.
Documentation
Please see the Syncthing documentation site [source].
All code is licensed under the MPLv2 License.