Why does BT-Sync connect 77.186.116.2 and t.usyncapp.com(54.225.196.38, 54.225.100.8)

[robert-info]

Hey,

Why does BT-Sync connecting servers at the internet even if I turned off the update mechanism?

Connected Servers:

- 77.186.116.2

- t.usyncapp.com(54.225.196.38, 54.225.100.8)

Thanks in advance,

Robert

[Syl]

did you turn off relay server and tracker server aswell?

[BtbN]

Most likely it's just DHT.

[robert-info]

did you turn off relay server and tracker server aswell?

Where can I find this option exactly? May under "Preferences" -> "Advanced..." ?

[robert-info]

Most likely it's just DHT.

Why should the DHT mechanism with an internet-server be used in my own local area network. Wouldn't a UDP-Broadcast more efficient?

[robert-info]

I am a bit sad, that nobody could explain this "feature" :-(.

[goli]

Hey there.

Since you didn't resond with "yes, i turned if off" I would assume you have DHT and/or Tracker Server on. By default, Tracker Server is on and DHT is off.

You ask why your local computers would need such a thing in your private network?

Well, what in your opinion should have told your computers that there are no others than your private ones?

Defaults are: There is another world besides your local network. Btsync isn't directly created as LAN synchronization tool but for a more general purpose. From this perspective it makes much more sense to have the Tracker Server thing on by default, don't you think?

If you don't want that: Turn it off. Nothing easier than that.

It's a per-share configuration. You can (or must) decide per share, if your computer should use Tracker Server and DHT. Just like you can (or must) decide per share if your computer should use "Search on LAN" (broadcasts) or known hosts. So rightclick on your share, Preferences, here you are.

And remember: You don't configure the share in a global perspective, you configure the behavior of your very personal node dealing with this share. So you nee to do it on all of your computers.

If you still discover unknown network traffic: This could be the auto update notification feature. You need to turn this off, too, in order to have no external connections going on. That's a per-device setting, not a per-share setting.

But you're not the first one asking those questions, using search would have helped you, too.

Regards,

Stephan.

[sharkswithlasers]

Not to beat a dead horse but this bothered me.  Despite having the options you mentioned above, turned off, btsync still calls home.  Kind of hard to tell what these are with so little documentation.  Quite disturbing too is despite being flaunted as secure, this is quite far from it (unless I'm missing something).  There is no way that header should be in any kind of heartbeat.

 

 

19:50:42.454545 IP 1.1.1.2.60575 > 1.1.1.1.domain: 32814+ A? r.usyncapp.com. (32)
E..<>!@.@.p............5.(.-.............r.usyncapp.com.....

19:50:42.455412 IP 1.1.1.1.domain > 1.1.1.2.60575: 32814 2/4/3 A 67.215.231.242, A 67.215.229.106 (249)
E.......@.N..........5....h1.............r.usyncapp.com.................C...............C..j.........#...ns-329    awsdns-41...........#...ns-607    awsdns-11.net..........#...ns-1467    awsdns-55.org..........#...ns-1725    awsdns-23.co.uk..k.......O....._.........O...............O......

 

19:50:42.463096 IP 1.1.1.2.sos > 239.192.0.0.sos: UDP, length 89
E..u..@....y.............a.pBSYNC.d1:m4:ping4:peer20

19:50:42.463112 IP 1.1.1.2.55373 > 1.1.1.1.domain: 48569+ A? t.usyncapp.com. (32)
E..<>)@.@.p..........M.5.(.-.............t.usyncapp.com.....

 

// Peer heartbeats

19:50:42.463153 IP 1.1.1.2.44444 > 10.0.1.2.44444: UDP, length 76
E..h..@.@.iF............T..BSYNC.d1:m4:ping4:peer20:..

19:50:42.463187 IP 1.1.1.2.44444 > 1.1.1.1.ddi-udp-1: UDP, length 76
E..h..@.@............."..T.YBSYNC.d1:m4:ping4:peer20:..

 

// Calling home again

19:50:42.463876 IP 1.1.1.1.domain > 1.1.1.2.55373: 48569 3/4/3 A 54.225.92.50, A 54.225.100.8, A 54.225.196.38 (265)
E..%....@.N..........5.M.................t.usyncapp.com..............w..6.\2.........w..6.d..........w..6..&.........#...ns-607    awsdns-11.net..........#...ns-1467    awsdns-55.org..........#...ns-329    awsdns-41...........#...ns-1725    awsdns-23.co.uk..\.......O....._.~.......O...............O......
19:50:42.464025 IP 1.1.1.2.51847 > 1.1.1.1.domain: 35375+ A? t.usyncapp.com. (32)
E..<>*@.@.p............5.(.-./...........t.usyncapp.com.....
19:50:42.464463 IP 1.1.1.2.domain > 1.1.1.1.51847: 35375 3/4/3 A 54.225.196.38, A 54.225.92.50, A 54.225.100.8 (265)
E..%....@.N..........5......./...........t.usyncapp.com..............w..6..&.........w..6.\2.........w..6.d..........#...ns-1467    awsdns-55.org..........#...ns-607    awsdns-11.net..........#...ns-1725    awsdns-23.co.uk..........#...ns-329    awsdns-41...........O....._.\.......O...............O......

 

19:50:42.997548 IP 1.1.1.1.sos > 239.192.0.0.sos: UDP, length 89
E..u..@..................a..BSYNC.d1:m4:ping4:peer20:.
19:50:43.506494 IP 1.1.1.2.sos > 239.192.0.0.sos: UDP, length 89
E..u..@....y.............a.pBSYNC.d1:m4:ping4:peer20:

19:50:43.506556 IP 1.1.1.2 .44444 > 10.0.1.2.44444: UDP, length 76
E..h..@.@.iF............T..BSYNC.d1:m4:ping4:peer20:..

 

19:50:43.506584 IP 1.1.1.2.44444 > 1.1.1.1.ddi-udp-1: UDP, length 76

E..h..@.@............."..T.YBSYNC.d1:m4:ping4:peer20:.

19:50:44.059042 IP 1.1.1.1.sos > 239.192.0.0.sos: UDP, length 89
E..u..@..................a..BSYNC.d1:m4:ping4:peer20:.
19:50:44.059183 IP 1.1.1.2.32367 > 1.1.1.2.44444: UDP, length 76
E..h..@.@...........~o...Tb_BSYNC.d1:m4:ping4:peer20:.
19:50:44.067887 IP 1.1.1.1.sos > 239.192.0.0.sos: UDP, length 89E..u..@....y.............a.pBSYNC.d1:m4:ping4:peer20:..

19:50:44.067949 IP 1.1.1.2.44444 > 10.0.1.2.44444: UDP, length 76
E..h..@.@.iF....
 

 

 

Config::

 

{
  "device_name": "lt_vm1",
    "storage_path" : "/export/fas250/.sync",
    "check_for_updates" : false,
    "download_limit" : 0,                      
    "upload_limit" : 0,
    "webui" :
  {
    "listen" : "127.0.0.1:8888",
    "login" : "admin",
    "password" : "removed"
  }
  ,
  "shared_folders" :
  [
    {

      "use_relay_server" : false,
      "use_tracker" : false,
      "use_dht" : false,
      "search_lan" : true,
      "use_sync_trash" : true,
      "known_hosts" :
      [

        "1.1.1.1:4444"

        "1.1.1.2:44444"
        "10.0.2.15:44444"
      ]
    }
  ]

"lan_encrypt_data": true

}
 

[mgr]

I'm seeing the same thing in my testing - Relay Servers, Trackers, and DHT all turned off, yet this beaconing home is happening constantly (it's a ping-pong of network traffic - haven't tried looking at the content, just saw the packets bouncing back and forth)

[gnur]

Not to beat a dead horse but this bothered me.  Despite having the options you mentioned above, turned off, btsync still calls home.  Kind of hard to tell what these are with so little documentation.  Quite disturbing too is despite being flaunted as secure, this is quite far from it (unless I'm missing something).  There is no way that header should be in any kind of heartbeat.

 

[...]

 

 

In the btsync config file you cannot define webui & folders at the same time. If the webui is working, the settings from the shared folders are probably ignored.

 

 

/* !!! if you set shared folders in config file WebUI will be DISABLED !!!

   shared directories specified in config file

   override the folders previously added from WebUI.

*/