starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Control ISC DHCP server with Netbox #1719

New Issue
Closed
opened 2025-12-29 16:34:42 +01:00 by adam · 3 comments
adam commented 2025-12-29 16:34:42 +01:00
Owner
Copy Link

Originally created by @jdemilledt on GitHub (May 9, 2018).

Issue type

[x] Feature request
[ ] Bug report
[ ] Documentation

Description

Functionality to add leases to DHCP based on IPAM addresses (and vice versa if possible)
This would be used to manage dynamic (or static leased) IP addresses from Netbox.
I'm unsure about needed changes for the schema or libraries.

Originally created by @jdemilledt on GitHub (May 9, 2018). <!-- Before opening a new issue, please search through the existing issues to see if your topic has already been addressed. Note that you may need to remove the "is:open" filter from the search bar to include closed issues. Check the appropriate type for your issue below by placing an x between the brackets. For assistance with installation issues, or for any other issues other than those listed below, please raise your topic for discussion on our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please note that issues which do not fall under any of the below categories will be closed. Due to an excessive backlog of feature requests, we are not currently accepting any proposals which extend NetBox's feature scope. Do not prepend any sort of tag to your issue's title. An administrator will review your issue and assign labels as appropriate. ---> ### Issue type [x] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> ### Description Functionality to add leases to DHCP based on IPAM addresses (and vice versa if possible) This would be used to manage dynamic (or static leased) IP addresses from Netbox. I'm unsure about needed changes for the schema or libraries.
adam closed this issue 2025-12-29 16:34:42 +01:00
adam commented 2025-12-29 16:34:43 +01:00
Author
Owner
Copy Link

@mdlayher commented on GitHub (May 9, 2018):

Hello, I'm not the maintainer of netbox, but I can assure you that such an integration would be outside the scope of netbox itself. There isn't a feasible way to integrate netbox directly with the large variety of systems that exist in the wild.

Your best bet is going to be to create an external component using the API, and integrate that with ISC dhcpd.

@mdlayher commented on GitHub (May 9, 2018): Hello, I'm not the maintainer of netbox, but I can assure you that such an integration would be outside the scope of netbox itself. There isn't a feasible way to integrate netbox directly with the large variety of systems that exist in the wild. Your best bet is going to be to create an external component using the API, and integrate that with ISC dhcpd.
adam commented 2025-12-29 16:34:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 11, 2018):

Just echoing what @mdlayher said: You'll need some layer of logic between NetBox and your DHCP server to automatically populate leases. It might be possible to accomplish what you want by writing a custom export template for IP addresses in NetBox, but I'm not sure what your end goal is.

@jeremystretch commented on GitHub (May 11, 2018): Just echoing what @mdlayher said: You'll need some layer of logic between NetBox and your DHCP server to automatically populate leases. It might be possible to accomplish what you want by writing a custom export template for IP addresses in NetBox, but I'm not sure what your end goal is.
adam commented 2025-12-29 16:34:43 +01:00
Author
Owner
Copy Link

@fusmu commented on GitHub (Dec 3, 2019):

I know it's a old thread but it's maybe the only one related to this.
Few months ago I've faced same scenario we have legacy isc-dhcpd box running on freebsd and something like 3000 hosts(servers, IoT devices, pxe, users) so we need something to manage it. What I did is what jeremystretch says, I write middle-layer logic that read Netbox DB and parse it as dhcpd config. What I modify in netobx was only IPAM app and forms related to it:

  • Added MAC address field for each IP
  • Implement some logic if the address is in use/free/dhcp or pxe
  • writing small python script that fetch records that are related to DHCP and parse them as isc-dhcpd config
  • modify IPAM save form to trigger that script on saving/editing new IP

Currently we're using it for several months without an issue.
Once again I'm sorry that i'm rising this thread from dust but maybe someone could find this useful, if you have any questions do not hesitate to contact me.

@fusmu commented on GitHub (Dec 3, 2019): I know it's a old thread but it's maybe the only one related to this. Few months ago I've faced same scenario we have legacy isc-dhcpd box running on freebsd and something like 3000 hosts(servers, IoT devices, pxe, users) so we need something to manage it. What I did is what jeremystretch says, I write middle-layer logic that read Netbox DB and parse it as dhcpd config. What I modify in netobx was only IPAM app and forms related to it: - Added MAC address field for each IP - Implement some logic if the address is in use/free/dhcp or pxe - writing small python script that fetch records that are related to DHCP and parse them as isc-dhcpd config - modify IPAM save form to trigger that script on saving/editing new IP Currently we're using it for several months without an issue. Once again I'm sorry that i'm rising this thread from dust but maybe someone could find this useful, if you have any questions do not hesitate to contact me.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1719
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?