Syncthing-Fork 1.23 on Samsung Android 13. Configured to sync data from Samsung to local network other device. Used to work up today when I detected remote device is being constantly in Disconnected status on Samsung’s Syncthing-Fork. So I have clear cache and data on Syncthing-Fork and started from scratch. To my surprise Syncthing-Fork is not advertising itself and is not discovered by other device. I tested the same on another Android phone and on this one Syncthing-Fork is discovered by other device which shows that the issue is with Samsung phone.
In the Syncthing log on Samsung Android 13 phone repeating entries:
22:21:54 [MGX26] DEBUG: multicastBeacon: Entering the backoff state. 22:21:54 [MGX26] DEBUG: multicastBeacon: Failed service ‘Service@0x4000442840 created by multicastBeacon@0x40003ccd20/writer’ (3.999969 failures of 2.000000), restarting: false, error: route ip+net: netlinkrib: permission denied 22:22:45 [MGX26] DEBUG: broadcastBeacon: Exiting backoff state. 22:22:45 [MGX26] DEBUG: broadcastBeacon: Failed service ‘Service@0x40004425c0 created by broadcastBeacon@0x40003ccc30/writer’ (1.000000 failures of 2.000000), restarting: true, error: route ip+net: netlinkrib: permission denied 22:22:45 [MGX26] DEBUG: broadcastBeacon: Failed service ‘Service@0x40004425c0 created by broadcastBeacon@0x40003ccc30/writer’ (1.999971 failures of 2.000000), restarting: true, error: route ip+net: netlinkrib: permission denied 22:23:09 [MGX26] DEBUG: broadcastBeacon: Entering the backoff state.
In the Web GUI in “This Device” Discovery 3/5 shows:
I have no idea what happened as it used to work until today. Update from Syncthing-Fork done few days ago from 1.22 to 1.23 and it worked fine.