Search the Community
Showing results for tags 'discovery'.
Hi there. I have been a resilio sync user for a while and I have synced a lot of data. I have 4 devices which I keep synced, my phone, work laptop, another laptop and a raspberry pi. The folder on raspberry pi is set to selective sync on each of the devices. Now for some reason, after syncing a 7 or 10 gb file to my pi, sync has stopped detecting my pi altogether. On my pcs, even if on the internet (not lan), it will not show up. But strangely enoiugh, on my phone the pi shows up (not on lan). So I am not sure what caused this. There was no update on either of my devices to cause this issue. It suddenly just stopped working. If you can help me it would be great, thanks.
Hallo, as I haven't found an answer to this question I'll just try it here. My assumption is that the "Sync with..." status of peers is chaining such that peers appear as synced (and online) even though this information is only available through one of the peers. Can somebody confirm that? Let me explain my setup. I am using BitTorrent Sync without tracker and relay server. Those are disabled for every folder on every machine and instead predefined hosts are used to talk to the other peers. I am using two 24/7 linux servers behind a NAT-router without upnp where only one of the servers has the BitTorrent Sync port forwarded through the router firewall. Currently me and my MacBook are in a totally different city. I resolve the mentioned NAT router through DynDns and only added the forwarded port to the predefined host list of the MacBook client. Interestingly I can see 2 relays synced (and online) even though my MacBook should only be able to talk with 1. I'd love to see this chaining feature confirmed. Or is there something I am missing? -- ankoh
Hi, I've been thinking a lot lately about whether it would be possible/useful to remove (or better: to give users an alternative to) the one centralized infrastructure btsync uses: the tracker. Currently, the app registers its shares (and asks for peers) at r.rsyncapp.com and/or t.rsyncapp.com, but what if we introduced an (optional) URL scheme for the secrets? SECRET btsync://SECRET btsync://tracker-server/SECRET The first one for compatibility (and simplicity) and uses the official trackers The second one is basically just like the first one but with a URL schema The third one might use another tracking server (i.e. a local one in a company) While I don't think this will be used a lot, it's a simple extension that might give those who don't want their IPs logged abroad (the tracker might be used to store an IP history for each peer) an extra feeling of privacy.