security while expanding flexibility

hi all, after ~1yr of trying various settings, syncthing finally works for me with very good response\reliability.

that being said, i have been unable to find a good guide\video that offers the minimal\simplest config for better security and reliability (and describing tradeoffs as they occur).

my current setup is use on a home network only between linux boxes that use spam+ad+malware blocking host files, updated every few months from antiX. this standard host file utilizes 127.0.0.1 assigned to both localnet and the unique hostname on which it resides, with 0.0.0.0 assigned to all specifically named unwelcome sites.

for reliability i use fixed IP+port settings for quic and tcp in syncthing, despite my router set to dynamic. somehow i ended up with different port setting for each machine (1 shared folder/machine), but i have now set most advanced option values back to ‘default’, where it is clear ‘default’ is a valid entry. introducer is set to just 1 desktop machine, and syncthing relays are ‘off’. LAN announce, global announce, local announce, and NAT are all set to ‘on’, but unsure which are really needed.

i basically see a few areas for advice on improving :

  • a. since someday the router may not renew existing IPs with the same address, i would like to replace the fixed syncthing IPs for tcp and quic. having tried ‘dynamic’ within syncthing in the past, i found sync would often not work within ~10 min of machines going into power suspend mode. my currrent use of fixed IP+port usually works as soon as the machine network activates.

  • b. i do not used the ‘always use local net’ option for added security. opinions and usage?

  • c. much further away, i would like to sync to cloud when traveling and then return to sync local when home. has anyone found a easy and secure process for this?

It’s the age old conundrum – easy, secure, cheap – pick any two. :wink:

If by “cloud” you mean syncing to online storage, then the most straightforward solution is renting a server at a hosting provider where you can run a Syncthing instance.

Security is very user-specific, so what’s good enough to one person might be unacceptable to another. So, without details regarding familiarity with computer security and networking, OSes being used, etc. there’s not enough context to recommend anything other than to search this forum for ideas based on what others have been doing.

1 Like

Thanks for the insight, gadget. I’ve been thinking along the same lines, seems like hosting a personal Syncthing instance on a rented server could balance access and security. Curious if anyone has tips on switching between local LAN sync and remote server sync smoothly without breaking the setup.

Leave them both up all the time? Your Device will figure out which ones it can reach and which ones it cannot.

Based on your use case, you might consider having the cloud Syncthing Device run as Untrusted (Untrusted (Encrypted) Devices — Syncthing documentation) so that your data there is encrypted.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.