Project

General

Profile

Actions
Copy link

Bug #11087

closed

Unbound fails to start if it binds to down/nocarrier interface

Added by Viktor Gurov about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Viktor Gurov
Category:
DNS Resolver
Target version:
2.5.0
Start date:
11/20/2020
Due date:
% Done:

100%

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

Description

How to reproduce:
1) Select OPT1 for example, in "Network Interfaces" list;
2) Disable OPT1 interface;
3) Reboot firewall (or receive new WAN ip);
4) Result:

Nov 20 15:22:43 pf41 php-fpm[344]: /system_routes.php: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1605874963] unbound[18329:0] error: can't bind socket: Can't assign requested address for 172.16.0.1 port 53 [1605874963] unbound[18329:0] fatal error: could not open ports'

Workaround:
Services / DNS Resolver -> save + apply

Actions
Copy link
 #2

Updated by Jim Pingle about 4 years ago

  • Status changed from New to Pull Request Review
  • Assignee set to Viktor Gurov
  • Target version set to 2.5.0
Actions
Copy link
 #3

Updated by Renato Botelho about 4 years ago

  • Status changed from Pull Request Review to Feedback

PR has been merged. Thanks!

Actions
Copy link
 #4

Updated by Viktor Gurov about 4 years ago

  • % Done changed from 0 to 100
Actions
Copy link
 #5

Updated by Danilo Zrenjanin about 4 years ago

  • Status changed from Feedback to Resolved

Replicated the issue on 2.4.5-p1.

Re-tested on:

2.5.0-DEVELOPMENT (amd64)
built on Wed Nov 25 07:03:07 EST 2020
FreeBSD 12.2-STABLE

It works fine. Ticket resolved.

Actions
Copy link

Also available in: Atom PDF