On ubuntu and synology i set
sysctl -w net.core.rmem_max=2500000
On host and I dont see warn message about buffer size in container logs… But i dont do the UDP test so dont know if its clear way
Keep in mind that that setting won’t survive reboots. On synology editing sysctl.conf isn’t that useful as it will get overwritten by DSM updates. In order to set it on boot it’s best to use the task scheduler to trigger that command on boot.
1 Like
After i enabled UDP protocol.I had some problems with dns config.I searched for errors and decided to change my nameservers to google ones.After that my egress showed a lot of improvement compared to before that.This is 3 day timeframe
So how ?
8.8.8.8
8.8.4.4 ???
1 Like
Hello everyone,
I want to open my nodes to the UDP protocol.
I use W10 with docker, I have already opened the ports in the Router, Windows Firewall and added the suggested string
-p <host-port>:<container-port>/tcp -p <host-port>:<container-port>/udp
on the DOCKER configuration, but how can I test that it works with windows10?
Best Regards
Tony
I don’t want to be short with you, but you could start by literally reading the first post in this topic.
It’s not ‘that’ obvious, as you’d need to install Go for Windows first and then run the script mentioned.
Pretty obvious as that’s literally stated in the comment. As far as I can tell it’s all explained in that post. It may not be the most straight forward process, but it’s all there. I’m sure people here are happy to help if there is a more specific question about it. But the question of how to test it has been answered.
My jails on FreeNAS are happily using UDP though I had to set a different tuneable for BSD to stop the buffer size error when my storagenodes start. I set the tuneable kern.ipc.maxsockbuf to 30146560 in sysctl. No idea if it’s an optimal value but I picked it up from Increase OS UDP Buffers to Improve Performance | by Cameron Sparr | Medium
1 Like
Just reconfigured my nodes today. I’m now part of the UDP family, yay! 
pi@raspberrypi:~/storj-udp-test $ go run ./cmd/connect-test 127.0.0.1:XXXX
2021/05/01 17:33:24 failed to sufficiently increase receive buffer size (was: 160 kiB, wanted: 2048 kiB, got: 320 kiB). See https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size for details.
QUIC success 12VH[...]6oHS
TCP success 12VH[...]6oHS
Despite some hints above in this thread, I’m not clear on these:
- Does the error about the buffer size needs us to do something, or is it just related to the test tool (i.e. the node software won’t be affected)?
- Is enabling UDP going to change something with regards to our nodes’ traffic?
@kirbah’s post (there) suggests that the answer to both questions is “no”.
Hi there, thank you for joining the UDP party!
Yes, kirbah is correct on both points that the buffer size warning won’t affect your node’s in any way and currently you won’t see any load difference with UDP enabled.
The team is working on various UDP based protocols to hopefully improve our network performance. We will provide updates once we make more progress.
Thank you again for helping us to improve the network!
2 Likes
I’m assuming that by enabling UDP in docker that the satellites will be told/just see that I’ve got UDP enabled and take advantage of it when they’re ready, correct? I’ve made the changes in my docker run commands and also made sure both TCP/UDP are forwarded on my router, so everything should be ready. I haven’t pulled down and tested with the go script though.
You make me think that is better to test with the public ip and 1 of my nodes haven’t the udp port forwarded on the router and fails the test
1 Like
i ran into this same issue, i ended up changing the configuration on the docker host system which then fixed it in docker and the containers.
just ran this command on the host to change it.
sysctl -w net.core.rmem_max=2500000
@Yingrong also got my QUIC working now, didn’t bother with the test thing.
seemed rather convoluted for something that could be done from a website instead…
making it not needed to be installed literally ten thousand times, rather than just put up once on a website.
i got the double ping in logs and know i completed all the settings correctly, so that should be fine… 
1 Like
And where else did you want to do it?
On Pingdom there is an opportunity to check QUIC
2 Likes
You think it will be okay?
Until the next restart of the host, what about after restart?
So that the party goes well …
it is not possible for Storj / DCS to provide a test as it is done like:
http://storjnet.info/ping_my_node
???
2 Likes
as i understand it, then the -w is suppose to make it permanent and because you aren’t changing a config file, but running the sysctl command and not something like echo > or however that one looks… then the change on the system is immediate.
i did however do a
docker stop storagenode
docker start storagenode
and checked the log to see if it actually worked, not sure if rebooting the node is required, it might be, but i don’t really think so…
run the command on the host and it should be fine…
seemed to work for me anyways, no host or such reboot required.
thanks for this, that was so much easier…
you don’t really need anything more than what that site does…
Yeah finally. I was already about to ask someone else to ping my node because I was too lazy to compile it myself (and didn’t want to clutter my setup for it)
1 Like