Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 563
    • Issues 563
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 70
    • Merge requests 70
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • KeaKea
  • Issues
  • #850
Closed
Open
Issue created Aug 21, 2019 by Marcin Siodelski@marcinDeveloper

Unable to set "interface" for a subnet via remote-subnet4-set when such interface is not present in the system

The cb_cmds uses Kea parsers to parse the subnet information received via commands. The parsers were initially designed to parse local Kea configuration files. The subnet parser, for example, checks whether the interface set for a subnet is present in the system. If it is not, it spits out an error similar to this:

[ { "result": 1, "text": "subnet configuration failed: Specified network interface name vboxnet0 for subnet 192.168.50.0/24 is not present in the system (:0:0)" } ]

This shouldn't be the case when setting the configuration via the CB, because a given server should be able to set the configuration for any DHCP server, not necessarily for itself.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking