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

IPAM Role #5657

New Issue
Closed
opened 2025-12-29 19:30:44 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:30:44 +01:00
Owner
Copy Link

Originally created by @WizCraker on GitHub (Nov 12, 2021).

NetBox version

3.0.10

Feature type

Change to existing functionality

Proposed functionality

I was checking out the beta demo and noticed the roles for the IP addressing in the IPAM doesn't have Multicast. since the Help documentation says roles cannot be user defined anyway you could add Multicast as one of the standard roles?

Use case

I have been looking for a solution for keeping track of our Video Multicast addresses which are used for video broadcast sources for our IPTV & OTT services to our headend. NetBox looks like the perfect solution as it looks like in addition to the IPAM it will help us also keep track of our server and broadcasting infrastructure.

It is a complete nightmare trying to keep track of multicast addresses in an organized fashion when dealing with hundreds of different broadcast sources (aka TV channels) which are either packaged in individual multicast (one-to-one) or multiple channels packaged inside of a single multicast. We are currently using spread sheets which you can imagine is a nightmare way to keep track of data since spread sheets is where data goes to die. :)

Database changes

No response

External dependencies

No response

Originally created by @WizCraker on GitHub (Nov 12, 2021). ### NetBox version 3.0.10 ### Feature type Change to existing functionality ### Proposed functionality I was checking out the beta demo and noticed the roles for the IP addressing in the IPAM doesn't have Multicast. since the Help documentation says roles cannot be user defined anyway you could add Multicast as one of the standard roles? ### Use case I have been looking for a solution for keeping track of our Video Multicast addresses which are used for video broadcast sources for our IPTV & OTT services to our headend. NetBox looks like the perfect solution as it looks like in addition to the IPAM it will help us also keep track of our server and broadcasting infrastructure. It is a complete nightmare trying to keep track of multicast addresses in an organized fashion when dealing with hundreds of different broadcast sources (aka TV channels) which are either packaged in individual multicast (one-to-one) or multiple channels packaged inside of a single multicast. We are currently using spread sheets which you can imagine is a nightmare way to keep track of data since spread sheets is where data goes to die. :) ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:30:44 +01:00
adam closed this issue 2025-12-29 19:30:44 +01:00
adam commented 2025-12-29 19:30:44 +01:00
Author
Owner
Copy Link

@zombah commented on GitHub (Nov 14, 2021):

Are you sure multicast role alone will add any more flexibility for multicast documenting?
There are ASM Multicast which is possible as Point-2-MultiPoint between
one source ip address and many destination addresses and SSM Multicast which is P2MP
between one destination ip and many source ip addresses, so even for alot addresses
with Multicast role you will need to connect them with f.e. tag's of channel names and
tag's of source operator and etc.
Myself i segment them with different tags now.
So it sounds like multicast is good target for plugin which can add P2MP or
even MP2MP relations between ip addresses and add channel names to
these groups and associate them with operator, reciever's tenants and etc.

@zombah commented on GitHub (Nov 14, 2021): Are you sure multicast role alone will add any more flexibility for multicast documenting? There are ASM Multicast which is possible as Point-2-MultiPoint between one source ip address and many destination addresses and SSM Multicast which is P2MP between one destination ip and many source ip addresses, so even for alot addresses with Multicast role you will need to connect them with f.e. tag's of channel names and tag's of source operator and etc. Myself i segment them with different tags now. So it sounds like multicast is good target for plugin which can add P2MP or even MP2MP relations between ip addresses and add channel names to these groups and associate them with operator, reciever's tenants and etc.
adam commented 2025-12-29 19:30:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 15, 2021):

Multicast status is a function of the address itself; IP addresses within certain prefixes are designated multicast address by standards (i.e. RFC 5771). These are not user-configurable, which is why there is no "multicast" role in NetBox.

@jeremystretch commented on GitHub (Nov 15, 2021): Multicast status is a function of the address itself; IP addresses within certain prefixes are designated multicast address by standards (i.e. [RFC 5771](https://datatracker.ietf.org/doc/html/rfc5771)). These are not user-configurable, which is why there is no "multicast" role in NetBox.
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#5657
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?