Le Sun, Oct 12, 2025 at 11:19:43AM +0100, Stuart Henderson a écrit : > On 2025/10/12 11:08, Landry Breuil wrote: > > hi, > > > > found while deploying a new unbound on 7.8, at startup it warns loudly > > about the so-sndbuf default: > > > > [1760258776] unbound[40302:0] warning: setsockopt(..., SO_SNDBUF, ...) was > > not granted: No buffer space available > > [1760258776] unbound[40302:0] warning: so-sndbuf 4194304 was not granted. > > Got 9216. To fix: start with root permissions(linux) or sysctl bigger > > net.core.wmem_max(linux) or kern.ipc.maxsockbuf(bsd) values. or set > > so-sndbuf: 0 (use system value). > > [1760258776] unbound[40302:0] warning: setsockopt(..., SO_SNDBUF, ...) was > > not granted: No buffer space available > > [1760258776] unbound[40302:0] warning: so-sndbuf 4194304 was not granted. > > Got 9216. To fix: start with root permissions(linux) or sysctl bigger > > net.core.wmem_max(linux) or kern.ipc.maxsockbuf(bsd) values. or set > > so-sndbuf: 0 (use system value). > > hmm, that's printed a lot of times! I suppose you've configured it > to run many instances (num-threads).
i think i use the default, and i see 6 msgs :) > Not noticed here because I don't normally use rcctl -d to start daemons, > and it doesn't show in syslog. yeah i only saw it because it didnt start for other reasons and i used -d. > > should we set so-sndbuf to 0 in the default shipped config, change the > > default in the code, silence the warnings ? > > perhaps this. that looks sensible. > (My busier instances are not in the same subnet as clients so I wouldn't > usually see many effects from lladdr resolution times here. I expect > the worst case is when you have unbound on the same subnet as a > lot of wifi clients). (dunno i that matters but that's more or less my case, unbound listening on wifi/voip/lan subnets with /24 each, and quite a bunch of wifi clients)
