FR: Port ranges in TCP/UDP access control #515

Closed
opened 2025-11-20 05:12:52 -05:00 by saavagebueno · 10 comments
Owner

Originally created by @azey7f on GitHub (Nov 23, 2023).

Is your feature request related to a problem? Please describe.
Typing out individual ports can be tedious at best and pretty much impossible at worst when trying to allow bigger port ranges like 1-1024, or when trying to allow all ports (1-65535) for a unidirectional rule.

Describe the solution you'd like
Add support for specifying port ranges in TCP/UDP access control rules instead of only specific ports.

Describe alternatives you've considered
N/A

Additional context
N/A

Originally created by @azey7f on GitHub (Nov 23, 2023). **Is your feature request related to a problem? Please describe.** Typing out individual ports can be tedious at best and pretty much impossible at worst when trying to allow bigger port ranges like 1-1024, or when trying to allow all ports (1-65535) for a unidirectional rule. **Describe the solution you'd like** Add support for specifying port ranges in TCP/UDP access control rules instead of only specific ports. **Describe alternatives you've considered** N/A **Additional context** N/A
saavagebueno added the feature-request label 2025-11-20 05:12:52 -05:00
Author
Owner

@joshmc82 commented on GitHub (Jan 9, 2024):

I would like to see this feature as well. I'm a new NetBird user but this is an important one for me.

@joshmc82 commented on GitHub (Jan 9, 2024): I would like to see this feature as well. I'm a new NetBird user but this is an important one for me.
Author
Owner

@EnterTheC commented on GitHub (Feb 24, 2024):

+1 :)

@EnterTheC commented on GitHub (Feb 24, 2024): +1 :)
Author
Owner

@Mifody-07 commented on GitHub (May 9, 2024):

I recently came across the need to create a rule to access a server that can dynamically select a port from the 1560:1591 range. Too bad netbird does not support port ranges.

@Mifody-07 commented on GitHub (May 9, 2024): I recently came across the need to create a rule to access a server that can dynamically select a port from the 1560:1591 range. Too bad netbird does not support port ranges.
Author
Owner

@da-wilky commented on GitHub (Jul 30, 2024):

That would be so helpful. You have currently no way to allow only TCP in only one direction...

@da-wilky commented on GitHub (Jul 30, 2024): That would be so helpful. You have currently no way to allow only TCP in only one direction...
Author
Owner

@hartmanshk commented on GitHub (Sep 19, 2024):

I would also greatly appreciate this feature.

@hartmanshk commented on GitHub (Sep 19, 2024): I would also greatly appreciate this feature.
Author
Owner

@northport-io commented on GitHub (Oct 3, 2024):

same

@northport-io commented on GitHub (Oct 3, 2024): same
Author
Owner

@JonTheNiceGuy commented on GitHub (Oct 17, 2024):

Interestingly, in this code block it shows "IsRange". This feels like it's on the road-map they've just not got to it yet.

@JonTheNiceGuy commented on GitHub (Oct 17, 2024): Interestingly, in this [code block](https://github.com/netbirdio/netbird/blob/006ba32086244b87430a3c1e58f7a53a9aae4fe2/client/firewall/manager/port.go#L28-L34) it shows "IsRange". This feels like it's on the road-map they've just not got to it yet.
Author
Owner

@ThHirsch commented on GitHub (Nov 6, 2024):

+1, otherwise following best practices in 'least privilege' setup is a faaar too tedious task.

@ThHirsch commented on GitHub (Nov 6, 2024): +1, otherwise following best practices in 'least privilege' setup is a faaar too tedious task.
Author
Owner

@ThHirsch commented on GitHub (Nov 23, 2024):

Hmm, the API documentation is stating, that port RANGES can be specified.
see: Api-docu which states elemnts of "port_ranges - start - end'
So is this just a missing piece int the current UI and we could create port-ranges for TCP and UDP by API already?
Are there any plans to to have it in the UI soon?

@ThHirsch commented on GitHub (Nov 23, 2024): Hmm, the API documentation is stating, that port RANGES can be specified. see: [Api-docu](https://docs.netbird.io/api/resources/policies#create-a-policy) which states elemnts of "port_ranges - start - end' So is this just a missing piece int the current UI and we could create port-ranges for TCP and UDP by API already? Are there any plans to to have it in the UI soon?
Author
Owner

@JonTheNiceGuy commented on GitHub (Nov 23, 2024):

In my brief experiments, port ranges are only valid for "All Ports" (which is 0-65535) and "ICMP"... but ICMP doesn't do "ports" in the same way, so it's not quite valid.

Unless the project want to comment and tell me it's coming :)

@JonTheNiceGuy commented on GitHub (Nov 23, 2024): In my brief experiments, port ranges are only valid for "All Ports" (which is 0-65535) and "ICMP"... but ICMP doesn't do "ports" in the same way, so it's not quite valid. Unless the project want to comment and tell me it's coming :)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#515