Project

General

Profile

Actions

Feature #2622

closed

Allow DHCP without a range so that only static mappings may be used on an interface

Added by Aris Adamantiadis over 11 years ago. Updated over 3 years ago.

Status:
Needs Patch
Priority:
Normal
Assignee:
-
Category:
DHCP (IPv4)
Target version:
-
Start date:
09/05/2012
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

Hello,

I have a range managed by a DHCP server. All the hosts in this range have a static DHCP assignment.
Each time I was adding a new host, I had to change the pool size, ie. from x.x.x.90-x.x.x.93
Today, I have to allocate the last available IP address in the range, and there's no way:
-Static assignment cannot overlap with pool range
-Pool range cannot be outside interface's range/cannot be on the broadcast address)
-Pool range cannot be deactivated.

As a workaround, I will statically configure the IP address on the host.

I am using
2.1-BETA0 (amd64)
built on Wed Aug 15 08:43:33 EDT 2012
FreeBSD 8.3-RELEASE-p4

Suggested fix: allow the DHCP server to have no assigned pool, or allow static mappings to overlap.
(which definitively would make things easier to me since my procedure to allocate an IP is to boot the server, checkout the lease in the DHCP Lease view and make it static).

Thx,

Aris

Actions #1

Updated by Jim Pingle over 11 years ago

  • Tracker changed from Bug to Feature
  • Subject changed from DHCP static mapping not possible when the range is full to Allow DHCP without a range so that only static mappings may be used on an interface
  • Affected Version deleted (2.1-IPv6)

Not a bug, but a missing feature.

Allowing DHCP without a defined range would be the only feasible way to do this, essentially making it a static-only setup. That is assuming ISC-DHCPD allows this, which it may not.

Static mappings inside the range are not allowed for good reason:
http://doc.pfsense.org/index.php/Why_can%27t_I_have_static_mappings_inside_my_DHCP_range%3F

In the meantime, feel free to edit out the input validation that blocks the range check for static mappings, but be aware of the consequences mentioned on the wiki doc.

Actions #2

Updated by Aris Adamantiadis over 11 years ago

Hello,

Thanks for your response.
If I provide a patch and test this feature (dhcp without pool), is there any chance you'll merge it in ?

Thanks,

Aris

Actions #3

Updated by Jim Pingle over 11 years ago

Sure, we'd be open to including the patch.

Actions #4

Updated by Chris Buechler about 8 years ago

  • Category set to DHCP (IPv4)
Actions #5

Updated by Chris Buechler almost 8 years ago

  • Status changed from New to Needs Patch
Actions #6

Updated by B D over 3 years ago

+1

Actions

Also available in: Atom PDF