I am using syncthing for much over two years by now on a lot of devices connected via LAN & Wifi.
TASK:
Connecting a (new) PXL9a to a local syncthing server hosted on a synology via dockers.
SETTINGS:
Synchting-Fork 1.30.0.2. on Android: installed via F-Droid on Stock PXL9a Android 16
Synchting server: v1.30.0, Linux (64-bit Intel/AMD Offizial Container) on DSM 7.2.2 (LAN connected)
STATUS:
I am able to connect with any devices syncthing to the ST-sever
I am able to connect from an to the Android phone with my debian/ubunut clients and the other Android phones and tablet (all on ST v1.30!) BUT NOT from to the Server.
Discovering ST-server with the PXL9a → Not visible
Discovering the PXL9a from TS-server → Not visible
Manual connecting to the server using the QR to PXL9a → Setup OK, server not visible
Manual setup of PXL9a on ST-Server → Setup OK, server not visible
However, connecting PXL9a via browser to ST-server GUI through network works fine!
PROBLEM:
Connecting between these two ST-clients seems to be impossible.
There is no internal firewall active inside the local Wifi/LAN. For testing, forced the PXL9a to only connect via Wifi (not other network). No improvement.
I restated my entire network infrastructure including phones, router and synology disk station. Not changed any!
The problem seems the PXL9a but no idea what to do.
After some digging I am now able to build and run the syncthing container in host mode. More importantly, this solved the connection issue right away and 10 sec after server restart I had the PXL9a request for connecting.
The specific synology help on network mode here:
was for me essentially useless since it indicates that it could be changed in → “Container Manger” → “Network”.
At least I was not able to do so. But at least it was confirming that the “host driver” was set-up and available.
Precises help was found here:
and within → stackoverflow → how-to-make-network-mode-host-work-in-docker-compose-yml-file
And it is as simple as adding:
network_mode: host
into the compose.yaml and then rebuild the container.
After that the Network Tab shows indeed that now one container is running in host mode.
Thanks for your very fast AND spot-on help! You saved my weekend!
Hope this can help other too