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

MAC Address tracking for virtual machines #7367

New Issue
Closed
opened 2025-12-29 20:22:24 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:22:24 +01:00
Owner
Copy Link

Originally created by @dutchman80 on GitHub (Dec 16, 2022).

NetBox version

v3.4

Feature type

Data model extension

Proposed functionality

Add a MAC Address tracker to the Virtualization section, and allow MAC Addresses to be associated with individual VMs

Use case

VMware (and perhaps others virtualization platforms?) have a range of MAC addresses that you can statically assign to VMs. This is very useful when using a VM with RLM or FlexLM licensed software (where the MAC address is what's used to generate the licenses), as you can perpetually reserve a specific MAC for a specific software license. I see this operating exactly like the Static IP list in the IPAM section.

Database changes

No response

External dependencies

No response

Originally created by @dutchman80 on GitHub (Dec 16, 2022). ### NetBox version v3.4 ### Feature type Data model extension ### Proposed functionality Add a MAC Address tracker to the Virtualization section, and allow MAC Addresses to be associated with individual VMs ### Use case VMware (and perhaps others virtualization platforms?) have a range of MAC addresses that you can statically assign to VMs. This is very useful when using a VM with RLM or FlexLM licensed software (where the MAC address is what's used to generate the licenses), as you can perpetually reserve a specific MAC for a specific software license. I see this operating exactly like the Static IP list in the IPAM section. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:22:24 +01:00
adam closed this issue 2025-12-29 20:22:24 +01:00
adam commented 2025-12-29 20:22:25 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Dec 16, 2022):

I'm not sure I understand here. You can already specify the MAC address on VM interfaces. I know very little about vmware, but I'm not sure I see how assigning a MAC address to the vm itself makes sense. Could you elaborate on your proposal?

@kkthxbye-code commented on GitHub (Dec 16, 2022): I'm not sure I understand here. You can already specify the MAC address on VM interfaces. I know very little about vmware, but I'm not sure I see how assigning a MAC address to the vm itself makes sense. Could you elaborate on your proposal?
adam commented 2025-12-29 20:22:25 +01:00
Author
Owner
Copy Link

@dutchman80 commented on GitHub (Dec 16, 2022):

You're right, I meant to say "assign to interface". To clarify, I'd like to be able to break out MAC address management to separate pages. So, just like IPAM, I'd like to be able to define a MAC Address range (i.e. 00:50:56:00:00:00 - 00:50:56:3F:FF:FF) and then have a list of MACs to assign, mark as Reserved, etc.

@dutchman80 commented on GitHub (Dec 16, 2022): You're right, I meant to say "assign to interface". To clarify, I'd like to be able to break out MAC address management to separate pages. So, just like IPAM, I'd like to be able to define a MAC Address range (i.e. 00:50:56:00:00:00 - 00:50:56:3F:FF:FF) and then have a list of MACs to assign, mark as Reserved, etc.
adam commented 2025-12-29 20:22:25 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Dec 18, 2022):

This seems like a fairly rare usecase and I really don't see IP addresses and MAC addresses as comparable. While MAC's are assignable to some degree, they are really intended as hardware addresses.

I recommend that you implement this as a plugin as this is not something likely to be included in core netbox.

@kkthxbye-code commented on GitHub (Dec 18, 2022): This seems like a fairly rare usecase and I really don't see IP addresses and MAC addresses as comparable. While MAC's are assignable to some degree, they are really intended as hardware addresses. I recommend that you implement this as a plugin as this is not something likely to be included in core netbox.
adam commented 2025-12-29 20:22:26 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 25, 2024):

This will likely be addressed by FR #4867.

@jeremystretch commented on GitHub (Oct 25, 2024): This will likely be addressed by FR #4867.
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 type: feature
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#7367
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?