Add support for TCP6 and UDP6 protocols in service templates and services #7855

Closed
opened 2025-12-29 20:29:04 +01:00 by adam · 4 comments
Owner

Originally created by @Sow1995 on GitHub (Apr 4, 2023).

NetBox version

v3.4.7

Feature type

Data model extension

Proposed functionality

TCP6 and UDP6 are not available in the protocol dropdown when creating a service.

It's proposed to add UDP6 and TCP6 to the protocols list

Use case

Currently it is not possible to add TCP6 and UDP6 connections to services. Being able to add services that use the TCP6 and/or UDP6 protocol makes it possible to distinguish between the two when adding a service that has both an IPv4 and a IPv6 connection.

Database changes

No response

External dependencies

No response

Originally created by @Sow1995 on GitHub (Apr 4, 2023). ### NetBox version v3.4.7 ### Feature type Data model extension ### Proposed functionality TCP6 and UDP6 are not available in the protocol dropdown when creating a service. It's proposed to add UDP6 and TCP6 to the protocols list ### Use case Currently it is not possible to add TCP6 and UDP6 connections to services. Being able to add services that use the TCP6 and/or UDP6 protocol makes it possible to distinguish between the two when adding a service that has both an IPv4 and a IPv6 connection. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:29:04 +01:00
adam closed this issue 2025-12-29 20:29:04 +01:00
Author
Owner

@Sow1995 commented on GitHub (Apr 4, 2023):

I can provide a PR as well, if/when this has been approved.

@Sow1995 commented on GitHub (Apr 4, 2023): I can provide a PR as well, if/when this has been approved.
Author
Owner

@jeremystretch commented on GitHub (Apr 4, 2023):

TCP6 and UDP6 aren't actual protocols. Rather, they're just shorthand used by some applications to imply that a port is bound to an IPv6 address (which can already be modeled explicitly in NetBox).

@jeremystretch commented on GitHub (Apr 4, 2023): TCP6 and UDP6 aren't actual protocols. Rather, they're just shorthand used by some applications to imply that a port is bound to an IPv6 address (which can already be modeled explicitly in NetBox).
Author
Owner

@DanSheps commented on GitHub (Apr 4, 2023):

I agree with @jeremystretch on this.

You can determine if it is TCP6 by the type of address assigned.

@DanSheps commented on GitHub (Apr 4, 2023): I agree with @jeremystretch on this. You can determine if it is TCP6 by the type of address assigned.
Author
Owner

@jeremystretch commented on GitHub (Apr 5, 2023):

Closing this as it does not seem to warrant any action.

@jeremystretch commented on GitHub (Apr 5, 2023): Closing this as it does not seem to warrant any action.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7855