Project

General

Profile

Actions
Copy link

Bug #7096

closed

Unbound fails to start on boot if specific network devices are configured in the "Network Interfaces"

Added by Chris Collins over 7 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
DNS Resolver
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.5-p1
Affected Architecture:

Description

It starts fine if default ALL is selected.

But if specific interfaces are selected instead it prints bind errors and will not start, this even happens if I put the commands right at end of rc.boot.

It starts fine from the GUI.

The first error I see in log is it reports it fails to bind to the wan ipv6 link-local address, the address it reports is not the same as the actual address on the interface, the last octect is changed. In addition the address is not selected in the "Network Interfaces" section and is correctly not binding to it when started from the dashboard.

The actual wan link local ends in d0e6 but it tries to use an address that ends in d0e5, I have no idea where it gets the d0e5 from.
I also see errors in the log where it fails to bind to the wan ipv4 address, again this is not selected.

The selected interfaces are LAN facing interfaces.

localhost
lan ipv6 link-local
LAN

It is perhaps not a coincidence it reports errors for interfaces that are deselected.

So either needs fixing or remove the option from the GUI to choose the interface, I will examine the scripts and post what I think is a fix if I find a way to fix myself.

Actions
Copy link

Also available in: Atom PDF