From d60ebfcd7d81f5ac41ff0755fcba27b8f697fbc1 Mon Sep 17 00:00:00 2001 From: Xabi Date: Thu, 13 Oct 2022 05:02:36 +0000 Subject: [PATCH] Disable so-rcvbuf custom value (#166) * 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 Co-authored-by: burnbabyburn --- one-container/pihole-unbound/unbound-pihole.conf | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/one-container/pihole-unbound/unbound-pihole.conf b/one-container/pihole-unbound/unbound-pihole.conf index 43954d9..27769d9 100644 --- a/one-container/pihole-unbound/unbound-pihole.conf +++ b/one-container/pihole-unbound/unbound-pihole.conf @@ -44,7 +44,8 @@ server: num-threads: 1 # 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 private-address: 192.168.0.0/16