Remote devices showing disconnected

Support
1

Hi,

I setup syncthing and its working perfectly in local network. But in live environment ,the remote machines are not connected. It shows as disconnected.I use my own relay server.

I am using default as global discovery servers, Do i need to set my own discover server?

2

Have you configured your devices to connect to your relay.

3

Yes. I set up syncthing in two machines. Attached the setting configuration. These settings given in two machines.

Settings-Connections
Settings-Connections.JPG907×456 33.6 KB

1)Some times it took long time to connected the remote machines. 2)While adding remote device,some times the device id of other machine shown under device id text box.Some times it does not show.Would you please tell me what is the reason? 3)Also in address text box, which one is preferred? dynamic or my relay address(relay://myrelay:22067)?

4

The docs explain how addresses work. You have discovery disabled, so I am not surprised connecting does not work.

I am not sure what you are asking in your other questions, perhaps pictures would be better.

1 Like
5

What do you want to achieve? I can’t imagine any scenario where direct TCP connections are not first preference, so you should have both the tcp listen address and your relay in there. See https://docs.syncthing.net/users/config.html#listen-addresses

6

Thanks for your reply. I disabled local and global discovery because of How setup to use ONLY my relay server. I use my own relay server and in this link shows that to set our own relay server disable local and global discovery,Set listen address and remote device address to the relay address. That’s why i disabled local and global discovery.

Settings -Connections

  1. Would you please tell what are the changes that i have to made in the setting configuration if i run my own server?

Add Remote Device

  1. RemoteMachineSettings
    RemoteMachineSettings.jpg1152×648 131 KB
    When adding remote machine,Some times the device id appears under device id box.Some times it will not appear.What is the reason behind that?

  2. In the address field,which one is prefer?dynamic or relay address.

7
  1. If you want to connect only over relay, then you put the relay address only. If you want relay and other protocols, you put relay and other protocols.
  2. It’s devices that were discovered on local network (if local discovery is enabled)
  3. If you have global discovery disabled, dynamic won’t work, and you have to hardcode addresses of other devices (where addresses could be relay address or a tcp address).

What is your end goal?

8

I used relay address there because

in this link shows that,to set up our own server ,“set listen address and remote device address to the relay address”. Thats why i asked whether i need to set "relay://myrelay:22067" in the remote device address field? Would you please tell me what are the conditions that i have to change if i use my own relay server?

9

Re:2 - If i connect over relay and i enable local discovery, can i show all devices connected to same relay ?

10

You haven’t explained if you only want to use the relay explicitly or as an additional channel of communication.

11

My end goal is to connect more devices without taking more delay.

When i test it locally, i could able sync files between devices easily. But i found following difficulties while move to production server.

1-Taking more time to connecting devices. 2-While adding new devices, then all connected devices are goes to ‘disconnected’ mode for a short time and after those goes to ‘up to date’ mode.(one by one), Same difficulty is facing while adding folders too.

Currently i am trying to connect through my own relay server.

What is the good configurations to make quick connection between devices (Connecting over own relay server,Connecting over own discovery server or Connecting over both own or default enough)?

12

That has nothing to do with connections: On certain operations like adding devices/folders connections need to be reestablished.

If what you care about is connection speed, use direct IP addresses in the remote devices field, thus skipping discovery. Own relay or global discovery won’t necessarily speed up connection times. Limiting to relay connections will probably slow down, as these are designed as fallback connections. From the goal you give you should really use static IP addresses where possible and normal discovery everywhere else. You can add your own relay if you want, as explained several times above.

2 Likes
13

Hard coding ip addresses on every side and potentially removing dynamic from addresses it will make it connect faster, as it can avoid discovery, yet it will still potentially be in the minutes, as the timeouts for old connections are long, as are the reconnect intervals.

Also, devices disconnecting and reconnecting when you add folders is expected as this is how the implementation resets the state of what we believe the cluster should look like, so there is not much you can do there.

2 Likes
14

OK, the reconnect is making trouble in my case as i need to use more devices inn production.

Thank you all for prompt replies :slight_smile: .

15

Hi, I changed the settings connections in the following way.

Setting-Connections
Setting-Connections.JPG896×541 33.7 KB

Then i add the remote device by just adding the device id and address as dynamic. But the remote device is disconnected. Remote-Devices

Would you please tell me what is the reason behind this ???

16

You can try running with STTRACE=connections environment variable from both sides and see what the logs say.

17

My device id is:- MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT

The log is gives as follows:-

2018-02-07 14:11:02 syncthing v0.14.43 "Dysprosium Dragonfly" (go1.9.2 linux-amd64) teamcity@build.syncthing.net 2017-12-29 21:23:06 UTC
2018-02-07 14:11:02 My ID: 7PJCGGO-LOMP4MG-PDI5H42-ELNBKJD-7WS3XVO-AOBWRRB-GYBH4NT-MI4O7Q3
2018-02-07 14:11:03 Single thread SHA256 performance is 90 MB/s using minio/sha256-simd (86 MB/s using crypto/sha256).
2018-02-07 14:11:04 Hashing performance with weak hash is 74.35 MB/s
2018-02-07 14:11:05 Hashing performance without weak hash is 84.46 MB/s
2018-02-07 14:11:05 Weak hash enabled, as it has an acceptable performance impact.
2018-02-07 14:11:05 Ready to synchronize "zone-FIRE OFF ZONE-vertical" (zone-FIRE OFF ZONE-vertical) (readonly)
2018-02-07 14:11:05 Ready to synchronize "branch-FIRE OFF BRANCH-horizontal" (branch-FIRE OFF BRANCH-horizontal) (readonly)
2018-02-07 14:11:05 Ready to synchronize "branch-FIRE OFF BRANCH-vertical" (branch-FIRE OFF BRANCH-vertical) (readonly)
2018-02-07 14:11:05 Ready to synchronize "Default Folder" (default) (readwrite)
2018-02-07 14:11:05 ...
2018-02-07 14:51:39 Not dialing relay://83.166.144.57:22067/?id=VINIISH-F6P27R2-3EEQETA-SFGX4XQ-KY4NJZW-FUHJHEW-XHL4KPF-WI7SQQT&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy= as sleep is 5s, next dial is at 2018-02-07 14:51:08.126614518 +0000 UTC m=+2405.480115428 and current time is 2018-02-07 14:50:40.297803009 +0000 UTC m=+2377.651303970
2018-02-07 14:51:39 Not dialing tcp://106.203.90.128:22000 as sleep is 5s, next dial is at 2018-02-07 14:50:45.297803009 +0000 UTC m=+2382.651303970 and current time is 2018-02-07 14:50:40.297803009 +0000 UTC m=+2377.651303970
2018-02-07 14:51:39 Not dialing tcp://[2402:8100:3922:e96e:695b:ef88:cd94:e596]:22000 as sleep is 5s, next dial is at 2018-02-07 14:50:45.297803009 +0000 UTC m=+2382.651303970 and current time is 2018-02-07 14:50:40.297803009 +0000 UTC m=+2377.651303970
2018-02-07 14:51:39 dialing ZAX5EBN-PMQNLZ3-SM4CKLY-EIG5STN-TAQCIH6-MRHN5CE-DIEBPJC-TY6S3A7 tcp://27.97.31.206:22000 prio 10
2018-02-07 14:51:49 dialing ZAX5EBN-PMQNLZ3-SM4CKLY-EIG5STN-TAQCIH6-MRHN5CE-DIEBPJC-TY6S3A7 tcp://27.97.31.206:22000 error: dial tcp 27.97.31.206:22000: i/o timeout
2018-02-07 14:51:49 failed to connect to ZAX5EBN-PMQNLZ3-SM4CKLY-EIG5STN-TAQCIH6-MRHN5CE-DIEBPJC-TY6S3A7 10
2018-02-07 14:51:49 dialing ZAX5EBN-PMQNLZ3-SM4CKLY-EIG5STN-TAQCIH6-MRHN5CE-DIEBPJC-TY6S3A7 kcp://106.203.122.104:12992 prio 50
2018-02-07 14:51:49 dialing ZAX5EBN-PMQNLZ3-SM4CKLY-EIG5STN-TAQCIH6-MRHN5CE-DIEBPJC-TY6S3A7 kcp://106.203.122.104:64558 prio 50
2018-02-07 14:51:49 dial kcp://106.203.122.104:64558 using existing conn on [::]:22020
2018-02-07 14:51:49 dialing ZAX5EBN-PMQNLZ3-SM4CKLY-EIG5STN-TAQCIH6-MRHN5CE-DIEBPJC-TY6S3A7 kcp://27.97.31.206:22020 prio 50
2018-02-07 14:51:49 dial kcp://27.97.31.206:22020 using existing conn on [::]:22020
2018-02-07 14:51:49 dial kcp://106.203.122.104:12992 using existing conn on [::]:22020
2018-02-07 14:51:50 dialing ZAX5EBN-PMQNLZ3-SM4CKLY-EIG5STN-TAQCIH6-MRHN5CE-DIEBPJC-TY6S3A7 kcp://106.203.122.104:12992 success: [::]:22020-106.203.122.104:12992/kcp-client
2018-02-07 14:51:50 connected to ZAX5EBN-PMQNLZ3-SM4CKLY-EIG5STN-TAQCIH6-MRHN5CE-DIEBPJC-TY6S3A7 50 using [::]:22020-106.203.122.104:12992/kcp-client 50
2018-02-07 14:51:50 Reconnect loop for 6Z3EWW2-DW7YVV4-CVSSY2N-KRKH52N-7PGUFMJ-I53MGSA-Y5HS44M-B2ZKUQO [kcp://202.83.55.151:22020 kcp://202.83.55.151:34556 relay://139.59.36.151:22067/?id=4EFLAOT-XAIPCTN-6NXCV43-CURFCXJ-SAJMHX6-XHA5UJU-T7FPOOM-OLPOYAR&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=350000&statusAddr=:22070&providedBy=baseops [at] tutanota.com tcp://202.83.55.151:11017 tcp://202.83.55.151:22000]
2018-02-07 14:51:50 Not dialing kcp://202.83.55.151:22020 as sleep is 5s, next dial is at 2018-02-07 14:51:04.297803009 +0000 UTC m=+2401.651303970 and current time is 2018-02-07 14:50:40.297803009 +0000 UTC m=+2377.651303970
2018-02-07 14:51:50 Not dialing relay://139.59.36.151:22067/?id=4EFLAOT-XAIPCTN-6NXCV43-CURFCXJ-SAJMHX6-XHA5UJU-T7FPOOM-OLPOYAR&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=350000&statusAddr=:22070&providedBy=baseops [at] tutanota.com as sleep is 5s, next dial is at 2018-02-07 14:52:40.297803009 +0000 UTC m=+2497.651303970 and current time is 2018-02-07 14:50:40.297803009 +0000 UTC m=+2377.651303970
2018-02-07 14:51:50 Not dialing tcp://202.83.55.151:22000 as sleep is 5s, next dial is at 2018-02-07 14:50:45.297803009 +0000 UTC m=+2382.651303970 and current time is 2018-02-07 14:50:40.297803009 +0000 UTC m=+2377.651303970
2018-02-07 14:51:50 dialing 6Z3EWW2-DW7YVV4-CVSSY2N-KRKH52N-7PGUFMJ-I53MGSA-Y5HS44M-B2ZKUQO tcp://202.83.55.151:11017 prio 10
2018-02-07 14:51:50 Connected to already connected device 55PC6T5-TZSBBN6-NN7I2OL-N7NEXWN-UJU7UTM-SWQE7MV-57C6MBB-LANWNAW (existing: 198.211.115.107:22000-106.203.122.104:41171/tcp-server new: [::]:22020-106.203.122.104:12992/kcp-client)
2018-02-07 14:51:50 connect from 106.203.90.128:34034
2018-02-07 14:51:59 dialing ZAX5EBN-PMQNLZ3-SM4CKLY-EIG5STN-TAQCIH6-MRHN5CE-DIEBPJC-TY6S3A7 kcp://106.203.122.104:64558 error: i/o timeout
2018-02-07 14:51:59 dialing ZAX5EBN-PMQNLZ3-SM4CKLY-EIG5STN-TAQCIH6-MRHN5CE-DIEBPJC-TY6S3A7 kcp://27.97.31.206:22020 error: i/o timeout
2018-02-07 14:51:59 discarding 0 connections while connecting to ZAX5EBN-PMQNLZ3-SM4CKLY-EIG5STN-TAQCIH6-MRHN5CE-DIEBPJC-TY6S3A7 50
2018-02-07 14:52:00 dialing 6Z3EWW2-DW7YVV4-CVSSY2N-KRKH52N-7PGUFMJ-I53MGSA-Y5HS44M-B2ZKUQO tcp://202.83.55.151:11017 error: dial tcp 202.83.55.151:11017: i/o timeout
2018-02-07 14:52:00 failed to connect to 6Z3EWW2-DW7YVV4-CVSSY2N-KRKH52N-7PGUFMJ-I53MGSA-Y5HS44M-B2ZKUQO 10
2018-02-07 14:52:00 dialing 6Z3EWW2-DW7YVV4-CVSSY2N-KRKH52N-7PGUFMJ-I53MGSA-Y5HS44M-B2ZKUQO kcp://202.83.55.151:34556 prio 50
2018-02-07 14:52:00 dial kcp://202.83.55.151:34556 using existing conn on [::]:22020
2018-02-07 14:52:00 smux accept: i/o timeout
2018-02-07 14:52:10 dialing 6Z3EWW2-DW7YVV4-CVSSY2N-KRKH52N-7PGUFMJ-I53MGSA-Y5HS44M-B2ZKUQO kcp://202.83.55.151:34556 error: i/o timeout
2018-02-07 14:52:10 failed to connect to 6Z3EWW2-DW7YVV4-CVSSY2N-KRKH52N-7PGUFMJ-I53MGSA-Y5HS44M-B2ZKUQO 50
2018-02-07 14:52:10 sleep until next dial 5s
2018-02-07 14:52:15 Reconnect loop
2018-02-07 14:52:15 Reconnect loop for AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS [kcp://106.203.90.128:22020 kcp://106.203.90.128:34034 kcp://27.97.189.215:22020 kcp://27.97.31.136:22020 kcp://[2402:8100:3922:e96e:695b:ef88:cd94:e596]:22020 relay://139.59.36.151:22067/?id=4EFLAOT-XAIPCTN-6NXCV43-CURFCXJ-SAJMHX6-XHA5UJU-T7FPOOM-OLPOYAR&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=350000&statusAddr=:22070&providedBy=baseops [at] tutanota.com relay://139.59.43.68:22067/?id=7D4EHJS-FD7RMQH-ZWVNT7R-XIMY2JD-GQJ2EFQ-3OBMZ52-57RMDK5-SM6BQQH&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=bradfordembedded.com tcp://106.203.90.128:22000 tcp://27.97.31.136:22000 tcp://[2402:8100:3922:e96e:695b:ef88:cd94:e596]:22000]
2018-02-07 14:52:15 Not dialing relay://139.59.36.151:22067/?id=4EFLAOT-XAIPCTN-6NXCV43-CURFCXJ-SAJMHX6-XHA5UJU-T7FPOOM-OLPOYAR&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=350000&statusAddr=:22070&providedBy=baseops [at] tutanota.com as sleep is 5s, next dial is at 2018-02-07 14:52:40.297803009 +0000 UTC m=+2497.651303970 and current time is 2018-02-07 14:52:15.635299478 +0000 UTC m=+2472.988800476
2018-02-07 14:52:15 Not dialing relay://139.59.43.68:22067/?id=7D4EHJS-FD7RMQH-ZWVNT7R-XIMY2JD-GQJ2EFQ-3OBMZ52-57RMDK5-SM6BQQH&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=bradfordembedded.com as sleep is 5s, next dial is at 2018-02-07 14:52:40.297803009 +0000 UTC m=+2497.651303970 and current time is 2018-02-07 14:52:15.635299478 +0000 UTC m=+2472.988800476
2018-02-07 14:52:15 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS tcp://106.203.90.128:22000 prio 10
2018-02-07 14:52:15 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS tcp://27.97.31.136:22000 prio 10
2018-02-07 14:52:15 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS tcp://[2402:8100:3922:e96e:695b:ef88:cd94:e596]:22000 prio 10
2018-02-07 14:52:15 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS tcp://[2402:8100:3922:e96e:695b:ef88:cd94:e596]:22000 error: dial tcp [2402:8100:3922:e96e:695b:ef88:cd94:e596]:22000: connect: network is unreachable
2018-02-07 14:52:25 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS tcp://106.203.90.128:22000 error: dial tcp 106.203.90.128:22000: i/o timeout
2018-02-07 14:52:25 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS tcp://27.97.31.136:22000 error: dial tcp 27.97.31.136:22000: i/o timeout
2018-02-07 14:52:25 failed to connect to AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS 10
2018-02-07 14:52:25 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS kcp://106.203.90.128:22020 prio 50
2018-02-07 14:52:25 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS kcp://106.203.90.128:34034 prio 50
2018-02-07 14:52:25 dial kcp://106.203.90.128:34034 using existing conn on [::]:22020
2018-02-07 14:52:25 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS kcp://27.97.189.215:22020 prio 50
2018-02-07 14:52:25 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS kcp://27.97.31.136:22020 prio 50
2018-02-07 14:52:25 dial kcp://27.97.31.136:22020 using existing conn on [::]:22020
2018-02-07 14:52:25 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS kcp://[2402:8100:3922:e96e:695b:ef88:cd94:e596]:22020 prio 50
2018-02-07 14:52:25 dial kcp://[2402:8100:3922:e96e:695b:ef88:cd94:e596]:22020 using existing conn on [::]:22020
2018-02-07 14:52:25 dial kcp://27.97.189.215:22020 using existing conn on [::]:22020
2018-02-07 14:52:25 dial kcp://106.203.90.128:22020 using existing conn on [::]:22020
2018-02-07 14:52:38 dial kcp://202.83.55.151:22020 using existing conn on [::]:22020
2018-02-07 14:52:38 dial kcp://[2405:204:d10b:affc:c08b:fb6f:e73a:89d4]:22020 using existing conn on [::]:22020
2018-02-07 14:52:38 dial kcp://137.97.189.99:22020 using existing conn on [::]:22020
2018-02-07 14:52:39 dialing IHXQJ7B-3M2TKHD-AZIPSKZ-K4CKZ43-6OPSGLR-JIKVKJF-USXHRIV-OHDVZA3 kcp://202.83.55.151:22020 success: [::]:22020-202.83.55.151:22020/kcp-client
2018-02-07 14:52:39 connected to IHXQJ7B-3M2TKHD-AZIPSKZ-K4CKZ43-6OPSGLR-JIKVKJF-USXHRIV-OHDVZA3 50 using [::]:22020-202.83.55.151:22020/kcp-client 50
2018-02-07 14:52:39 Connected to already connected device 6WOKNBC-PZLTG42-NHUHQ4T-FQMMO6P-KSZUCXX-HMOPGMK-MOGLNZ3-WJIM3AY (existing: 198.211.115.107:22000-202.83.55.151:51439/tcp-server new: [::]:22020-202.83.55.151:22020/kcp-client)
2018-02-07 14:52:41 Reconnect loop for MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT [kcp://202.83.55.151:22020 tcp://202.83.55.151:22000 tcp://202.83.55.151:53282]
2018-02-07 14:52:41 Not dialing kcp://202.83.55.151:22020 as sleep is 5s, next dial is at 2018-02-07 14:52:39.635299478 +0000 UTC m=+2496.988800476 and current time is 2018-02-07 14:52:15.635299478 +0000 UTC m=+2472.988800476
2018-02-07 14:52:41 Not dialing tcp://202.83.55.151:22000 as sleep is 5s, next dial is at 2018-02-07 14:52:20.635299478 +0000 UTC m=+2477.988800476 and current time is 2018-02-07 14:52:15.635299478 +0000 UTC m=+2472.988800476
2018-02-07 14:52:41 dialing MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT tcp://202.83.55.151:53282 prio 10
2018-02-07 14:52:48 dialing IHXQJ7B-3M2TKHD-AZIPSKZ-K4CKZ43-6OPSGLR-JIKVKJF-USXHRIV-OHDVZA3 kcp://[2405:204:d10b:affc:c08b:fb6f:e73a:89d4]:22020 error: i/o timeout
2018-02-07 14:52:48 dialing IHXQJ7B-3M2TKHD-AZIPSKZ-K4CKZ43-6OPSGLR-JIKVKJF-USXHRIV-OHDVZA3 kcp://137.97.189.99:22020 error: i/o timeout
2018-02-07 14:52:48 discarding 0 connections while connecting to IHXQJ7B-3M2TKHD-AZIPSKZ-K4CKZ43-6OPSGLR-JIKVKJF-USXHRIV-OHDVZA3 50
2018-02-07 14:52:51 dialing MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT tcp://202.83.55.151:53282 error: dial tcp 202.83.55.151:53282: i/o timeout
2018-02-07 14:52:51 failed to connect to MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT 10
2018-02-07 14:52:51 Reconnect loop for RSNLABS-KMBNTNQ-BQM3LQ4-QZJWW5H-SH4JXWU-3I3PKKX-67JWGCU-PSUPKQD [kcp://137.97.189.99:22020 kcp://[2405:204:d10b:affc:c08b:fb6f:e73a:89d4]:22020 relay://118.189.177.157:22067/?id=MM4OYPA-IMKEFOC-K5BPWA6-PD6MU32-NT56J43-AJMPP7I-DYVEBMS-3NTGUQ2&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=4096R/5819E33F Zhongfu Li <syncthingrelay AT zhongfu DOT li> relay://139.59.43.68:22067/?id=7D4EHJS-FD7RMQH-ZWVNT7R-XIMY2JD-GQJ2EFQ-3OBMZ52-57RMDK5-SM6BQQH&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=bradfordembedded.com tcp://137.97.189.99:22000 tcp://[2405:204:d10b:affc:c08b:fb6f:e73a:89d4]:22000]
2018-02-07 14:53:23 Not dialing kcp://202.83.55.151:22020 as sleep is 5s, next dial is at 2018-02-07 14:52:39.635299478 +0000 UTC m=+2496.988800476 and current time is 2018-02-07 14:52:15.635299478 +0000 UTC m=+2472.988800476
2018-02-07 14:53:23 Not dialing relay://139.59.36.151:22067/?id=4EFLAOT-XAIPCTN-6NXCV43-CURFCXJ-SAJMHX6-XHA5UJU-T7FPOOM-OLPOYAR&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=350000&statusAddr=:22070&providedBy=baseops [at] tutanota.com as sleep is 5s, next dial is at 2018-02-07 14:52:40.297803009 +0000 UTC m=+2497.651303970 and current time is 2018-02-07 14:52:15.635299478 +0000 UTC m=+2472.988800476
2018-02-07 14:53:23 Not dialing tcp://202.83.55.151:22000 as sleep is 5s, next dial is at 2018-02-07 14:52:20.635299478 +0000 UTC m=+2477.988800476 and current time is 2018-02-07 14:52:15.635299478 +0000 UTC m=+2472.988800476
2018-02-07 14:53:58 dial kcp://[2402:8100:3922:e96e:695b:ef88:cd94:e596]:22020 using existing conn on [::]:22020
2018-02-07 14:53:58 dial kcp://27.97.189.215:22020 using existing conn on [::]:22020
2018-02-07 14:53:58 dial kcp://106.203.90.128:22020 using existing conn on [::]:22020
2018-02-07 14:53:59 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS kcp://106.203.90.128:34034 success: [::]:22020-106.203.90.128:34034/kcp-client
2018-02-07 14:53:59 connected to AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS 50 using [::]:22020-106.203.90.128:34034/kcp-client 50
2018-02-07 14:53:59 Connected to already connected device 55PC6T5-TZSBBN6-NN7I2OL-N7NEXWN-UJU7UTM-SWQE7MV-57C6MBB-LANWNAW (existing: 198.211.115.107:22000-106.203.122.104:47335/tcp-server new: [::]:22020-106.203.90.128:34034/kcp-client)
2018-02-07 14:53:59 Reconnect loop for MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT [kcp://202.83.55.151:22020 tcp://202.83.55.151:22000 tcp://202.83.55.151:53282]
2018-02-07 14:53:59 dialing MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT tcp://202.83.55.151:22000 prio 10
2018-02-07 14:53:59 dialing MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT tcp://202.83.55.151:53282 prio 10
2018-02-07 14:54:08 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS kcp://106.203.90.128:22020 error: i/o timeout
2018-02-07 14:54:08 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS kcp://27.97.31.136:22020 error: i/o timeout
2018-02-07 14:54:08 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS kcp://[2402:8100:3922:e96e:695b:ef88:cd94:e596]:22020 error: i/o timeout
2018-02-07 14:54:08 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS kcp://27.97.189.215:22020 error: i/o timeout
2018-02-07 14:54:08 discarding 0 connections while connecting to AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS 50
2018-02-07 14:54:09 dialing MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT tcp://202.83.55.151:22000 error: dial tcp 202.83.55.151:22000: i/o timeout
2018-02-07 14:54:09 dialing MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT tcp://202.83.55.151:53282 error: dial tcp 202.83.55.151:53282: i/o timeout
2018-02-07 14:54:09 failed to connect to MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT 10
2018-02-07 14:54:09 dialing MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT kcp://202.83.55.151:22020 prio 50
2018-02-07 14:54:09 dial kcp://202.83.55.151:22020 using existing conn on [::]:22020
2018-02-07 14:54:10 dialing MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT kcp://202.83.55.151:22020 success: [::]:22020-202.83.55.151:22020/kcp-client
2018-02-07 14:54:10 connected to MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT 50 using [::]:22020-202.83.55.151:22020/kcp-client 50
2018-02-07 14:54:10 discarding 0 connections while connecting to MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT 50
2018-02-07 14:54:10 Connected to already connected device 6WOKNBC-PZLTG42-NHUHQ4T-FQMMO6P-KSZUCXX-HMOPGMK-MOGLNZ3-WJIM3AY (existing: 198.211.115.107:22000-202.83.55.151:51442/tcp-server new: [::]:22020-202.83.55.151:22020/kcp-client)
2018-02-07 14:54:57 dial kcp://[2402:8100:3922:e96e:695b:ef88:cd94:e596]:22020 using existing conn on [::]:22020
2018-02-07 14:54:57 dial kcp://27.97.189.215:22020 using existing conn on [::]:22020
2018-02-07 14:54:57 dial kcp://106.203.90.128:22020 using existing conn on [::]:22020
2018-02-07 14:54:58 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS kcp://106.203.90.128:34034 success: [::]:22020-106.203.90.128:34034/kcp-client
2018-02-07 14:54:58 connected to AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS 50 using [::]:22020-106.203.90.128:34034/kcp-client 50
2018-02-07 14:54:58 Reconnect loop for MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT [kcp://202.83.55.151:22020 tcp://202.83.55.151:22000 tcp://202.83.55.151:53282]
2018-02-07 14:54:58 dialing MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT tcp://202.83.55.151:22000 prio 10
2018-02-07 14:54:58 dialing MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT tcp://202.83.55.151:53282 prio 10
2018-02-07 14:54:58 Connected to already connected device 55PC6T5-TZSBBN6-NN7I2OL-N7NEXWN-UJU7UTM-SWQE7MV-57C6MBB-LANWNAW (existing: 198.211.115.107:22000-106.203.122.104:47335/tcp-server new: [::]:22020-106.203.90.128:34034/kcp-client)
2018-02-07 14:55:07 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS kcp://27.97.31.136:22020 error: i/o timeout
2018-02-07 14:55:07 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS kcp://[2402:8100:3922:e96e:695b:ef88:cd94:e596]:22020 error: i/o timeout
2018-02-07 14:55:07 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS kcp://27.97.189.215:22020 error: i/o timeout
2018-02-07 14:55:07 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS kcp://106.203.90.128:22020 error: i/o timeout
2018-02-07 14:55:07 discarding 0 connections while connecting to AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS 50
2018-02-07 14:55:08 dialing MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT tcp://202.83.55.151:22000 error: dial tcp 202.83.55.151:22000: i/o timeout
2018-02-07 14:55:08 dialing MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT tcp://202.83.55.151:53282 error: dial tcp 202.83.55.151:53282: i/o timeout
2018-02-07 14:55:08 failed to connect to MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT 10
2018-02-07 14:55:08 dialing MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT kcp://202.83.55.151:22020 prio 50
2018-02-07 14:55:08 dial kcp://202.83.55.151:22020 using existing conn on [::]:22020
2018-02-07 14:55:09 dialing MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT kcp://202.83.55.151:22020 success: [::]:22020-202.83.55.151:22020/kcp-client
2018-02-07 14:55:09 connected to MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT 50 using [::]:22020-202.83.55.151:22020/kcp-client 50
2018-02-07 14:55:09 Reconnect loop for RSNLABS-KMBNTNQ-BQM3LQ4-QZJWW5H-SH4JXWU-3I3PKKX-67JWGCU-PSUPKQD [kcp://137.97.189.99:22020 kcp://[2405:204:d10b:affc:c08b:fb6f:e73a:89d4]:22020 relay://118.189.177.157:22067/?id=MM4OYPA-IMKEFOC-K5BPWA6-PD6MU32-NT56J43-AJMPP7I-DYVEBMS-3NTGUQ2&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=4096R/5819E33F Zhongfu Li <syncthingrelay AT zhongfu DOT li> relay://139.59.43.68:22067/?id=7D4EHJS-FD7RMQH-ZWVNT7R-XIMY2JD-GQJ2EFQ-3OBMZ52-57RMDK5-SM6BQQH&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=bradfordembedded.com tcp://137.97.189.99:22000 tcp://[2405:204:d10b:affc:c08b:fb6f:e73a:89d4]:22000]
2018-02-07 14:55:09 Not dialing relay://118.189.177.157:22067/?id=MM4OYPA-IMKEFOC-K5BPWA6-PD6MU32-NT56J43-AJMPP7I-DYVEBMS-3NTGUQ2&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=4096R/5819E33F Zhongfu Li <syncthingrelay AT zhongfu DOT li> as sleep is 5s, next dial is at 2018-02-07 14:55:48.519972947 +0000 UTC m=+2685.873473861 and current time is 2018-02-07 14:54:47.092377837 +0000 UTC m=+2624.445878744
2018-02-07 14:55:09 Not dialing relay://139.59.43.68:22067/?id=7D4EHJS-FD7RMQH-ZWVNT7R-XIMY2JD-GQJ2EFQ-3OBMZ52-57RMDK5-SM6BQQH&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=bradfordembedded.com as sleep is 5s, next dial is at 2018-02-07 14:55:48.519972947 +0000 UTC m=+2685.873473861 and current time is 2018-02-07 14:54:47.092377837 +0000 UTC m=+2624.445878744
2018-02-07 14:55:09 discarding 0 connections while connecting to MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT 50
2018-02-07 14:55:09 dialing RSNLABS-KMBNTNQ-BQM3LQ4-QZJWW5H-SH4JXWU-3I3PKKX-67JWGCU-PSUPKQD tcp://137.97.189.99:22000 prio 10
2018-02-07 14:55:09 dialing RSNLABS-KMBNTNQ-BQM3LQ4-QZJWW5H-SH4JXWU-3I3PKKX-67JWGCU-PSUPKQD tcp://[2405:204:d10b:affc:c08b:fb6f:e73a:89d4]:22000 prio 10
2018-02-07 14:55:54 dial kcp://[2402:8100:3922:e96e:695b:ef88:cd94:e596]:22020 using existing conn on [::]:22020
2018-02-07 14:55:54 dial kcp://27.97.189.215:22020 using existing conn on [::]:22020
2018-02-07 14:55:54 dial kcp://106.203.90.128:22020 using existing conn on [::]:22020
2018-02-07 14:55:56 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS kcp://106.203.90.128:34034 success: [::]:22020-106.203.90.128:34034/kcp-client
2018-02-07 14:55:56 connected to AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS 50 using [::]:22020-106.203.90.128:34034/kcp-client 50
2018-02-07 14:55:56 Connected to already connected device 55PC6T5-TZSBBN6-NN7I2OL-N7NEXWN-UJU7UTM-SWQE7MV-57C6MBB-LANWNAW (existing: 198.211.115.107:22000-106.203.122.104:47335/tcp-server new: [::]:22020-106.203.90.128:34034/kcp-client)
2018-02-07 14:55:56 Reconnect loop for MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT [kcp://202.83.55.151:22020 tcp://202.83.55.151:22000 tcp://202.83.55.151:53282]
2018-02-07 14:55:56 dialing MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT tcp://202.83.55.151:22000 prio 10
2018-02-07 14:55:56 dialing MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT tcp://202.83.55.151:53282 prio 10
2018-02-07 14:56:04 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS kcp://27.97.31.136:22020 error: i/o timeout
2018-02-07 14:56:04 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS kcp://[2402:8100:3922:e96e:695b:ef88:cd94:e596]:22020 error: i/o timeout
2018-02-07 14:56:04 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS kcp://27.97.189.215:22020 error: i/o timeout
2018-02-07 14:56:04 dialing AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS kcp://106.203.90.128:22020 error: i/o timeout
2018-02-07 14:56:04 discarding 0 connections while connecting to AO7DFW6-6NT3DVI-RCIUREL-R4UL2JF-RCC4QSA-NJX4LSF-E27ZP64-LIQ57AS 50
2018-02-07 14:56:06 dialing MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT tcp://202.83.55.151:22000 error: dial tcp 202.83.55.151:22000: i/o timeout
2018-02-07 14:56:06 dialing MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT tcp://202.83.55.151:53282 error: dial tcp 202.83.55.151:53282: i/o timeout
2018-02-07 14:56:06 failed to connect to MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT 10
2018-02-07 14:56:06 dialing MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT kcp://202.83.55.151:22020 prio 50
2018-02-07 14:56:06 dial kcp://202.83.55.151:22020 using existing conn on [::]:22020
2018-02-07 14:56:07 dialing MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT kcp://202.83.55.151:22020 success: [::]:22020-202.83.55.151:22020/kcp-client
2018-02-07 14:56:07 connected to MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT 50 using [::]:22020-202.83.55.151:22020/kcp-client 50
2018-02-07 14:56:07 discarding 0 connections while connecting to MYON7JQ-EN4WVLA-NMH6U2V-4Z5QCAY-TTAKNZM-T7EEWN2-XVUZECH-36ZW3AT 50
2018-02-07 14:56:07 Connected to already connected device 6WOKNBC-PZLTG42-NHUHQ4T-FQMMO6P-KSZUCXX-HMOPGMK-MOGLNZ3-WJIM3AY (existing: 198.211.115.107:22000-202.83.55.151:51442/tcp-server new: [::]:22020-202.83.55.151:22020/kcp-client)
2018-02-07 14:56:07 Reconnect loop for RSNLABS-KMBNTNQ-BQM3LQ4-QZJWW5H-SH4JXWU-3I3PKKX-67JWGCU-PSUPKQD [kcp://137.97.189.99:22020 kcp://
2018-02-07 14:56:27 dialing SNOXI4O-QKG4MFY-FG5F3TW-3V5E6J7-FFYLLT3-ED7GQK3-5QTCHWY-BHMJ5A2 tcp://202.83.55.151:62330 prio 10
18

Yeah, this is caused by kcp, it thinks it’s connected, but it seems it isn’t when it comes to the handshake. We plan to remove that in a future version.

19

Not connected doesn’t mean not working. In a cluster, the connected devices are the device that are really acting together at present time (So the same for upload and download speed). When you upload something, it’s synced with other connected devices, but then the connection drops giving a turn to the other devices to exchange the torrent between them, then they are connected together, but they appear to be disconnected from the first as there is nothing more for him to distribute. That’s what I’ve seen while using syncthing with a few lan and wan devices.

20

No, that’s not correct. (Dis-)Connected means just exactly that - whether or not there is anything to transfer and presence of other devices has nothing to do with it.