assiging ip address out of my network

Support
1

Hi I see part of the answer talking about relays getting but my 3 boxes are on the same network and I don’t think I need a relay.

I have 1 windows and 2 Rockstor/Suse boxes. When I create link between the windos box and one rockstor it uses the IP4 address. When I try to attach the rockstor boxes it gets a relay address.

There is no need for anything to go outside of my network.

How do I prevent this?

TIA Steve

2

Sounds like a networking problem. I will assign arbitrary names to the boxes of Alice, Bob, and Charlie.

Can Alice ping Bob and Charlie?

Can Bob ping Alice and Charlie?

Can Charlie ping Alice and Bob?

Are they all on the same IP network? With the same subnet mask? Please share the IP addresses and subnet mask information.

3

Thx for the reply

from vault1 myip https://192.168.254.90 https://172.17.0.1

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether c8:fe:0f:d0:3b:62 brd ff:ff:ff:ff:ff:ff altname enp2s0 inet 192.168.254.90/24 brd 192.168.254.255 scope global dynamic noprefixroute eth1 valid_lft 8632sec preferred_lft 8632sec

PING 192.168.254.91 (192.168.254.91) 56(84) bytes of data. 64 bytes from 192.168.254.91: icmp_seq=1 ttl=64 time=0.265 ms 64 bytes from 192.168.254.91: icmp_seq=2 ttl=64 time=0.258 ms 64 bytes from 192.168.254.91: icmp_seq=3 ttl=64 time=0.254 ms 64 bytes from 192.168.254.91: icmp_seq=4 ttl=64 time=0.262 ms 64 bytes from 192.168.254.91: icmp_seq=5 ttl=64 time=0.257 ms 64 bytes from 192.168.254.91: icmp_seq=6 ttl=64 time=0.251 ms 64 bytes from 192.168.254.91: icmp_seq=7 ttl=64 time=0.248 ms ^Z [1]+ Stopped ping 192.168.254.91

Vault:~ # ping 192.168.254.151 PING 192.168.254.151 (192.168.254.151) 56(84) bytes of data. 64 bytes from 192.168.254.151: icmp_seq=1 ttl=128 time=2.23 ms 64 bytes from 192.168.254.151: icmp_seq=2 ttl=128 time=0.582 ms 64 bytes from 192.168.254.151: icmp_seq=3 ttl=128 time=0.424 ms

From vault2 Vault2:~ # ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether c8:fe:0f:d0:46:ba brd ff:ff:ff:ff:ff:ff altname enp4s0 inet 192.168.254.91/24 brd 192.168.254.255 scope global dynamic noprefixroute eth2 valid_lft 14028sec preferred_lft 14028sec

Vault2:~ # myip https://192.168.254.91 https://172.17.0.1

Vault2:~ # ping 192.168.254.90 PING 192.168.254.90 (192.168.254.90) 56(84) bytes of data. 64 bytes from 192.168.254.90: icmp_seq=1 ttl=64 time=0.267 ms 64 bytes from 192.168.254.90: icmp_seq=2 ttl=64 time=0.240 ms ^Z [1]+ Stopped ping 192.168.254.90

Vault2:~ # ping 192.168.254.151 PING 192.168.254.151 (192.168.254.151) 56(84) bytes of data. 64 bytes from 192.168.254.151: icmp_seq=1 ttl=128 time=0.613 ms 64 bytes from 192.168.254.151: icmp_seq=2 ttl=128 time=0.509 ms ^Z [2]+ Stopped ping 192.168.254.151

Windows Steve-HP Connection-specific DNS Suffix . : local.ftr Link-local IPv6 Address . . . . . : fe80::4ed3:b709:bfa8:f20f%11 IPv4 Address. . . . . . . . . . . : 192.168.254.151 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.254.254

Pinging 192.168.254.90 with 32 bytes of data: Reply from 192.168.254.90: bytes=32 time=1ms TTL=64 Reply from 192.168.254.90: bytes=32 time<1ms TTL=64 Reply from 192.168.254.90: bytes=32 time<1ms TTL=64 Reply from 192.168.254.90: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.254.90: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 1ms, Average = 0ms PS C:\Users\Omen> PS C:\Users\Omen> ping 192.168.254.91

Pinging 192.168.254.91 with 32 bytes of data: Reply from 192.168.254.91: bytes=32 time<1ms TTL=64 Reply from 192.168.254.91: bytes=32 time<1ms TTL=64 Reply from 192.168.254.91: bytes=32 time<1ms TTL=64 Reply from 192.168.254.91: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.254.91: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms

They are all on the same switch connected to the same router.

4

This is what happens trying to add link

image

5

Very helpful, thank you! Assuming that the .151 machine also has a /24 subnet mask set and that you don’t have anything unusual going on with your switch (like VACLs, L2 ACLs, Protected Port), this would not seem to be a networking issue.

Your device vault2 seemed to have a LAN IP of 192.168.254.91/24 in your console log and a LAN IP of 172.17.0.3 in your GUI. What’s going on with that?

That “unexpected handshake message” error may also be important here. Is there anything in the log that would explain that? Feel free to post your entire log.

1 Like
6

