Project

General

Profile

Actions
Copy link

Bug #13019

closed

Setting an NTP FQDN kills DHCP Server

Added by Kristopher Kolpin about 2 years ago. Updated about 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
DHCP (IPv4)
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.6.0
Affected Architecture:
amd64

Description

Very strange issue here. Setting a FQDN for one of the 3 NTP server options in the IPv4 DHCP server settings kills IP address assignment functions. I've started from a fresh pfSense system twice now so this issue is very reproducible.

How to reproduce:

1) Go to DHCP server setting for a VLAN (didn't test non-VLAN interface) and set reserve an IP address for a client
2) set "ca.pool.ntp.org" for NTP1
3) set "pool.ntp.org" for NTP2
4) Save settings
5) Observe that client never gets the assigned IP address. An ARP entry hangs around but is always incomplete. Sometimes letting DHCP server assign from a pool works but only after 30-60 seconds. Some clients give up quicker than other so you may get mixed results.

Actions
Copy link

Also available in: Atom PDF