Actions
Bug #11087
closedUnbound fails to start if it binds to down/nocarrier interface
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
Updated by Viktor Gurov almost 4 years ago
Updated by Jim Pingle almost 4 years ago
- Status changed from New to Pull Request Review
- Assignee set to Viktor Gurov
- Target version set to 2.5.0
Updated by Renato Botelho almost 4 years ago
- Status changed from Pull Request Review to Feedback
PR has been merged. Thanks!
Updated by Viktor Gurov almost 4 years ago
- % Done changed from 0 to 100
Applied in changeset e65b646f30245863571f8b99e8b08c4d8a595e0d.
Updated by Danilo Zrenjanin almost 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