Bug #1280
closed
MS DHCP ignores address exclusions
Added by Corey Osman about 13 years ago.
Updated about 5 years ago.
Description
I have the following set in my MS DHCP scope
Address range 192.168.1.1 - 192.168.1.254
Address Excluded Range: 192.168.1.1 - 192.168.1.150
Address Excluded Range: 192.168.1.200 - 192.168.1.254
However, when foreman makes a request to get an IP it returns an IP from the range without considering the excluded ranges.
So when an IP of 192.168.1.1 is returned via the dhcp smart-proxy it will conflict with another IP
Files
We can get the excluded ranges by using the following command:
netsh dhcp server 192.168.1.1 scope 192.168.1.0 show excluderange
yep, imho ms dhcp should be queried via the netsh dump command instead of individual netsh commands.
- Category set to DHCP
- Target version set to 0.3
- Target version changed from 0.3 to 1.0
is it scope reservations range, or scope range in general? I think there is a difference between when a scope enables dynamic guests (e.g. with no reservation) vs. this IP's are out of the DHCP server range.
Foreman currently picks an ip that is part of the scope but is also part of an excluded range. Because the IP is part of the excluded range there could be IP conflicts.
- Target version deleted (
1.0)
- Has duplicate Feature #4171: Smart proxy DHCP plugin does not honor exclude ranges added
- Related to Bug #7766: ms_native dhcp smart proxy code scales poorly added
- Description updated (diff)
- Status changed from New to Resolved
This has been fixed in Ms dhcp provider on Windows Server 2012 platform (please note there won't be a fix for Windows Server 2008). Marking this as resolved.
- Fixed in Releases 1.24.0 added
Hi,
sorry this problem still exists even on Windows 2012 R2. We are running Foreman 1.22.1 (Katello 3.12). DHCP exclusions are not honored when creating hosts.
Best Regards,
Oliver
- Found in Releases 1.22.1 added
- Fixed in Releases deleted (
1.24.0)
Oliver, could you please open a new bug with the details of the issue you are seeing and mark it as related to this one? it may be that the symptoms are similar but the cause is different than the original issue.
- Related to Feature #34105: Windows MS DHCP Scope and Exclusions not honored added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by Anonymous 
Updated by 
Updated by