port forwarding should support port ranges

What is missing?

Openstack allows forwarding a range of ports in a single call using syntax like:
openstack floating ip port forwarding create --internal-protocol-port 15000:15099 ...
but gophercloud is forcing the type for these fields to be integer.

Per Neutron API documentation[1], we're indeed missing InternalPortRange and ExternalPortRange, so this looks like a valid bug.

Would you like to give it a spin?

[1] https://docs.openstack.org/api-ref/network/v2/index.html#port-forwarding-with-port-ranges

Well, I have a bigger issue. I was led here because the terraform openstack provider uses gophercloud v2.10.0 and cant (easily) upgrade to the latest. I’ve internally patched v2.10.0 to support port ranges and was able to get terraform working but something tells me you wont be eager to make a v2.10.1 release just for this issue so I’m kind of stuck. b

…

On May 14, 2026, at 10:03 PM, Winicius Allan ***@***.***> wrote: winiciusallan left a comment (gophercloud/gophercloud#3750) <#3750 (comment)> Per Neutron API documentation[1], we're indeed missing InternalPortRange and ExternalPortRange, so this looks like a valid bug. Would you like to give it a spin? [1] https://docs.openstack.org/api-ref/network/v2/index.html#port-forwarding-with-port-ranges — Reply to this email directly, view it on GitHub <#3750 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABMRU52CSSIQG245LZE7BDT42YQ7RAVCNFSM6AAAAACY5SAV56VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DINJUGI4DENRRHA>. You are receiving this because you authored the thread.

Great to hear that you've managed the issue.

I'm not the one who cuts the releases, but I'd say that this change should be made in a minor version, instead of a patch, since we follow semver and this is an API change. A maintainer can confirm this.

In normal circumstances, we (or you) would implement your changes for v2.13.0 and ask for the terraform-provider-openstack maintainer(s) to bump gophercloud version so you can have your feature there.

If you are ok with this, feel free to submit a PR against the main branch. I'll be happy to review it 😃

Whelp, I’m sure I did it wrong but I opened a PR for this. The issue is 3750. If you accept it, and after you release v2.13.0, I’ll worry about the terraform openstack provider. I’m also attaching my test program. Bob

…

On May 15, 2026, at 2:03 PM, Winicius Allan ***@***.***> wrote: winiciusallan left a comment (gophercloud/gophercloud#3750) <#3750 (comment)> Great to hear that you've managed the issue. I'm not the one who cuts the releases, but I'd say that this change should be made in a minor version, instead of a patch, since we follow semver and this is an API change. A maintainer can confirm this. In normal circumstances, we (or you) would implement your changes for v2.13.0 and ask for the terraform-provider-openstack maintainer(s) to bump gophercloud version so you can have your feature there. If you are ok with this, feel free to submit a PR against the main branch. I'll be happy to review it 😃 — Reply to this email directly, view it on GitHub <#3750 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABMRU52X7KEAJDJL76AR2HD424BSNAVCNFSM6AAAAACY5SAV56VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DINJZGU3TQMRQGE>. You are receiving this because you authored the thread.

Whelp, I’m sure I did it wrong but I opened a PR for this. The issue is 3750.

It looks like you pushed a commit from an old branch. I highly recommend that you take a look at the contribution guide.

We merge changes into the main branch and backport non-breaking changes to V2 or V1. That being said, you should create a new branch from the main and push it (I believe it is okay if you create a fresh PR for this).

If you need some help from my side, let me know.

Can you access https://github.com/rjmercier1/gophercloud ? I just did a normal fork and unchecked the ‘main only’ button. ***@***.***:~/bob/git/gophercloud# git show $(git merge-base main b/portforward) commit 148e8c3 (origin/main, origin/HEAD, main) b

…

On May 15, 2026, at 4:14 PM, Winicius Allan ***@***.***> wrote: winiciusallan left a comment (gophercloud/gophercloud#3750) <#3750 (comment)> Whelp, I’m sure I did it wrong but I opened a PR for this. The issue is 3750. It looks like you pushed a commit from an old branch. I highly recommend that you take a look at the contribution guide <https://github.com/gophercloud/gophercloud/blob/main/.github/CONTRIBUTING.md>. We merge changes into the main branch and backport non-breaking changes to V2 or V1. That being said, you should create a new branch from the main and push it (I believe it is okay if you create a fresh PR for this). If you need some help from my side, let me know. — Reply to this email directly, view it on GitHub <#3750 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABMRU537UNYDYIJWVP4FVW3424Q4XAVCNFSM6AAAAACY5SAV56VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DINRQGUYTSMRUHA>. You are receiving this because you authored the thread.

@rjmercier1

@rjmercier1 In the previous message, I was talking about the PR that you closed. Regarding your actual PR (#3756), it is all good.

Ok, so you need me to update the test cases. It’s going to take me a bit because I can’t run the tests agains our production cluster. On May 18, 2026, at 4:21 PM, Winicius Allan ***@***.***> wrote:winiciusallan left a comment (gophercloud/gophercloud#3750) @rjmercier1 In the previous message, I was talking about the PR that you closed. Regarding your actual PR (#3756), it is all good. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

Ok, so you need me to update the test cases. It’s going to take me a bit because I can’t run the tests agains our production

Feel free to join us at #gophercloud in the Kubernetes slack workspace if you need some help :)

I’ve added acceptance tests for port ranges b

…

On May 18, 2026, at 5:48 PM, Winicius Allan ***@***.***> wrote: winiciusallan left a comment (gophercloud/gophercloud#3750) <#3750 (comment)> Ok, so you need me to update the test cases. It’s going to take me a bit because I can’t run the tests agains our production Feel free to join us at #gophercloud <https://kubernetes.slack.com/archives/C05G4NJ6P6X> in the Kubernetes slack workspace if you need some help :) — Reply to this email directly, view it on GitHub <#3750?email_source=notifications&email_token=ABMRU52OYGG3XHGMYVUSYJL43MWDNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINBXHEZTMNRZHA3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4479366986>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABMRU57MXLMKVER25RSUR5L43MWDNAVCNFSM6AAAAACY5SAV56VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DINZZGM3DMOJYGY>. You are receiving this because you were mentioned.

Navigation Menu

Repository navigation

port forwarding should support port ranges #3750

What is missing?

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

port forwarding should support port ranges #3750

Description

What is missing?

Activity

winiciusallan commented on May 14, 2026

rjmercier1 commented on May 15, 2026

winiciusallan commented on May 15, 2026

rjmercier1 commented on May 15, 2026

winiciusallan commented on May 15, 2026

rjmercier1 commented on May 15, 2026

winiciusallan commented on May 18, 2026

rjmercier1 commented on May 18, 2026

winiciusallan commented on May 18, 2026

rjmercier1 commented on May 19, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions