Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
fusiondirectory-plugins
fusiondirectory-plugins
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 46
    • Issues 46
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • 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
  • fusiondirectory
  • fusiondirectory-pluginsfusiondirectory-plugins
  • Issues
  • #5249

Closed
Open
Opened Nov 17, 2016 by Prethorian@aspasojevicReporter

[DHCP] after migration from .16 to .17 there previous configurations are not migrated to new one automatically.

After migration there is no any definitions in DHCP section which should point to previous DHCP configurations.

Also when I add manually new options in DHCP section, after browsing with Apache Directory Studio I saw that on baseDN are created those options with DN = cn=optionname. Is it better to be like for DNS plugin? For DNS plugi there is ou=dns and inside are all zones. For DHCP options also should be stored in for example ou=dhcp for better management.

Thanks, Aleksandar

(from redmine: issue id 5249, created on 2016-11-17, closed on 2017-01-02)

  • Relations:
    • relates #5295 (closed)
  • Custom Fields:
    • Bug in version: 1.0.17
Assignee
Assign to
FusionDirectory 1.0.18
Milestone
FusionDirectory 1.0.18
Assign milestone
Time tracking
None
Due date
None
Reference: fusiondirectory/fd-plugins#5249