Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D dhcp
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 106
    • Issues 106
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • dhcp
  • Issues
  • #22

Closed
Open
Created Jun 13, 2019 by Chris@Tatsu-Kishi

[keama] dhcp4 option 67 wrong name

I used keama quite successfully to convert an existing ISC-dhcpd config to use as template (awesome work!), but came upon an incomplete conversion of dhcp4 option 67: bootfile-name

Kea config uses the name "boot-file-name", but keama outputs "bootfile-name".

isc-dhcpd source:

option bootfile-name "boot.pxe"

keama output:

"option-data": [
  {
    "space": "dhcp4",
    "name": "bootfile-name",
    "code": 67,
    "data": "boot.pxe"
  }
]

While discussions can (and maybe should) be held whether the kea name is "incorrect" in the first place (both RFC2132 and kea's own KB for supported options refer to it as "Bootfile Name") or should support both versions, the goal of keama is to create valid kea configs and should output "boot-file-name".

Assignee
Assign to
Time tracking