simono41/docker-pihole-unbound
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Disable so-rcvbuf custom value (#166)

Browse source 
* Disable so-rcvbuf custom value

Using the default value is most of the time enough for a normal operation.

This removes an Unbound warning that complains about not having the requested 1m or more for kernel buffering.

* Corrected indentation

* Include additional information

Explained how to correctly enable so-rcvbuf.

Co-authored-by: burnbabyburn <xyz258@abwesend.de>

Co-authored-by: burnbabyburn <xyz258@abwesend.de>
This commit is contained in:
Xabi 2022-10-13 05:02:36 +00:00 committed by GitHub
parent ecee22c5f9
commit d60ebfcd7d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
one-container/pihole-unbound/unbound-pihole.conf
View file

@ -44,7 +44,8 @@ server:
num-threads: 1 num-threads: 1
# Ensure kernel buffer is large enough to not lose messages in traffic spikes # Ensure kernel buffer is large enough to not lose messages in traffic spikes
so-rcvbuf: 1m # Be aware that if enabled (requires CAP_NET_ADMIN or privileged), the kernel buffer must have the defined amount of memory, if not, a warning will be raised.
#so-rcvbuf: 1m
# Ensure privacy of local IP ranges # Ensure privacy of local IP ranges
private-address: 192.168.0.0/16 private-address: 192.168.0.0/16