<html><head></head><body>As far as I know, those are "discovery" servers which allow you to connect your instances when they are on different networks. Their usage should be configurable.<br>
<br>
D.<br><br><div class="gmail_quote">On December 27, 2017 4:50:11 AM GMT+01:00, "A. F. Cano" <afc@shibaya.lonestar.org> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Hi,<br /><br />I have installed syncthing but have not configured it yet.  While<br />troubleshooting other stuff I found these troubling messages in<br />/var/log/messages:<br /><br />Dec 26 04:41:07 fbx syncthing[524]: [V7KVP] INFO: Disconnected from relay relay://<a href="45.79.172.54:22067">45.79.172.54:22067</a><br />Dec 26 04:41:12 fbx syncthing[524]: [V7KVP] INFO: Joined relay relay://<a href="192.99.175.39:22067">192.99.175.39:22067</a><br /><br />and after I disconnected from the internet:<br /><br />Dec 26 05:04:41 fbx NetworkManager[418]: <info>  [1514282681.8647] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')<br />Dec 26 05:04:41 fbx NetworkManager[418]: <info>  [1514282681.8714] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external')<br />Dec 26 05:05:20 fbx syncthing[524]: [V7KVP] INFO: Disconnected from relay relay://<a href="192.99.175.39:22067">192.99.175.39:22067</a><br />Dec 26 05:05:27 fbx syncthing[524]: [V7KVP] INFO: Could not connect to relay relay://<a href="74.111.40.65:443/?id=REBDAOM-CDHW4UA-B63Y477-CTTZYQE-VOSIPPB-SNR63DS-R244DS6-P37KAQN&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=harry.lu">74.111.40.65:443/?id=REBDAOM-CDHW4UA-B63Y477-CTTZYQE-VOSIPPB-SNR63DS-R244DS6-P37KAQN&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=harry.lu</a> - New York, US: EOF<br />Dec 26 05:05:34 fbx syncthing[524]: [V7KVP] INFO: Could not connect to relay relay://<a href="192.99.71.152:443/?id=OOCD4WB-BWU2SBD-YD62YUZ-E5DP7PN-YGEHKBT-TJDO3ND-VQG3NUF-72JRKQS&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=10000000&statusAddr=:22070&providedBy=https://keybase.io/gibstick">192.99.71.152:443/?id=OOCD4WB-BWU2SBD-YD62YUZ-E5DP7PN-YGEHKBT-TJDO3ND-VQG3NUF-72JRKQS&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=10000000&statusAddr=:22070&providedBy=https://keybase.io/gibstick</a>: EOF<br />Dec 26 05:05:42 fbx syncthing[524]: [V7KVP] INFO: Could not connect to relay relay://<a href="104.193.225.93:443/?id=UV3SIHA-N6U7DL2-XOQ7OSX-TMUO2Y5-V7CMJSA-3EM4YVP-5KMMB2W-B4OVDAK&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=harry.lu">104.193.225.93:443/?id=UV3SIHA-N6U7DL2-XOQ7OSX-TMUO2Y5-V7CMJSA-3EM4YVP-5KMMB2W-B4OVDAK&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=harry.lu</a> - Texas, US: EOF<br />Dec 26 05:05:49 fbx syncthing[524]: [V7KVP] INFO: Could not connect to relay relay://<a href="107.170.56.60:443/?id=4DPTHBY-G6Y5CDI-2HH2ZUI-674CQUG-IYTPVZ7-CRRJMPH-7A5ELMO-4WM5SQS&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=400000&statusAddr=:22070&providedBy=congruity">107.170.56.60:443/?id=4DPTHBY-G6Y5CDI-2HH2ZUI-674CQUG-IYTPVZ7-CRRJMPH-7A5ELMO-4WM5SQS&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=400000&statusAddr=:22070&providedBy=congruity</a>: EOF<br />Dec 26 05:06:01 fbx syncthing[524]: [V7KVP] INFO: Could not connect to relay relay://<a href="107.150.6.122:8080/?id=YZEDTET-MSMJW5I-FHP65VK-KTARQPH-OWBWODN-6IRBXNR-JGMDUJL-GBQXRAA&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=1024000&statusAddr=:22070&providedBy=assortedflotsam.com">107.150.6.122:8080/?id=YZEDTET-MSMJW5I-FHP65VK-KTARQPH-OWBWODN-6IRBXNR-JGMDUJL-GBQXRAA&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=1024000&statusAddr=:22070&providedBy=assortedflotsam.com</a>: EOF<br />Dec 26 05:06:12 fbx syncthing[524]: [V7KVP] INFO: Could not connect to relay relay://<a href="159.203.30.69:443/?id=BHRVSCI-OS7CQUT-GD52ST6-ADHJ3BZ-OKLJ6O7-2VXKV73-YC477KC-BGWSRAK&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=Colin">159.203.30.69:443/?id=BHRVSCI-OS7CQUT-GD52ST6-ADHJ3BZ-OKLJ6O7-2VXKV73-YC477KC-BGWSRAK&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=Colin</a> Taylor: EOF<br />Dec 26 05:06:32 fbx syncthing[524]: [V7KVP] INFO: Could not connect to relay relay://<a href="89.163.130.244:22067/?id=E76TLVX-UNGBGPN-OL4P3EC-XN24JUK-UWSPZBI-I5DVXRE-XWHKM3M-ESN3IAT&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=marcohald">89.163.130.244:22067/?id=E76TLVX-UNGBGPN-OL4P3EC-XN24JUK-UWSPZBI-I5DVXRE-XWHKM3M-ESN3IAT&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=marcohald</a>: read tcp <a href="75.213.225.50:41058">75.213.225.50:41058</a>-><a href="89.163.130.244:22067">89.163.130.244:22067</a>: i/o timeout<br />Dec 26 05:06:52 fbx syncthing[524]: [V7KVP] INFO: Could not connect to relay relay://<a href="165.227.61.6:22067/?id=LXHDHBN-S7TAF6Q-K5NXQQO-MGHAHH7-LMV4ZAA-5WVQ4S7-WTKI2EQ-55TUMQ4&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy">165.227.61.6:22067/?id=LXHDHBN-S7TAF6Q-K5NXQQO-MGHAHH7-LMV4ZAA-5WVQ4S7-WTKI2EQ-55TUMQ4&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy</a>=: read tcp <a href="75.213.225.50:34226">75.213.225.50:34226</a>-><a href="165.227.61.6:22067">165.227.61.6:22067</a>: i/o timeout<br /><br />Nothing I've read about syncthing indicated that it would be connecting<br />to these "relays" out there.  Why is it doing this? Like I said I<br />haven't even configured it yet.  Until I figure out why it's doing this<br />it will remain disabled.  The prospect that my files I'm trying to sync<br />might end up at those "relays" is not too appealing.  Can someone shed<br />some light on this?<br /><br />FreedomBox testing, just updated.  Thanks a bunch for the switch to turn<br />off snapshot generation and the "delete all" button.  Even with a 32G<br />ssd, it got filled up.  The huge log files (1.2-1.4G) that are generated<br />also don't help.  I realize this is not an issue about freedombox or<br />plinth, it's caused by thousands of "named: network unreachable" error<br />messages when the outside interface is down, which is the case for hours<br />at a time in my setup.<br /><br />Thanks.<br /><br />Augustine<br /><br /><br /><hr /><br />Freedombox-discuss mailing list<br />Freedombox-discuss@lists.alioth.debian.org<br /><a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss</a><br /></pre></blockquote></div></body></html>