Project

General

Profile

Actions
Copy link

Bug #1280

closed

MS DHCP ignores address exclusions

Added by Corey Osman about 13 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
DHCP
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Foreman - 1.22.1
Red Hat JIRA:

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

Screen_Shot_2011-10-31_at_6.28.10_PM.png View Screen_Shot_2011-10-31_at_6.28.10_PM.png 42.5 KB Corey Osman, 10/31/2011 09:35 PM

Related issues 3 (1 open — 2 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
Has duplicate Smart Proxy - Feature #4171: Smart proxy DHCP plugin does not honor exclude ranges Duplicate01/23/2014Actions
Actions
Copy link
 #1

Updated by Corey Osman about 13 years ago

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

Actions
Copy link
 #2

Updated by Ohad Levy about 13 years ago

yep, imho ms dhcp should be queried via the netsh dump command instead of individual netsh commands.

Actions
Copy link
 #3

Updated by Corey Osman about 13 years ago

  • Category set to DHCP
  • Target version set to 0.3
Actions
Copy link
 #4

Updated by Ohad Levy about 13 years ago

  • Target version changed from 0.3 to 1.0
Actions
Copy link
 #5

Updated by Ohad Levy almost 13 years ago

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.

Actions
Copy link
 #6

Updated by Corey Osman almost 13 years ago

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.

Actions
Copy link
 #7

Updated by Ohad Levy over 12 years ago

  • Target version deleted (1.0)
Actions
Copy link
 #8

Updated by Dominic Cleal over 10 years ago

  • Has duplicate Feature #4171: Smart proxy DHCP plugin does not honor exclude ranges added
Actions
Copy link
 #9

Updated by Dominic Cleal over 8 years ago

  • Related to Bug #7766: ms_native dhcp smart proxy code scales poorly added
Actions
Copy link
 #10

Updated by Anonymous about 8 years ago

  • 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.

Actions
Copy link
 #11

Updated by Oliver Weinmann about 5 years ago

  • 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

Actions
Copy link
 #12

Updated by Oliver Weinmann about 5 years ago

  • Found in Releases 1.22.1 added
Actions
Copy link
 #13

Updated by Tomer Brisker about 5 years ago

  • Fixed in Releases deleted (1.24.0)
Actions
Copy link
 #14

Updated by Tomer Brisker about 5 years ago

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.

Actions
Copy link
 #15

Updated by Oliver Weinmann about 3 years ago

  • Related to Feature #34105: Windows MS DHCP Scope and Exclusions not honored added
Actions
Copy link

Also available in: Atom PDF