Project

General

Profile

Actions

Bug #749

closed

Dhcpd range value not used?

Added by Arnaud Sourioux almost 14 years ago. Updated almost 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Smart Proxy
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

I set a smart proxy to manage my dhcpd
but when it tries to find an ip for my hosts,
the IPs aren't in the range I selected for my dhcpd
they always begin at xxx.xxx.xxx.2 and are incremented by one

I tried to set the range value thoses ways :
xxx.xxx.xxx.20-xxx.xxx.xxx.50
xxx.xxx.xxx.20 xxx.xxx.xxx.50
xxx.xxx.xxx.20;xxx.xxx.xxx.50
xxx.xxx.xxx.20,xxx.xxx.xxx.50
20-50

but it hasn't change anything


Related issues 1 (0 open1 closed)

Is duplicate of Smart Proxy - Bug #884: IP proposed during Host creation does not belong to IP range defined in the subnetClosedOhad Levy05/06/2011Actions
Actions #1

Updated by D. Johnson over 13 years ago

Few small items:

Smart-proxy knows how to read the range from dhcpd.conf, but does not convey that information back up to foreman.

Foreman might allocate new host IP values within the range above, ordered by last-reporting date. (This way, allocated hosts that do not respond to pings would still be at the end of the queue, and hosts that respond are not in the available pool at all)

Unmanaged hosts that are ping-able should not come up as a default-IP. (Avoid clobbering with printers, routers, etc..)

Actions #2

Updated by Ohad Levy almost 13 years ago

  • Status changed from New to Closed

Applied in changeset commit:"440a88a9322e8c9f601c81ecc4993b82e1f1d8b3".

Actions

Also available in: Atom PDF