vault1 after I tried it again 2024-10-02 15:18:03 Connection from RTJF5LO-NRTXHC3-JMKM3QD-F5RW2M5-F3RFPDM-O5JDB7Z-VCTO7XZ-ZIZKVAO at 172.232.11.126:22067 (relay-server) rejected: unknown device 2024-10-02 15:18:56 Established secure connection to RTJF5LO at 172.17.0.3:42462-66.110.9.44:443/relay-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P50-5VQN3MK1MDUEEHAJJU70L1KKDO 2024-10-02 15:18:56 Device RTJF5LO client is “syncthing v1.27.12” named “Vault2” at 172.17.0.3:42462-66.110.9.44:443/relay-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P50-5VQN3MK1MDUEEHAJJU70L1KKDO

Vault2 with some debugging on 2024-10-02 15:23:08 negative cache entry for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at global@https://discovery-v4.syncthing.net/v2/ valid until 2024-10-02 15:18:47.688486142 -0400 EDT m=+254368.788440671 or 2024-10-02 16:17:47.688487786 -0400 EDT m=+257908.788442315 2024-10-02 15:23:08 negative cache entry for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at global@https://discovery-v6.syncthing.net/v2/ valid until 2024-10-02 15:18:47.688491167 -0400 EDT m=+254368.788445696 or 2024-10-02 16:17:47.688491521 -0400 EDT m=+257908.788446050 2024-10-02 15:23:08 lookup results for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ 2024-10-02 15:23:08 addresses: [quic://172.17.0.3:22000 quic://47.197.2.78:1029 quic://47.197.2.78:22000 relay://172.232.11.126:22067/?id=YMPELZP-YR2G6X3-OML3HOE-ATYWZRT-NKLLHZI-2Z7KAK3-TT5CZVV-G5RQBAO tcp://172.17.0.3:22000 tcp://47.197.2.78:22000] 2024-10-02 15:23:08 negative cache entry for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at global@https://discovery-v6.syncthing.net/v2/ valid until 2024-10-02 14:55:41.522085409 -0400 EDT m=+252982.622039938 or 2024-10-02 15:54:41.522085766 -0400 EDT m=+256522.622040295 2024-10-02 15:23:08 lookup for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at IPv4 local 2024-10-02 15:23:08 addresses: [relay://136.54.129.162:22067/?id=XIDJFJC-Q4V3BTT-L7KC6TY-U65WS6Q-Q2BMICC-K4DOOQE-ZVEADZC-SH22KQB quic://172.17.0.1:22000 quic://192.168.254.151:22000 quic://169.254.148.192:22000 quic://169.254.30.206:22000 quic://192.168.137.1:22000 quic://47.197.2.78:22000 tcp://172.17.0.1:22000 tcp://192.168.254.151:22000 tcp://169.254.148.192:22000 tcp://169.254.30.206:22000 tcp://192.168.137.1:22000 tcp://47.197.2.78:40204 tcp://172.17.0.1:40204] 2024-10-02 15:23:08 lookup for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at IPv6 local 2024-10-02 15:23:08 addresses: 2024-10-02 15:23:08 cached discovery entry for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at global@https://discovery.syncthing.net/v2/ 2024-10-02 15:23:08 cache: {[quic://169.254.148.192:22000 quic://169.254.30.206:22000 quic://192.168.137.1:22000 quic://192.168.254.151:22000 quic://47.197.2.78:22000 relay://136.54.129.162:22067/?id=XIDJFJC-Q4V3BTT-L7KC6TY-U65WS6Q-Q2BMICC-K4DOOQE-ZVEADZC-SH22KQB relay://71.255.90.18:22067/?id=XLAKDGA-EK4QHOZ-KDDVZQF-V3UJ5EM-3ZMVP7K-PX2FALJ-LHX265Z-5QFLRQW tcp://169.254.148.192:22000 tcp://169.254.30.206:22000 tcp://192.168.137.1:22000 tcp://192.168.254.151:22000 tcp://47.197.2.78:22000 tcp://47.197.2.78:40204] {13958771900808658327 254434240954536 0x1adaaa0} true {0 0 } 0} 2024-10-02 15:23:08 negative cache entry for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at global@https://discovery-v4.syncthing.net/v2/ valid until 2024-10-02 14:55:41.522079857 -0400 EDT m=+252982.622034386 or 2024-10-02 15:54:41.522082004 -0400 EDT m=+256522.622036533 2024-10-02 15:23:08 lookup results for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB 2024-10-02 15:23:08 addresses: [quic://169.254.148.192:22000 quic://169.254.30.206:22000 quic://172.17.0.1:22000 quic://192.168.137.1:22000 quic://192.168.254.151:22000 quic://47.197.2.78:22000 relay://136.54.129.162:22067/?id=XIDJFJC-Q4V3BTT-L7KC6TY-U65WS6Q-Q2BMICC-K4DOOQE-ZVEADZC-SH22KQB relay://71.255.90.18:22067/?id=XLAKDGA-EK4QHOZ-KDDVZQF-V3UJ5EM-3ZMVP7K-PX2FALJ-LHX265Z-5QFLRQW tcp://169.254.148.192:22000 tcp://169.254.30.206:22000 tcp://172.17.0.1:22000 tcp://172.17.0.1:40204 tcp://192.168.137.1:22000 tcp://192.168.254.151:22000 tcp://47.197.2.78:22000 tcp://47.197.2.78:40204] 2024-10-02 15:23:15 discover: Received local announcement from 172.17.0.1:54505 for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB 2024-10-02 15:23:15 discover: Registering addresses for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB 2024-10-02 15:23:15 discover: Reconstructed URL is quic://172.17.0.1:22000 2024-10-02 15:23:15 discover: Replaced address 0.0.0.0 in quic://0.0.0.0:22000 to get quic://172.17.0.1:22000 2024-10-02 15:23:15 discover: Accepted address quic://192.168.254.151:22000 verbatim 2024-10-02 15:23:15 discover: Accepted address quic://169.254.148.192:22000 verbatim 2024-10-02 15:23:15 discover: Accepted address quic://169.254.30.206:22000 verbatim 2024-10-02 15:23:15 discover: Accepted address quic://192.168.137.1:22000 verbatim 2024-10-02 15:23:15 discover: Accepted address quic://47.197.2.78:22000 verbatim 2024-10-02 15:23:15 discover: Reconstructed URL is tcp://172.17.0.1:22000 2024-10-02 15:23:15 discover: Replaced address 0.0.0.0 in tcp://0.0.0.0:22000 to get tcp://172.17.0.1:22000 2024-10-02 15:23:15 discover: Accepted address tcp://192.168.254.151:22000 verbatim 2024-10-02 15:23:15 discover: Accepted address tcp://169.254.148.192:22000 verbatim 2024-10-02 15:23:15 discover: Accepted address tcp://169.254.30.206:22000 verbatim 2024-10-02 15:23:15 discover: Accepted address tcp://192.168.137.1:22000 verbatim 2024-10-02 15:23:15 discover: Accepted address tcp://47.197.2.78:40204 verbatim 2024-10-02 15:23:15 discover: Reconstructed URL is tcp://172.17.0.1:40204 2024-10-02 15:23:15 discover: Replaced address 0.0.0.0 in tcp://0.0.0.0:40204 to get tcp://172.17.0.1:40204 2024-10-02 15:23:15 discover: Accepted address relay://136.54.129.162:22067/?id=XIDJFJC-Q4V3BTT-L7KC6TY-U65WS6Q-Q2BMICC-K4DOOQE-ZVEADZC-SH22KQB verbatim 2024-10-02 15:23:19 discover: Received local announcement from 172.17.0.3:52444 for RTJF5LO-NRTXHC3-JMKM3QD-F5RW2M5-F3RFPDM-O5JDB7Z-VCTO7XZ-ZIZKVAO 2024-10-02 15:23:19 discover: Received local announcement from 172.17.0.1:40904 for RTJF5LO-NRTXHC3-JMKM3QD-F5RW2M5-F3RFPDM-O5JDB7Z-VCTO7XZ-ZIZKVAO 2024-10-02 15:23:23 cached discovery entry for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at global@https://discovery.syncthing.net/v2/ 2024-10-02 15:23:23 cache: {[quic://172.17.0.3:22000 quic://47.197.2.78:1029 quic://47.197.2.78:22000 relay://172.232.11.126:22067/?id=YMPELZP-YR2G6X3-OML3HOE-ATYWZRT-NKLLHZI-2Z7KAK3-TT5CZVV-G5RQBAO tcp://172.17.0.3:22000 tcp://47.197.2.78:22000] {13958772091243624855 254611623618304 0x1adaaa0} true {0 0 } 0} 2024-10-02 15:23:23 negative cache entry for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at global@https://discovery-v4.syncthing.net/v2/ valid until 2024-10-02 15:18:47.688486142 -0400 EDT m=+254368.788440671 or 2024-10-02 16:17:47.688487786 -0400 EDT m=+257908.788442315 2024-10-02 15:23:23 negative cache entry for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at global@https://discovery-v6.syncthing.net/v2/ valid until 2024-10-02 15:18:47.688491167 -0400 EDT m=+254368.788445696 or 2024-10-02 16:17:47.688491521 -0400 EDT m=+257908.788446050 2024-10-02 15:23:23 lookup for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at IPv4 local 2024-10-02 15:23:23 addresses: 2024-10-02 15:23:23 lookup for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at IPv6 local 2024-10-02 15:23:23 addresses: 2024-10-02 15:23:23 lookup results for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ 2024-10-02 15:23:23 addresses: [quic://172.17.0.3:22000 quic://47.197.2.78:1029 quic://47.197.2.78:22000 relay://172.232.11.126:22067/?id=YMPELZP-YR2G6X3-OML3HOE-ATYWZRT-NKLLHZI-2Z7KAK3-TT5CZVV-G5RQBAO tcp://172.17.0.3:22000 tcp://47.197.2.78:22000] 2024-10-02 15:23:23 lookup for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at IPv4 local 2024-10-02 15:23:23 addresses: [quic://172.17.0.1:22000 quic://192.168.254.151:22000 quic://169.254.148.192:22000 quic://169.254.30.206:22000 quic://192.168.137.1:22000 quic://47.197.2.78:22000 tcp://172.17.0.1:22000 tcp://192.168.254.151:22000 tcp://169.254.148.192:22000 tcp://169.254.30.206:22000 tcp://192.168.137.1:22000 tcp://47.197.2.78:40204 tcp://172.17.0.1:40204 relay://136.54.129.162:22067/?id=XIDJFJC-Q4V3BTT-L7KC6TY-U65WS6Q-Q2BMICC-K4DOOQE-ZVEADZC-SH22KQB] 2024-10-02 15:23:23 lookup for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at IPv6 local 2024-10-02 15:23:23 addresses: 2024-10-02 15:23:23 cached discovery entry for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at global@https://discovery.syncthing.net/v2/ 2024-10-02 15:23:23 cache: {[quic://169.254.148.192:22000 quic://169.254.30.206:22000 quic://192.168.137.1:22000 quic://192.168.254.151:22000 quic://47.197.2.78:22000 relay://136.54.129.162:22067/?id=XIDJFJC-Q4V3BTT-L7KC6TY-U65WS6Q-Q2BMICC-K4DOOQE-ZVEADZC-SH22KQB relay://71.255.90.18:22067/?id=XLAKDGA-EK4QHOZ-KDDVZQF-V3UJ5EM-3ZMVP7K-PX2FALJ-LHX265Z-5QFLRQW tcp://169.254.148.192:22000 tcp://169.254.30.206:22000 tcp://192.168.137.1:22000 tcp://192.168.254.151:22000 tcp://47.197.2.78:22000 tcp://47.197.2.78:40204] {13958771900808658327 254434240954536 0x1adaaa0} true {0 0 } 0} 2024-10-02 15:23:23 negative cache entry for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at global@https://discovery-v4.syncthing.net/v2/ valid until 2024-10-02 14:55:41.522079857 -0400 EDT m=+252982.622034386 or 2024-10-02 15:54:41.522082004 -0400 EDT m=+256522.622036533 2024-10-02 15:23:23 negative cache entry for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at global@https://discovery-v6.syncthing.net/v2/ valid until 2024-10-02 14:55:41.522085409 -0400 EDT m=+252982.622039938 or 2024-10-02 15:54:41.522085766 -0400 EDT m=+256522.622040295 2024-10-02 15:23:23 lookup results for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB 2024-10-02 15:23:23 addresses: [quic://169.254.148.192:22000 quic://169.254.30.206:22000 quic://172.17.0.1:22000 quic://192.168.137.1:22000 quic://192.168.254.151:22000 quic://47.197.2.78:22000 relay://136.54.129.162:22067/?id=XIDJFJC-Q4V3BTT-L7KC6TY-U65WS6Q-Q2BMICC-K4DOOQE-ZVEADZC-SH22KQB relay://71.255.90.18:22067/?id=XLAKDGA-EK4QHOZ-KDDVZQF-V3UJ5EM-3ZMVP7K-PX2FALJ-LHX265Z-5QFLRQW tcp://169.254.148.192:22000 tcp://169.254.30.206:22000 tcp://172.17.0.1:22000 tcp://172.17.0.1:40204 tcp://192.168.137.1:22000 tcp://192.168.254.151:22000 tcp://47.197.2.78:22000 tcp://47.197.2.78:40204] 2024-10-02 15:23:32 multicastBeacon: Exiting backoff state. 2024-10-02 15:23:32 multicastBeacon: Failed service ‘Service@0xc000146400 created by multicastBeacon@0xc00011c8c0/writer’ (1.000000 failures of 2.000000), restarting: true, error: write udp [::]:45096->[ff12::8384]:21027: sendmsg: cannot assign requested address 2024-10-02 15:23:32 multicastBeacon: Failed service ‘Service@0xc000146400 created by multicastBeacon@0xc00011c8c0/writer’ (1.999980 failures of 2.000000), restarting: true, error: write udp [::]:41259->[ff12::8384]:21027: sendmsg: cannot assign requested address 2024-10-02 15:23:40 negative cache entry for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at global@https://discovery-v6.syncthing.net/v2/ valid until 2024-10-02 15:18:47.688491167 -0400 EDT m=+254368.788445696 or 2024-10-02 16:17:47.688491521 -0400 EDT m=+257908.788446050 2024-10-02 15:23:40 lookup for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at IPv4 local 2024-10-02 15:23:40 addresses: 2024-10-02 15:23:40 lookup for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at IPv6 local 2024-10-02 15:23:40 addresses: 2024-10-02 15:23:40 cached discovery entry for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at global@https://discovery.syncthing.net/v2/ 2024-10-02 15:23:40 cache: {[quic://172.17.0.3:22000 quic://47.197.2.78:1029 quic://47.197.2.78:22000 relay://172.232.11.126:22067/?id=YMPELZP-YR2G6X3-OML3HOE-ATYWZRT-NKLLHZI-2Z7KAK3-TT5CZVV-G5RQBAO tcp://172.17.0.3:22000 tcp://47.197.2.78:22000] {13958772091243624855 254611623618304 0x1adaaa0} true {0 0 } 0} 2024-10-02 15:23:40 negative cache entry for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at global@https://discovery-v4.syncthing.net/v2/ valid until 2024-10-02 15:18:47.688486142 -0400 EDT m=+254368.788440671 or 2024-10-02 16:17:47.688487786 -0400 EDT m=+257908.788442315 2024-10-02 15:23:40 lookup results for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ 2024-10-02 15:23:40 addresses: [quic://172.17.0.3:22000 quic://47.197.2.78:1029 quic://47.197.2.78:22000 relay://172.232.11.126:22067/?id=YMPELZP-YR2G6X3-OML3HOE-ATYWZRT-NKLLHZI-2Z7KAK3-TT5CZVV-G5RQBAO tcp://172.17.0.3:22000 tcp://47.197.2.78:22000] 2024-10-02 15:23:40 negative cache entry for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at global@https://discovery-v4.syncthing.net/v2/ valid until 2024-10-02 14:55:41.522079857 -0400 EDT m=+252982.622034386 or 2024-10-02 15:54:41.522082004 -0400 EDT m=+256522.622036533 2024-10-02 15:23:40 negative cache entry for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at global@https://discovery-v6.syncthing.net/v2/ valid until 2024-10-02 14:55:41.522085409 -0400 EDT m=+252982.622039938 or 2024-10-02 15:54:41.522085766 -0400 EDT m=+256522.622040295 2024-10-02 15:23:40 lookup for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at IPv4 local 2024-10-02 15:23:40 addresses: [quic://172.17.0.1:22000 quic://192.168.254.151:22000 quic://169.254.148.192:22000 quic://169.254.30.206:22000 quic://192.168.137.1:22000 quic://47.197.2.78:22000 tcp://172.17.0.1:22000 tcp://192.168.254.151:22000 tcp://169.254.148.192:22000 tcp://169.254.30.206:22000 tcp://192.168.137.1:22000 tcp://47.197.2.78:40204 tcp://172.17.0.1:40204 relay://136.54.129.162:22067/?id=XIDJFJC-Q4V3BTT-L7KC6TY-U65WS6Q-Q2BMICC-K4DOOQE-ZVEADZC-SH22KQB] 2024-10-02 15:23:40 lookup for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at IPv6 local 2024-10-02 15:23:40 addresses: 2024-10-02 15:23:40 cached discovery entry for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at global@https://discovery.syncthing.net/v2/ 2024-10-02 15:23:40 cache: {[quic://169.254.148.192:22000 quic://169.254.30.206:22000 quic://192.168.137.1:22000 quic://192.168.254.151:22000 quic://47.197.2.78:22000 relay://136.54.129.162:22067/?id=XIDJFJC-Q4V3BTT-L7KC6TY-U65WS6Q-Q2BMICC-K4DOOQE-ZVEADZC-SH22KQB relay://71.255.90.18:22067/?id=XLAKDGA-EK4QHOZ-KDDVZQF-V3UJ5EM-3ZMVP7K-PX2FALJ-LHX265Z-5QFLRQW tcp://169.254.148.192:22000 tcp://169.254.30.206:22000 tcp://192.168.137.1:22000 tcp://192.168.254.151:22000 tcp://47.197.2.78:22000 tcp://47.197.2.78:40204] {13958771900808658327 254434240954536 0x1adaaa0} true {0 0 } 0} 2024-10-02 15:23:40 lookup results for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB 2024-10-02 15:23:40 addresses: [quic://169.254.148.192:22000 quic://169.254.30.206:22000 quic://172.17.0.1:22000 quic://192.168.137.1:22000 quic://192.168.254.151:22000 quic://47.197.2.78:22000 relay://136.54.129.162:22067/?id=XIDJFJC-Q4V3BTT-L7KC6TY-U65WS6Q-Q2BMICC-K4DOOQE-ZVEADZC-SH22KQB relay://71.255.90.18:22067/?id=XLAKDGA-EK4QHOZ-KDDVZQF-V3UJ5EM-3ZMVP7K-PX2FALJ-LHX265Z-5QFLRQW tcp://169.254.148.192:22000 tcp://169.254.30.206:22000 tcp://172.17.0.1:22000 tcp://172.17.0.1:40204 tcp://192.168.137.1:22000 tcp://192.168.254.151:22000 tcp://47.197.2.78:22000 tcp://47.197.2.78:40204] 2024-10-02 15:23:43 StaticClient:0xc000ecb720@relay://66.110.9.44:443/?id=AT6IL4Q-VP7RMX6-CF4FU2K-JUUAK26-CEM577I-VNHUMUD-AGCJUQN-CTHWPAF received message protocol.Ping 2024-10-02 15:23:43 StaticClient:0xc000ecb720@relay://66.110.9.44:443/?id=AT6IL4Q-VP7RMX6-CF4FU2K-JUUAK26-CEM577I-VNHUMUD-AGCJUQN-CTHWPAF sent pong 2024-10-02 15:23:45 discover: Received local announcement from 172.17.0.1:54505 for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB 2024-10-02 15:23:45 discover: Registering addresses for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB 2024-10-02 15:23:45 discover: Reconstructed URL is tcp://172.17.0.1:22000 2024-10-02 15:23:45 discover: Replaced address 0.0.0.0 in tcp://0.0.0.0:22000 to get tcp://172.17.0.1:22000 2024-10-02 15:23:45 discover: Accepted address tcp://192.168.254.151:22000 verbatim 2024-10-02 15:23:45 discover: Accepted address tcp://169.254.148.192:22000 verbatim 2024-10-02 15:23:45 discover: Accepted address tcp://169.254.30.206:22000 verbatim 2024-10-02 15:23:45 discover: Accepted address tcp://192.168.137.1:22000 verbatim 2024-10-02 15:23:45 discover: Accepted address tcp://47.197.2.78:40204 verbatim 2024-10-02 15:23:45 discover: Reconstructed URL is tcp://172.17.0.1:40204 2024-10-02 15:23:45 discover: Replaced address 0.0.0.0 in tcp://0.0.0.0:40204 to get tcp://172.17.0.1:40204 2024-10-02 15:23:45 discover: Accepted address relay://136.54.129.162:22067/?id=XIDJFJC-Q4V3BTT-L7KC6TY-U65WS6Q-Q2BMICC-K4DOOQE-ZVEADZC-SH22KQB verbatim 2024-10-02 15:23:45 discover: Reconstructed URL is quic://172.17.0.1:22000 2024-10-02 15:23:45 discover: Replaced address 0.0.0.0 in quic://0.0.0.0:22000 to get quic://172.17.0.1:22000 2024-10-02 15:23:45 discover: Accepted address quic://192.168.254.151:22000 verbatim 2024-10-02 15:23:45 discover: Accepted address quic://169.254.148.192:22000 verbatim 2024-10-02 15:23:45 discover: Accepted address quic://169.254.30.206:22000 verbatim 2024-10-02 15:23:45 discover: Accepted address quic://192.168.137.1:22000 verbatim 2024-10-02 15:23:45 discover: Accepted address quic://47.197.2.78:22000 verbatim 2024-10-02 15:23:49 multicastBeacon: Entering the backoff state. 2024-10-02 15:23:49 discover: Received local announcement from 172.17.0.3:52444 for RTJF5LO-NRTXHC3-JMKM3QD-F5RW2M5-F3RFPDM-O5JDB7Z-VCTO7XZ-ZIZKVAO 2024-10-02 15:23:49 multicastBeacon: Failed service ‘Service@0xc000146400 created by multicastBeacon@0xc00011c8c0/writer’ (2.350821 failures of 2.000000), restarting: false, error: write udp [::]:53563->[ff12::8384]:21027: sendmsg: cannot assign requested address 2024-10-02 15:23:49 discover: Received local announcement from 172.17.0.1:58919 for RTJF5LO-NRTXHC3-JMKM3QD-F5RW2M5-F3RFPDM-O5JDB7Z-VCTO7XZ-ZIZKVAO 2024-10-02 15:23:55 lookup for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at IPv6 local 2024-10-02 15:23:55 addresses: 2024-10-02 15:23:55 cached discovery entry for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at global@https://discovery.syncthing.net/v2/ 2024-10-02 15:23:55 cache: {[quic://172.17.0.3:22000 quic://47.197.2.78:1029 quic://47.197.2.78:22000 relay://172.232.11.126:22067/?id=YMPELZP-YR2G6X3-OML3HOE-ATYWZRT-NKLLHZI-2Z7KAK3-TT5CZVV-G5RQBAO tcp://172.17.0.3:22000 tcp://47.197.2.78:22000] {13958772091243624855 254611623618304 0x1adaaa0} true {0 0 } 0} 2024-10-02 15:23:55 negative cache entry for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at global@https://discovery-v4.syncthing.net/v2/ valid until 2024-10-02 15:18:47.688486142 -0400 EDT m=+254368.788440671 or 2024-10-02 16:17:47.688487786 -0400 EDT m=+257908.788442315 2024-10-02 15:23:55 negative cache entry for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at global@https://discovery-v6.syncthing.net/v2/ valid until 2024-10-02 15:18:47.688491167 -0400 EDT m=+254368.788445696 or 2024-10-02 16:17:47.688491521 -0400 EDT m=+257908.788446050 2024-10-02 15:23:55 lookup for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at IPv4 local 2024-10-02 15:23:55 addresses: 2024-10-02 15:23:55 lookup results for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ 2024-10-02 15:23:55 addresses: [quic://172.17.0.3:22000 quic://47.197.2.78:1029 quic://47.197.2.78:22000 relay://172.232.11.126:22067/?id=YMPELZP-YR2G6X3-OML3HOE-ATYWZRT-NKLLHZI-2Z7KAK3-TT5CZVV-G5RQBAO tcp://172.17.0.3:22000 tcp://47.197.2.78:22000] 2024-10-02 15:23:55 cached discovery entry for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at global@https://discovery.syncthing.net/v2/ 2024-10-02 15:23:55 cache: {[quic://169.254.148.192:22000 quic://169.254.30.206:22000 quic://192.168.137.1:22000 quic://192.168.254.151:22000 quic://47.197.2.78:22000 relay://136.54.129.162:22067/?id=XIDJFJC-Q4V3BTT-L7KC6TY-U65WS6Q-Q2BMICC-K4DOOQE-ZVEADZC-SH22KQB relay://71.255.90.18:22067/?id=XLAKDGA-EK4QHOZ-KDDVZQF-V3UJ5EM-3ZMVP7K-PX2FALJ-LHX265Z-5QFLRQW tcp://169.254.148.192:22000 tcp://169.254.30.206:22000 tcp://192.168.137.1:22000 tcp://192.168.254.151:22000 tcp://47.197.2.78:22000 tcp://47.197.2.78:40204] {13958771900808658327 254434240954536 0x1adaaa0} true {0 0 } 0} 2024-10-02 15:23:55 negative cache entry for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at global@https://discovery-v4.syncthing.net/v2/ valid until 2024-10-02 14:55:41.522079857 -0400 EDT m=+252982.622034386 or 2024-10-02 15:54:41.522082004 -0400 EDT m=+256522.622036533 2024-10-02 15:23:55 negative cache entry for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at global@https://discovery-v6.syncthing.net/v2/ valid until 2024-10-02 14:55:41.522085409 -0400 EDT m=+252982.622039938 or 2024-10-02 15:54:41.522085766 -0400 EDT m=+256522.622040295 2024-10-02 15:23:55 lookup for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at IPv4 local 2024-10-02 15:23:55 addresses: [tcp://172.17.0.1:22000 tcp://192.168.254.151:22000 tcp://169.254.148.192:22000 tcp://169.254.30.206:22000 tcp://192.168.137.1:22000 tcp://47.197.2.78:40204 tcp://172.17.0.1:40204 relay://136.54.129.162:22067/?id=XIDJFJC-Q4V3BTT-L7KC6TY-U65WS6Q-Q2BMICC-K4DOOQE-ZVEADZC-SH22KQB quic://172.17.0.1:22000 quic://192.168.254.151:22000 quic://169.254.148.192:22000 quic://169.254.30.206:22000 quic://192.168.137.1:22000 quic://47.197.2.78:22000] 2024-10-02 15:23:55 lookup for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at IPv6 local 2024-10-02 15:23:55 addresses: 2024-10-02 15:23:55 lookup results for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB 2024-10-02 15:23:55 addresses: [quic://169.254.148.192:22000 quic://169.254.30.206:22000 quic://172.17.0.1:22000 quic://192.168.137.1:22000 quic://192.168.254.151:22000 quic://47.197.2.78:22000 relay://136.54.129.162:22067/?id=XIDJFJC-Q4V3BTT-L7KC6TY-U65WS6Q-Q2BMICC-K4DOOQE-ZVEADZC-SH22KQB relay://71.255.90.18:22067/?id=XLAKDGA-EK4QHOZ-KDDVZQF-V3UJ5EM-3ZMVP7K-PX2FALJ-LHX265Z-5QFLRQW tcp://169.254.148.192:22000 tcp://169.254.30.206:22000 tcp://172.17.0.1:22000 tcp://172.17.0.1:40204 tcp://192.168.137.1:22000 tcp://192.168.254.151:22000 tcp://47.197.2.78:22000 tcp://47.197.2.78:40204] 2024-10-02 15:24:13 cached discovery entry for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at global@https://discovery.syncthing.net/v2/ 2024-10-02 15:24:13 cache: {[quic://172.17.0.3:22000 quic://47.197.2.78:1029 quic://47.197.2.78:22000 relay://172.232.11.126:22067/?id=YMPELZP-YR2G6X3-OML3HOE-ATYWZRT-NKLLHZI-2Z7KAK3-TT5CZVV-G5RQBAO tcp://172.17.0.3:22000 tcp://47.197.2.78:22000] {13958772091243624855 254611623618304 0x1adaaa0} true {0 0 } 0} 2024-10-02 15:24:13 negative cache entry for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at global@https://discovery-v4.syncthing.net/v2/ valid until 2024-10-02 15:18:47.688486142 -0400 EDT m=+254368.788440671 or 2024-10-02 16:17:47.688487786 -0400 EDT m=+257908.788442315 2024-10-02 15:24:13 negative cache entry for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at global@https://discovery-v6.syncthing.net/v2/ valid until 2024-10-02 15:18:47.688491167 -0400 EDT m=+254368.788445696 or 2024-10-02 16:17:47.688491521 -0400 EDT m=+257908.788446050 2024-10-02 15:24:13 lookup for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at IPv4 local 2024-10-02 15:24:13 addresses: 2024-10-02 15:24:13 lookup for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ at IPv6 local 2024-10-02 15:24:13 addresses: 2024-10-02 15:24:13 lookup results for OKIZFI4-VB5KKS3-NSJ54GQ-IPPIAWX-V6I7SVE-6JQGYL5-LQ7CDAI-NIY6OQJ 2024-10-02 15:24:13 addresses: [quic://172.17.0.3:22000 quic://47.197.2.78:1029 quic://47.197.2.78:22000 relay://172.232.11.126:22067/?id=YMPELZP-YR2G6X3-OML3HOE-ATYWZRT-NKLLHZI-2Z7KAK3-TT5CZVV-G5RQBAO tcp://172.17.0.3:22000 tcp://47.197.2.78:22000] 2024-10-02 15:24:13 cached discovery entry for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at global@https://discovery.syncthing.net/v2/ 2024-10-02 15:24:13 cache: {[quic://169.254.148.192:22000 quic://169.254.30.206:22000 quic://192.168.137.1:22000 quic://192.168.254.151:22000 quic://47.197.2.78:22000 relay://136.54.129.162:22067/?id=XIDJFJC-Q4V3BTT-L7KC6TY-U65WS6Q-Q2BMICC-K4DOOQE-ZVEADZC-SH22KQB relay://71.255.90.18:22067/?id=XLAKDGA-EK4QHOZ-KDDVZQF-V3UJ5EM-3ZMVP7K-PX2FALJ-LHX265Z-5QFLRQW tcp://169.254.148.192:22000 tcp://169.254.30.206:22000 tcp://192.168.137.1:22000 tcp://192.168.254.151:22000 tcp://47.197.2.78:22000 tcp://47.197.2.78:40204] {13958771900808658327 254434240954536 0x1adaaa0} true {0 0 } 0} 2024-10-02 15:24:13 negative cache entry for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at global@https://discovery-v4.syncthing.net/v2/ valid until 2024-10-02 14:55:41.522079857 -0400 EDT m=+252982.622034386 or 2024-10-02 15:54:41.522082004 -0400 EDT m=+256522.622036533 2024-10-02 15:24:13 negative cache entry for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at global@https://discovery-v6.syncthing.net/v2/ valid until 2024-10-02 14:55:41.522085409 -0400 EDT m=+252982.622039938 or 2024-10-02 15:54:41.522085766 -0400 EDT m=+256522.622040295 2024-10-02 15:24:13 lookup for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at IPv4 local 2024-10-02 15:24:13 addresses: [tcp://172.17.0.1:22000 tcp://192.168.254.151:22000 tcp://169.254.148.192:22000 tcp://169.254.30.206:22000 tcp://192.168.137.1:22000 tcp://47.197.2.78:40204 tcp://172.17.0.1:40204 relay://136.54.129.162:22067/?id=XIDJFJC-Q4V3BTT-L7KC6TY-U65WS6Q-Q2BMICC-K4DOOQE-ZVEADZC-SH22KQB quic://172.17.0.1:22000 quic://192.168.254.151:22000 quic://169.254.148.192:22000 quic://169.254.30.206:22000 quic://192.168.137.1:22000 quic://47.197.2.78:22000] 2024-10-02 15:24:13 lookup for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB at IPv6 local 2024-10-02 15:24:13 addresses: 2024-10-02 15:24:13 lookup results for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB 2024-10-02 15:24:13 addresses: [quic://169.254.148.192:22000 quic://169.254.30.206:22000 quic://172.17.0.1:22000 quic://192.168.137.1:22000 quic://192.168.254.151:22000 quic://47.197.2.78:22000 relay://136.54.129.162:22067/?id=XIDJFJC-Q4V3BTT-L7KC6TY-U65WS6Q-Q2BMICC-K4DOOQE-ZVEADZC-SH22KQB relay://71.255.90.18:22067/?id=XLAKDGA-EK4QHOZ-KDDVZQF-V3UJ5EM-3ZMVP7K-PX2FALJ-LHX265Z-5QFLRQW tcp://169.254.148.192:22000 tcp://169.254.30.206:22000 tcp://172.17.0.1:22000 tcp://172.17.0.1:40204 tcp://192.168.137.1:22000 tcp://192.168.254.151:22000 tcp://47.197.2.78:22000 tcp://47.197.2.78:40204] 2024-10-02 15:24:15 discover: Received local announcement from 172.17.0.1:54505 for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB 2024-10-02 15:24:15 discover: Registering addresses for 5HR5YST-TYVJPAI-PE3D7LU-XDTL6ZF-UC4CHIY-RLLEQ4U-HBVKGGH-MUKUIQB 2024-10-02 15:24:15 discover: Reconstructed URL is tcp://172.17.0.1:22000 2024-10-02 15:24:15 discover: Replaced address 0.0.0.0 in tcp://0.0.0.0:22000 to get tcp://172.17.0.1:22000 2024-10-02 15:24:15 discover: Accepted address tcp://192.168.254.151:22000 verbatim 2024-10-02 15:24:15 discover: Accepted address tcp://169.254.148.192:22000 verbatim 2024-10-02 15:24:15 discover: Accepted address tcp://169.254.30.206:22000 verbatim 2024-10-02 15:24:15 discover: Accepted address tcp://192.168.137.1:22000 verbatim 2024-10-02 15:24:15 discover: Accepted address tcp://47.197.2.78:40204 verbatim 2024-10-02 15:24:15 discover: Reconstructed URL is tcp://172.17.0.1:40204 2024-10-02 15:24:15 discover: Replaced address 0.0.0.0 in tcp://0.0.0.0:40204 to get tcp://172.17.0.1:40204 2024-10-02 15:24:15 discover: Accepted address relay://136.54.129.162:22067/?id=XIDJFJC-Q4V3BTT-L7KC6TY-U65WS6Q-Q2BMICC-K4DOOQE-ZVEADZC-SH22KQB verbatim 2024-10-02 15:24:15 discover: Reconstructed URL is quic://172.17.0.1:22000 2024-10-02 15:24:15 discover: Replaced address 0.0.0.0 in quic://0.0.0.0:22000 to get quic://172.17.0.1:22000 2024-10-02 15:24:15 discover: Accepted address quic://192.168.254.151:22000 verbatim 2024-10-02 15:24:15 discover: Accepted address quic://169.254.148.192:22000 verbatim 2024-10-02 15:24:15 discover: Accepted address quic://169.254.30.206:22000 verbatim 2024-10-02 15:24:15 discover: Accepted address quic://192.168.137.1:22000 verbatim 2024-10-02 15:24:15 discover: Accepted address quic://47.197.2.78:22000 verbatim

