I have now tried several times and I have the same issue with my synology docker node. Port mapping on router correctly set Started node with tcp and udp port No firewalls active on my synology Node runs newest version (v1.49.5) Restarted node several times Still says: QUIC Misconfigured Any hint…

I have a test node on DSM 7 and QUIC works fine. You need to set “rmem_max” when starting DSM, not in “docker run” [syn_task1] [syn_task2] [syn_task3] sysctl -w net.core.rmem_max=2500000 and restart DSM (your Synology) and stop, rm, start your SN without [syn_task4]

Hmm not experienced in LINUX stuff but it would be nice if someone can re-write this to DSM - Docker like “format”. :innocent: But anyway is funny that other people does not have this issue on SYNOLOGY and DSM. Thank you Wigo

I start to believe that update on your Synology did not goes well…

Yes looks like I have to try reset network as first step and than as second step reinstall DSM on SYNOLOGY.

After messing around with a Synology NAS and Docker on the DSM I was able to finally figure out why some, may not be able to get quic working, and a fix for that. If you have a Synology nas, and you have followed all the documented steps to get quic working, and it is still misconfigured on your Sy…

Hello @Vortal , Welcome to the forum! Could you please describe in details what you did to fix the issue? This would help other Community members to understand, how to fix it.

You need to make sure there are no DENY or DROP entries in your Docker Isolation Chain on Iptables on the Synology NAS with SSH. if you have run development setups on docker on your nas there may be some stale entries. A ds1621+ for instances comes with a 4 port NIC card. If you are utilizing all o…

I don’t use more than 1 eth port on my DS216+, running 2 nodes on 2 HDDs, but I had QUICK missconfigured when I tryed using the same 28967 internal port for both. So my advise is to use different ports, internal and external, in router and in docker run, for each node, for tcp, udp, dashboard. Using…

Then you also need to change the internal listening ports either in your config.yaml or with an argument options, especially for dashboard (console.address) and listening address (server.address).

I got fast open working last night. Made a decent improvement in my wins / uploads etc. My average bw went up considerably.

Yes, I know it impuves a lot, but we, Synology users, are cut out, because Synology plays by its own rules, and what it is working for the majority, dosen’t seem to work for Syno. My canceled uploads and downloads are through the roof ever since tcp_fastopen has been implemented and addopted by majo…