Project

General

Profile

Actions

Bug #9998

closed

DHCP6c and Unbound DNS Server Boot-Up Configuration Failure

Added by Eric Veum almost 2 years ago. Updated 9 months ago.

Status:
Resolved
Priority:
Normal
Category:
Interfaces
Target version:
Start date:
12/24/2019
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:
All

Description

When running my router with ‘Track Interface’ and dual IPv4/IPv6, using unbound as a local DNS server bound to only internal interfaces: LAN, LAN IPv6, and LAN IPv6 Link-Local, the DHCP6c service start-up is clobbering the FreeBSD kernels’ IPv6 auto link local LAN (​ net.inet6.ip6.auto_linklocal=1) ​ assignment over to a default address of fe80::1:1 ​and causing ubound DNS server to fail to startup for local service which still hold the original address in unbound.conf, and which it cannot ‘bind’
socket to, crashing on startup. Details in attached PDF writeup.


Files

pfSense - DHCP6c and Unbound Boot-up Configuration Failure.pdf (377 KB) pfSense - DHCP6c and Unbound Boot-up Configuration Failure.pdf DHCP6c and Unbound startup example failure, writeup Eric Veum, 12/24/2019 01:56 PM
etc_inc_interfaces_inc.patch (761 Bytes) etc_inc_interfaces_inc.patch Eric Veum, 01/13/2020 11:18 AM
Actions

Also available in: Atom PDF