search

opnsense / ports

OPNsense ports on top of FreeBSD
https://opnsense.org/
Other
157 stars 114 forks source link

Segmentation fault in Unbound 1.13.0 #111

Closed Tsuroerusu closed 3 years ago

Tsuroerusu commented 3 years ago

Important notices Before you add a new report, we ask you kindly to acknowledge the following:

[X] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md

[X] I have searched the existing issues and I'm convinced that mine is new.

Describe the bug A bug in Unbound causes it to crash with a segmentation fault which renders DNS resolution inoperable on the network. The bug is described here: https://github.com/NLnetLabs/unbound/issues/376

On the 17th of December, a fix for this was committed to the FreeBSD ports tree with version 1.13.0_1: https://svnweb.freebsd.org/ports/head/dns/unbound/?view=log

Personally, I think this is well worthy of a hotfix because today a client called me saying that his network was down and the cause was this bug.

I also saw it mention on the FreeBSD forums: https://forums.freebsd.org/threads/libunbound-error.78121/

To Reproduce I do not know precisely how to reproduce this. My client said it happened a few days ago and he rebooted his router, today it also happened at random. I checked his log file and I saw this error happening literally every second:

[69515:1] error: udp connect failed: No route to host for 2600:9000:5302:e300::1 port 53

Expected behavior Unbound not crashing.

Environment OPNsense 20.7.7_1 (amd64, LibreSSL).

fichtner commented 3 years ago

Whatever state is in FreeBSD ports first full week of January is going to be in 20.7.8. Threads in the forum with multiple workarounds regarding this already exist. My favourite scenario would be that 1.13.1 is released soon...

fichtner commented 3 years ago

1.13.0_1 is now part of 20.7.7. We will continue to monitor for newer Unbond versions but for now that will be everything we can possibly do.