Project

General

Profile

Actions

Feature #4171

closed

Smart proxy DHCP plugin does not honor exclude ranges

Added by Laurent Domb over 10 years ago. Updated almost 8 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
DHCP
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Hi,

When adding a smart proxy runing on win2008 Server the smart proxy is not honoring dhcp exclude ranges. This results in foreman/smart-proxy (dhcp) running on m$ reserving ip addresses which should not be reserved. A workaround for now is to explicitly specify the start-stop address in the subnet tab.

I would expect if the start stop range is "optional" in the Provisioning-> subnets -> subnet TAB and not set by the user, that the smart proxy queries the address scope and also looks for excluded addresses. Otherwise what happens is that addresses get reserved even if they are exluded.

Here an example:

Excluded range in windows dhcp is 10.175.15.1 - 10.175.15.15. The fields start range stop range in the subnet tab are empty.

Add a new host, pick the subnet and let the smart-proxy negotiate an ip.

The smart proxy now tries to pick 10.175.15.1, .2, .3 as this ip is not reserved, just excluded.
-----------------------

What I would expect is if start stop address is not set: do

for each scope:

netsh dhcp server $SERVER scope $SCOPE show exluderange

Then if found an exluded range, calculate the start stop range.

Then get an ip.


Related issues 3 (1 open2 closed)

Related to Smart Proxy - Bug #7766: ms_native dhcp smart proxy code scales poorlyClosed10/01/2014Actions
Related to Smart Proxy - Feature #34105: Windows MS DHCP Scope and Exclusions not honoredNewActions
Is duplicate of Smart Proxy - Bug #1280: MS DHCP ignores address exclusionsResolvedActions
Actions

Also available in: Atom PDF