Search the Community

Showing results for tags 'tracker'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Resilio Sync
    • Sync General Discussion
    • Sync Troubleshooting
    • Sync for NAS (Network Attached Storage)
    • Sync Stories
    • Developers
    • Feature Requests

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 9 results

  1. I setup sync between two nodes and despite turning off relay and tracker (on both nodes) and restarting the sync service, all data is sent to 66.63.177.26.static.quadranet.com according to TCPView. Very concerning. Can someone please let me know what is going on?
  2. System A (Synology NAS) w/ btsync 1.3.109. Share 'Repository' has settings relay server, tracker, LAN, not DHT. System B (x64 Linux) w/ btsync 1.4.83. Share 'Repository' has settings relay server, tracker, LAN, not DHT. The shares are connected and synched. Only these two systems are involved. On system B, I change the settings to LAN only. After a while both systems report that there are no peers to connect to. Restarting btsync on system B will re-establish the connection. I guess a restart on system A would have helped as well. I think btsync should re-establish the connection after changing the connection properties.
  3. Hi, Btsync tracker is not working right now ? I am asking because in my logs files tracker is not responding. btsync log : [20140904 10:15:49.500] Requesting peers from tracker 54.225.100.8:3000 for share 93xxxx....[20140904 10:15:49.500] Creating TCP tracker connection to 54.225.100.8:3000[20140904 10:15:49.500] Creating uTP tracker connection to 54.225.100.8:3000[20140904 10:16:10.521] Closing uTP tracker connection to 54.225.100.8:3000. Error 110and logs from proxy : 1409800366.064 0 10.99.x.x TCP_DENIED/407 3886 CONNECT 54.225.100.8:3000 - HIER_NONE/- text/html1409800426.339 60273 10.99.x.x TCP_MISS/503 0 CONNECT 54.225.100.8:3000 kbrpva HIER_NONE/- -
  4. Hello all, I'm testing out BT Sync in a corporate environment for efficiently transfer files across different DC. I found that untick "use_relay_server" and "use_tracker" doesn't work even for our VLAN setup. Is it possible to setup our own tracker and relay server? If yes, how do we do that? We choose BT Sync because we believe it's truly private, but it seems that we still need to connect with upstream tracker and relay server to get this working.
  5. On http://labs.bittorre...technology.html it says What does BTSync send if my full access secret is AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA and I use tracker or DHT? Does it send AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA or a SHA-256 or SHA-512 or another hash of that secret? I've turned of the relay server, because I don't want all my files stored on other peoples server, but if it sends the regular secret without hashing it the trackers can just add that to their BTSync client and get the files from me. What does the URL look like? I know how the trackers work on regular BitTorrent Clients, so I'm curious what BTSync sends where. And what tracker does BTSync use? Can you choose yourself?
  6. Hi All, I was waitting for an opportunity to make use of btSync and now I had it on an empresarial context. I did a test on the company's local network and it was great, but I'm concerned about how btSync deals with peers when they are all over the world. Based on what I read, there's a central public tracker and my question is if it is possible to setup a private tracker (using, for example, the opentracker software) accessible through the internet to "facilitate" the peers discovery and connection? Thanks in advance,
  7. hello everyone, I was wondering if it was possible to build my own tracker ? I have realised that all the trackers are from NA, that could be interesting to build some in Europe so we don't have to cross all the way and Back. Can anybody point me out were I can find info on that ? Thank you.
  8. 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.
  9. I like the software in concept, and am considering using it in an enterprise environment. I am wondering if it is possible to specify my own tracker. TIA, Peter