Opened 3 years ago

Closed 22 months ago

#5240 closed enhancement (complete)

ISC DHCP server config option site-option-space

Reported by: fdupont Owned by:
Priority: medium Milestone: ISC DHCP migration
Component: Unclassified Version: git
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DHCP Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


Note this is a discussion about this idea (which can be easily mapped when it is used once):

The site-option-space statement

site-option-space name ;

The site-option-space statement can be used to determine from what
option space site-local options will be taken. This can be used
in much the same way as the vendor-option-space statement. Site-
local options in DHCP are those options whose numeric codes are
greater than 224. These options are intended for site-specific
uses, but are frequently used by vendors of embedded hardware that
contains DHCP clients. Because site-specific options are allo-
cated on an ad hoc basis, it is quite possible that one vendor's
DHCP client might use the same option code that another vendor's
client uses, for different purposes. The site-option-space option
can be used to assign a different set of site-specific options for
each such vendor, using conditional evaluation (see dhcp-eval (5)
for details).

This is about multiple definitions in DHCPv4 option space for codes > 224.
On the output side it seems not to hard to do with a space aliasing feature limited to a known scope.
On the input side (which IMHO is more important) there is no way to unpack an option without knowing its definition so no definition or multiple definitions are the same: the only property is whether the option is present by its name or code...
See #5073 too for a similar (solved?) issue.
Note that ISC DHCP unpack packets but not options.


Change History (2)

comment:1 Changed 3 years ago by fdupont

  • Milestone changed from Kea-proposed to ISC DHCP migration

comment:2 Changed 22 months ago by fdupont

  • Resolution set to complete
  • Status changed from new to closed

Done by #5073.

Note: See TracTickets for help on using tickets.