Feature #17856
closed
SmartProxy should support multiple dhcp reservations for the same ip address
Added by Timo Goebel about 8 years ago.
Updated over 6 years ago.
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 to Feature #17533: Using a bonded interface as provision interface should provision DHCP for all child macs as well added
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).
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/smart-proxy/pull/485 added
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.
- 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
- Related to Feature #18069: Add ip and mac address validations to api endpoints in dhcp api controller added
- 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
- Related to Feature #18071: Handling of removal of non-existing record by dhcp provider should be the same across all providers added
- Related to Refactor #18072: Defer to dhcp providers for their intialization. added
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Translation missing: en.field_release set to 209
- Related to Refactor #19295: Use new proxy API for getting information from DHCP added
- Related to Bug #19599: DHCP reservation deletion returns "null" string added
Also available in: Atom
PDF