tomli
November 13, 2015, 7:36am
1
After updating syncthing on Android to the current version, which uses syncthing 0.12.1, my Android (6.0) device won’t connect to my notebook running ubuntu 14.04.
With STRACE=discovery,connections, I get the potentially suspicious line on Android:
connections.go:285:INFO: Failed to parse connection url: tcp://[....%wlan0]:22000 parse tcp://[...%wlan0]:22000: hexadecimal escape in host
Any recommendations?
Regards,
Tom
wweich
November 13, 2015, 7:52am
2
There have been github issues about that problem.
The current one is …
If you don’t use IPv6 on your Ubuntu machine, you can disable that to workaround that issue.
calmh
(Jakob Borg)
November 13, 2015, 8:22am
3
The problem only affects local IPv6 discovery though; local IPv4 and global discovery should work just fine.
tomli
November 13, 2015, 10:11am
4
Thanks for the hint. After disabling ipv6 as described at https://askubuntu.com/questions/440649/how-to-disable-ipv6-in-ubuntu-14-04 the message has disappeared from the log on the Android device. Now I get:
local.go:172: received local announcement
connections_tcp.go:43 connection timed out
connections.go:285 dial failed
The log on the Ubuntu side doesn’t show much.
Is there anything I can do?
calmh
(Jakob Borg)
November 13, 2015, 10:41am
5
Connection timed out sounds like a genuine network or firewall problem.
tomli
November 13, 2015, 12:04pm
6
I didn’t change anything though.
On Ubuntu the log looks quite different from the Android log. Here I get:
[...] 2015/11/13 13:02:01.263572 cache.go:99: DEBUG: lookup for ... at IPv6 local
[...] 2015/11/13 13:02:01.263626 cache.go:100: DEBUG: direct: []
[...] 2015/11/13 13:02:01.263673 cache.go:101: DEBUG: relays: []
[...] 2015/11/13 13:02:01.263572 cache.go:99: DEBUG: lookup for ... at IPv4 local
[...] 2015/11/13 13:02:01.263626 cache.go:100: DEBUG: direct: []
[...] 2015/11/13 13:02:01.263673 cache.go:101: DEBUG: relays: []
I only use local lookups.
Is there anything I can do?
It’s your firewall, read the guide on how to setup your firewall.
Also, make sure your listen addresses are reasonable.
tomli
November 13, 2015, 1:50pm
8
Ok, you’re right. I don’t quite understand what has changed though but this seems to have caused the problem. Thanks a lot for pushing me to review my firewall rules.
tomli
November 13, 2015, 2:03pm
9
For the records: I had udp:21025 unblocked. Now syncthing seemingly requires udp:21027 to be unblocked.