We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hey there,
I'm running into an issue on OpenBSD where I get the following output:
failed to increase receive buffer size (wanted: 2048 kiB, got 0 kiB). See https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size for details.
Unfortunately the linked documentation doesn't describe how to do so. Also, resources that I found (e.g. https://comp.unix.bsd.openbsd.misc.narkive.com/X8fbptCR/how-to-raise-the-maxsockbuf-in-openbsd) doesn't seem to provide a feasible solution to this.
Is there a way quic-go can circumvent this issue?
Thank you!
The text was updated successfully, but these errors were encountered:
I don’t have any experience with OpenBSD. A PR would be appreciated.
Sorry, something went wrong.
I've just tested this on OpenBSD 7.2 amd64 and have taken the following notes:
The correct sysctl to change is:
sysctl net.inet.udp.recvspace=...
While the maximum value supported by the kernel is 2147483647, resolving DNS hostnames via dig fails when the value is set beyond 2048000.
The maximum value doesn't seem to be affected by allocating more memory to the system (8GB vs 16GB available to the host at boot time).
No branches or pull requests
Hey there,
I'm running into an issue on OpenBSD where I get the following output:
Unfortunately the linked documentation doesn't describe how to do so. Also, resources that I found (e.g. https://comp.unix.bsd.openbsd.misc.narkive.com/X8fbptCR/how-to-raise-the-maxsockbuf-in-openbsd) doesn't seem to provide a feasible solution to this.
Is there a way quic-go can circumvent this issue?
Thank you!
The text was updated successfully, but these errors were encountered: