Feature #14731
closed
Unbound Advanced Settings entry for ``sock-queue-timeout``
Added by Marcos M 9 months ago.
Updated 7 months ago.
Plus Target Version:
23.09
Description
sock-queue-timeout was introduced in unbound 1.18.0.
https://unbound.docs.nlnetlabs.nl/en/latest/manpages/unbound.conf.html
UDP queries that have waited in the socket buffer for a long time can be dropped. The time is set in seconds, 3 could be a good value to ignore old queries that likely the client does not need a reply for any more. This could happen if the host has not been able to service the queries for a while, i.e. Unbound is not running, and then is enabled again. It uses timestamp socket options. Default: 0 (disabled)
Before the feature can be implemented, the port will need to be updated upstream then pulled.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273456
- Description updated (diff)
- Status changed from New to Waiting on Merge
- Parent task set to #14732
suggest changing the description on this to include "Unbound"
- Subject changed from Add the option ``sock-queue-timeout`` to the Advanced Settings GUI to Add the option ``sock-queue-timeout`` to the Unbound Advanced Settings GUI
- Status changed from Waiting on Merge to Pull Request Review
- Target version set to CE-Next
- Plus Target Version set to 23.09
Unbound has now been updated to 1.18.0, this is now ready to land
- Parent task deleted (
#14732)
Changed from a subtask to "follows" otherwise this would prevent us from closing the Unbound update task until this was also closed, and it isn't a hard requirement.
- Status changed from Pull Request Review to Feedback
- % Done changed from 0 to 100
- Subject changed from Add the option ``sock-queue-timeout`` to the Unbound Advanced Settings GUI to Unbound Advanced Settings entry for ``sock-queue-timeout``
- Target version changed from CE-Next to 2.8.0
Updating subject for release notes.
- Status changed from Feedback to New
If you remove the value from the field so it's blank, then save, the config it generates is not valid and unbound won't start.
The config.xml entry looks like:
<sock_queue_timeout></sock_queue_timeout>
The unbound.conf file ends up with the following line:
sock-queue-timeout:
Manually entering a value of 0 allows it to start and run.
- Status changed from New to Feedback
- Status changed from Feedback to Resolved
An empty value now defaults to 0 as expected.
- Target version changed from 2.8.0 to 2.7.1
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by