Project

General

Profile

Feature #17856

SmartProxy should support multiple dhcp reservations for the same ip address

Added by Timo Goebel almost 4 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
DHCP
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Smart Proxy should support multiple dhcp records for the same ip address to support bonded interfaces. Cobbler already supports this.

It should be possible to deploy two dhcp reservations for a single nic.
The ipaddress and hostnames should be the same, the macs and names should differ.

Conflict detection should not mark these records as a conflict.


Related issues

Related to Foreman - Feature #17533: Using a bonded interface as provision interface should provision DHCP for all child macs as wellClosed
Related to Smart Proxy - Feature #18069: Add ip and mac address validations to api endpoints in dhcp api controllerNew2017-01-13
Related to Smart Proxy - Bug #18070: When adding a new dhcp reservation, ip and mac addresses should be checked not only against existing reservations but leases as wellClosed2017-01-13
Related to Smart Proxy - Feature #18071: Handling of removal of non-existing record by dhcp provider should be the same across all providersClosed2017-01-13
Related to Smart Proxy - Refactor #18072: Defer to dhcp providers for their intialization.Closed2017-01-13
Related to Foreman - Refactor #19295: Use new proxy API for getting information from DHCPClosed2017-04-18
Related to Smart Proxy - Bug #19599: DHCP reservation deletion returns "null" stringClosed2017-05-19

Associated revisions

Revision c7aa35f0 (diff)
Added by Timo Goebel almost 4 years ago

fixes #17856 - support multiple dhcp records for same ip

History

#1 Updated by Timo Goebel almost 4 years ago

  • Related to Feature #17533: Using a bonded interface as provision interface should provision DHCP for all child macs as well added

#2 Updated by Dmitri Dolguikh almost 4 years ago

There's a chance that it might be possible with ISC dhcpd when 'option dhcp-client-identifier' is used to explicitly set client ids, but it needs to be checked (it also doesn't apply to most setups, as not all eherhnet switches support forwarding of custom client ids). I don't think this is possible with MS dhcp at all (but also needs to be verified).

#3 Updated by The Foreman Bot almost 4 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/smart-proxy/pull/485 added

#4 Updated by Timo Goebel almost 4 years ago

Dmitri Dolguikh wrote:

There's a chance that it might be possible with ISC dhcpd when 'option dhcp-client-identifier' is used to explicitly set client ids, but it needs to be checked (it also doesn't apply to most setups, as not all eherhnet switches support forwarding of custom client ids). I don't think this is possible with MS dhcp at all (but also needs to be verified).

Dimitri, what do you want to gain from the client id? I believe (and tests indicate that as well and cobbler does it in a similar way) that it's enough to deploy to reservations and make the checking for duplicates/conflicts more intelligent. I'd have foreman send a white list of mac addresses and filter the duplicates by them. Should work, I guess.

#5 Updated by Timo Goebel almost 4 years ago

  • Subject changed from SmartProxy should support multiple dhcp records for the same ip address to SmartProxy should support multiple dhcp reservations for the same ip address

#6 Updated by Dmitri Dolguikh almost 4 years ago

  • Related to Feature #18069: Add ip and mac address validations to api endpoints in dhcp api controller added

#7 Updated by Dmitri Dolguikh almost 4 years ago

  • Related to Bug #18070: When adding a new dhcp reservation, ip and mac addresses should be checked not only against existing reservations but leases as well added

#8 Updated by Dmitri Dolguikh almost 4 years ago

  • Related to Feature #18071: Handling of removal of non-existing record by dhcp provider should be the same across all providers added

#9 Updated by Dmitri Dolguikh almost 4 years ago

  • Related to Refactor #18072: Defer to dhcp providers for their intialization. added

#10 Updated by Anonymous almost 4 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#11 Updated by Dominic Cleal almost 4 years ago

  • Legacy Backlogs Release (now unused) set to 209

#12 Updated by Marek Hulán over 3 years ago

  • Related to Refactor #19295: Use new proxy API for getting information from DHCP added

#13 Updated by Dominic Cleal over 3 years ago

  • Related to Bug #19599: DHCP reservation deletion returns "null" string added

Also available in: Atom PDF