Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unbound DNS Errors "Protocol Not Available" #8393

Open
2 tasks done
roblangston opened this issue Mar 3, 2025 · 2 comments
Open
2 tasks done

Unbound DNS Errors "Protocol Not Available" #8393

roblangston opened this issue Mar 3, 2025 · 2 comments
Labels
incomplete Issue template missing info

Comments

@roblangston
Copy link

roblangston commented Mar 3, 2025

Important notices

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

Describe the bug

I have a standard OPNSense install and since version 24.7, I receive hundreds of errors in the Unbound logs when unbound is enabled (see below). This happens in version 24.7, 24.10 and now 25.1.2. Due to this, I have used Dnsmasq instead but now require some features in Unbound.

2024-11-29T19:53:44 Error unbound [49173:2] error: recvfrom 45 failed: Protocol not available 2024-11-29T19:53:44 Error unbound [49173:2] error: recvfrom 46 failed: Protocol not available 2024-11-29T19:53:44 Error unbound [49173:2] error: recvfrom 45 failed: Protocol not available 2024-11-29T19:53:44 Error unbound [49173:2] error: recvfrom 46 failed: Protocol not available 2024-11-29T19:53:44 Error unbound [49173:2] error: recvfrom 45 failed: Protocol not available 2024-11-29T19:53:44 Error unbound [49173:2] error: recvfrom 46 failed: Protocol not available 2024-11-29T19:53:38 Error unbound [49173:0] error: recvfrom 35 failed: Protocol not available

To Reproduce

  • Log in to OPNSense
  • Enable Unbound Service
  • Under general settings enable "Register ISC DHCP4 Leases"
  • Under general settings enable "Register DHCP Static Mappings"
  • Wait 10-15 seconds and check the log file to see errors generated.

Expected behavior

Errors not to be generated in the log file.

Describe alternatives you considered

Switching to Dnsmasq. Updating OPNSense version (both revision and major versions).

Screenshots

Image

Image

Image

Image

Relevant log files

See attached unbound log file

resolver.log

Additional context

I opened a forum thread in November 2024 on the OPNSense forum which can be found here:-
https://forum.opnsense.org/index.php?topic=44353.0

Environment

OPNsense 25.1.2-amd64
FreeBSD 14.2-RELEASE-p2
OpenSSL 3.0.16

Hardware

Mini-PC with 4 x intel i226-V 2.5G NICs
Alder N100 CPU,

@OPNsense-bot
Copy link

Thank you for creating an issue.
Since the ticket doesn't seem to be using one of our templates, we're marking this issue as low priority until further notice.

For more information about the policies for this repository,
please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.

The easiest option to gain traction is to close this ticket and open a new one using one of our templates.

@OPNsense-bot OPNsense-bot added the incomplete Issue template missing info label Mar 3, 2025
@roblangston
Copy link
Author

I am not sure what the above means, the issue was created from the template.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
incomplete Issue template missing info
Development

No branches or pull requests

2 participants