Project

General

Profile

Bug #4878

DHCP pools can be out of range causing DHCP server to exit

Added by Phillip Davis over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
DHCP Server
Target version:
Start date:
07/24/2015
Due date:
% Done:

0%

Estimated time:
Affected Version:
All
Affected Architecture:

Description

For example:
LAN 192.168.1.1/24 with DHCP pool 192.168.1.100-192.168.1.199 working fine.
OPT1 192.168.2.1/24 with DHCP pool 192.168.1.100-192.168.1.199 working fine.

Interfaces->OPT1 - edit the IP address to 192.168.3.1/24, Save and Apply (without going to the DHCP settings and fixing those.

The system makes a new dhcpd.conf that has OPT1 with DHCP pool outside of the OPT1 subnet.
dhcpd exits complaining about this.
Thus there is now no DHCP service on any interface, even though it is only OPT1 that has a dud configuration.

It would be nice if this user "accident" did not break DHCP for every interface on the system.

History

#2 Updated by Chris Buechler about 4 years ago

  • Status changed from New to Confirmed
  • Target version set to 2.2.5

#3 Updated by Phillip Davis about 4 years ago

Note: The eventual pull request for master was https://github.com/pfsense/pfsense/pull/1824
That was merged to master a couple of weeks ago.

For RELENG_2_2 this pull request is waiting to be merged:
https://github.com/pfsense/pfsense/pull/1836

#4 Updated by Renato Botelho about 4 years ago

  • Status changed from Confirmed to Feedback

Pull request has been merged. Thanks!

#5 Updated by Chris Buechler about 4 years ago

  • Status changed from Feedback to Resolved

this is fine with the exception of #5200 which we'll address there.

Also available in: Atom PDF