UDP QUIC configuration guide for linux / docker

[SGC]

Changelog v1.28.2 (title has already been used)

For Storage Nodes Move Deleted Pieces to Trash UDP Pingback We haven’t finished our research around QUIC yet. At some point, all storage nodes need to forward UDP traffic. In a first step, the satellite will check if the UDP port is open. The outcome is already visible in the storage node log but not on the storage node dashboard. If you haven’t already please forward TCP and UDP traffic. For Customers New Branding, Pricing and Free Tier We changed our branding. Tardigrade is now Storj …

[o1eal]

With the first command I get this error:

$ sudo echo "n$ sudo echo "net.core.rmem_max=2500000" >> /etc/sysctl.conf
-bash: /etc/sysctl.conf: Permission denied

I did open the UDP ports on my router, and I did modify the docker-compose configuration to include UDP and then I rebooted. But the storj.net.info ping gives me the following:

• started
• TCP: dialed node in 314ms
• QUIC: couldn’t connect to node: rpc: quic: context deadline exceeded

So it seems this was unsuccessful. I’m not sure how much of my actions I should undo now since it does not seem to be helping anything.

*** UPDATED ***
After a few hours, I tried again…it works now! The “Dial” button results in:

• started
• QUIC: dialed node in 159ms
• TCP: dialed node in 309ms

*** UPDATED AGAIN ***
Even though UDP was properly exposed, after having read the official documentation page, I think my previous efforts were insufficient.

I found that I was able to run the commands successfully if I switched to the root user (instead of simply using sudo.) That is, I first ran sudo su to get to the root user, and then followed the instructions from there. This worked (but of course, be very careful when logged in as root user.)

I do have a lingering question whether maybe I was supposed to do this in the docker container, rather than…or in addition to…on the host machine itself.