Syncthing (v1.18) ignores QUIC. Is that supposed to happen in that version?

Support
1

I’m running Syncthing v1.18 on Ubuntu, as that is the version packaged in the system repository. I have my nodes configured to listen on both TCP and QUIC, but the nodes are not enabling a QUIC listener. TCP connections work just fine.

It’s a quite old version, but does someone know if QUIC is supposed to work in v1.18? Judging from the release notes QUIC was introduced before that, but the release notes on Github are hard to search through so I may have missed something.

2

Probably also depends on who built it and how, but yes.

3

Is this answering “Syncthing (v1.18) ignores quick. Is that supposed to happen in that version?” or “does someone know if QUIC is supposed to work in v1.18?” ?

I’m just using whatever the Ubuntu standard repositories give me.

4

QUIC was available in 1.18, yes, but Ubuntu/Debian uses a patched version so who knows. Either need to ask them, or just use a newer build. It’s been five years.

1 Like
5

I’m running 1.29.7 (from the upstream provided deb repository) on a mix of computers – my pop-os desktop (derived from ubuntu 22.04), a raspberrry pi 3b running stable raspberry os (derived from debian bookworm), and a samsung android tablet. I can’t get QUIC either, IIRC not between any 2 of these 3.

For the android I could blame this on the stupid ISP forced router, but the desktop and the Pi are on ethernet, with just a hub between them.

6

@nobrowser @JanKanis Y’all know that TCP is preferred over QUIC by default? You have to configure Syncthing to prefer QUIC.

7

Yes, but in my case Syncthing is not even enabling the QUIC listener. Even with TCP preferred I would expect it to at least listen for QUIC.

1 Like
8

Yes, same here.

9

How about anyone show a log or screenshot of what the actual problem you’re seeing is? Ideally including the version output from the log (like, the first line) or a screenshot of the about box.

1 Like
10

quic-go in these old versions was a PITA regarding golang compatibility. I guess they simply disabled it.

1 Like
11

That’s my guess too but then there are claims of our build of 1.29.7 and “same here” and it’s all very vague. I don’t think it’s same at all, so some explicitness would be appreciated

2 Likes
12

For me the question I had is answered, I only wanted to know if QUIC is supposed to work in my (very old) version, and the answer is “maybe not”, because it depends on how the debian ppl built it. TCP is functioning just fine for me, and if I decide I want to dive deeper in getting QUIC I’ll install a newer version.

Maybe the v1.29 issue should go to a separate thread, as this thread explicitly has v1.18 in the title.

2 Likes
13

The Ubuntu source code for syncthing (e.g. patches and build scripts) is freely available for anyone: Ubuntu – Details of source package syncthing in jammy

(Note that for syncthing, the Debian-packaged version differs from the Ubuntu-packaged version)

The specific Ubuntu source code for v1.18 is here: https://archive.ubuntu.com/ubuntu/pool/universe/s/syncthing/syncthing_1.18.0~ds1-3ubuntu0.3.debian.tar.xz

I can’t see anything obvious in their scripts that would disable QUIC, and they include it in their dependency tree. My presumption would be that QUIC is enabled in that build.

We should also note that you can run a recent version of syncthing trough apt, as syncthing publishes official packages: https://apt.syncthing.net/

1 Like
14

I run the one from the syncthing specific repo (except on android, that app is via F-Droid). So Ubuntu and Debian build steps are not relevant, for my situation.

I’ll attempt a screenshot when I’m better awake (it’s hard work for me, I am very non-visual type).