Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Kea
Kea
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 415
    • Issues 415
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 67
    • Merge Requests 67
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • KeaKea
  • Issues
  • #247

Closed
Open
Opened Nov 07, 2018 by Francis Dupont@fdupontDeveloper

ISC DHCP expression

ISC DHCP supports "expressions" of 3 types: boolean, data (string) and numeric (integer). They can be used for matching classes, set option values, etc.

Unfortunately this system is not fully consistent, for instance if you'd like to set an option to true:

option ip-forwarding = true;

This does not work because true is not a keyword and is parsed as a variable reference. As it is not set at runtime it will be evaluated as null so false...

If you try a constant true expression (aka tautology):

option ip-forwarding = 'foo' = 'foo';

In this case you specify a boolean expression when the system wants a data expression so refused this attempt at parsing time.

Note it is worse for integers, in:

option default-ip-ttl = 12;

the 12 is in hexadecimal so in fact is 18... If you want a decimal value you need a context where a number is expected.

Cf KB references:

​https://kb.isc.org/article/AA-00334/56/Do-the-list-of-parameters-in-the-dhcp-parameter-request-list-need-to-be-in-hex.html

and about inconsistencies in output/display:

​https://kb.isc.org/article/AA-01039/56/Formatting-MAC-addresses-in-dhcpd-or-why-does-binary-to-ascii-strip-leading-zeroes.html

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
ISC DHCP Migration
Milestone
ISC DHCP Migration
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/kea#247