This is all I could fit. I’ll turn debug off and see. It has something to do with ROCKSTOR NAS

7

Thanks!

Please let us know if vault2 is on 192.168.254.91, 172.17.0.3, or both. Please also take a look at Actions/Settings/Connections and let us know what you have in Sync Protocol Listen Addresses (if it’s “default” that will help me understand that this isn’t part of your issue).

In order to help me parse your log, what are the first five characters of each of your Device IDs please? Your device vault2 is RTJF5LO (I’m not trying to do anything nefarious, see FAQ — Syncthing documentation regarding Device IDs not being sensitive).

8

Got it… I put the address of the port instead of dynamic in the add remote device

the 192 address is the box and the 172 Is something in Rockstor.

Rockstor and syncthing are running in dockers

Vault2 RTJF5

image
image884×528 13.3 KB

Vault1 OKIZF

image
image896×533 13.1 KB

@chaos Thanks so much for the help

1 Like
9

@kaufstev Happy to help!

It’s not 100% clear to me from your last post: is everything working as expected now?

11

Yes by putting in the IP addr it is working correctly.

1 Like
12

@er-pa The “connected to self”-message may be a solid indication here, if it still does not work. That sounds like Vault1 tries to connect to Vault2 but ends up connecting to Vault1 (itself).

I did not see that anywhere but why would it do that?

13

It was in assiging ip address out of my network - #4 by kaufstev that screenshot.

The only times I’ve seen this happen is when for some reason global discovery / relays were used while two devices were behind the same NAT-gateway.

I can’t really deduct if that’s the case here or if something else causes this. But either way, that message shouldn’t be shown.

14

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.