Project

General

Profile

Feature #2774

Extend DHCP Pools code to allow using different subnets

Added by Jim Pingle over 7 years ago. Updated about 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
DHCP Server
Target version:
-
Start date:
01/23/2013
Due date:
% Done:

0%

Estimated time:

Description

The current DHCP pools code allows creating multiple ranges within the same large subnet. The ISC DHCP Daemon also supports using multiple subnets by declaring them as a "shared-network".

It should be possible to adapt the pools code to use that declaration when a pool is outside of the typical "LAN" range.

History

#1 Updated by Jim Pingle over 6 years ago

  • Target version changed from 2.2 to 2.3

#2 Updated by Chris Buechler over 5 years ago

  • Tracker changed from Bug to Feature
  • Priority changed from Very Low to Normal

#3 Updated by Chris Buechler about 5 years ago

  • Target version deleted (2.3)

#4 Updated by Steve Thomas almost 5 years ago

Is support for this no longer planned??

#5 Updated by Chris Buechler almost 5 years ago

Steve Thomas wrote:

Is support for this no longer planned??

Not likely for 2.3, maybe at some point. Not a very commonly needed feature, networks that need that usually have a separate DHCP server and the firewall's a DHCP relay.

#6 Updated by david stievenard about 4 years ago

The first time I used pfsense I was surprised to see that it can do dhcp relay but not the other side of the coin that is dhcp server recieving dhcp request from 3rd party dhcp relays.

Let me try to defend this feature :)

I build remotely small infrastructure with 10-50 users and it's composed with 5 elements firewall, l3 switch, access point, storage server micro server, virtualization micro server. It's a balance between squeezing as much computing power from the hardware (to keep it as cheap as possible) and separate roles onto different machines/VMs (so it's reliable/maintainable)

One practice I have is to keep 'unfiltered vlans' traffic routed directly on the l3-switch to avoid pulling up traffic to the firewall. For now I do dhcp services with a pfsense VM or with the l3-switch but this feature could allow me to centralize all dhcp services in one place with a nice GUI.

It's the same method I apply when I try avoid doing network filtering on the l3-switches or the servers...it's centralized on the firewall.

#7 Updated by Kill Bill about 4 years ago

@david: This functionality has been done at least 3 times by pfSense user (marcelloc), the code never got merged, so all that work went down the drain repeatedly. To conclude: this feature won't ever happen, there certainly must be some phobia wrt using pfSense as a DHCP server. All the details here: https://forum.pfsense.org/index.php?topic=65736.90

#8 Updated by Jim Pingle about 1 year ago

See also: #2323

Also available in: Atom PDF