Using Port Ranges in ACL will result in error code 422 #2476

Open
opened 2025-11-20 07:10:16 -05:00 by saavagebueno · 0 comments
Owner

Originally created by @on-nightingale on GitHub (Nov 19, 2025).

Describe the problem

Adding a Port Range to an Access Control Policy with protocol TCP or UDP will result in this error:

Request failed with status code 422
Error: For all or icmp protocol type flow can be only bi-directional

Image

To Reproduce

Steps to reproduce the behavior:

  1. Go to 'Access Control' -> 'Policies'
  2. Click on '+ Add Policy'
  3. Select Protocol 'UDP' (or TCP)
  4. Select a Source Group
  5. Select a Destination Group (I used one with CIDR Resources)
  6. Direction will automatically switch to one-way
  7. Add '5061-65535' to Ports
  8. Click on 'Name & Description'
  9. Add a name to 'Name of the Rule'
  10. Click on '+ Add Policy'Expected behavior

The Policy will accept port ranges for TCP and UDP.

Are you using NetBird Cloud?

No

NetBird version

0.60.0

Is any other VPN software installed?

Yes

Debug output

No debug output of client needed, as this issue is in the API and Dashboard.

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

Have you tried these troubleshooting steps?

Originally created by @on-nightingale on GitHub (Nov 19, 2025). **Describe the problem** Adding a Port Range to an Access Control Policy with protocol TCP or UDP will result in this error: _Request failed with status code 422 Error: For all or icmp protocol type flow can be only bi-directional_ <img width="463" height="90" alt="Image" src="https://github.com/user-attachments/assets/8818a82d-e234-4036-8b82-aaa21a23f9a7" /> **To Reproduce** Steps to reproduce the behavior: 1. Go to 'Access Control' -> 'Policies' 2. Click on '+ Add Policy' 3. Select Protocol 'UDP' (or TCP) 4. Select a Source Group 5. Select a Destination Group (I used one with CIDR Resources) 6. Direction will automatically switch to one-way 7. Add '5061-65535' to Ports 8. Click on 'Name & Description' 9. Add a name to 'Name of the Rule' 10. Click on '+ Add Policy'**Expected behavior** The Policy will accept port ranges for TCP and UDP. **Are you using NetBird Cloud?** No **NetBird version** `0.60.0` **Is any other VPN software installed?** Yes **Debug output** No debug output of client needed, as this issue is in the API and Dashboard. **Screenshots** If applicable, add screenshots to help explain your problem. **Additional context** Add any other context about the problem here. **Have you tried these troubleshooting steps?** - [x] Reviewed [client troubleshooting](https://docs.netbird.io/how-to/troubleshooting-client) (if applicable) - [x] Checked for newer NetBird versions - [x] Searched for similar issues on GitHub (including closed ones) https://github.com/netbirdio/netbird/issues/1995 https://github.com/netbirdio/netbird/issues/2320 - [ ] Restarted the NetBird client - [ ] Disabled other VPN software - [ ] Checked firewall settings
saavagebueno added the triage-needed label 2025-11-20 07:10:16 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#2476