Skip to content

Conversation

@larsks
Copy link
Member

@larsks larsks commented Aug 20, 2025

Previously, if --internal-ip-network was provided, we would find ports on
the wrong network because we were only searching for ports by address. With
this change, ports must match both the address and the network in order to
be considered.

@larsks
Copy link
Member Author

larsks commented Aug 20, 2025

I will update this shortly with working tests.

@larsks larsks force-pushed the fix/port-forwarding branch 4 times, most recently from 25eadd3 to 515084a Compare August 20, 2025 14:36
Previously, if --internal-ip-network was provided, we would find ports on
the wrong network because we were only searching for ports by address. With
this change, ports must match both the address and the network in order to
be considered.
@larsks larsks force-pushed the fix/port-forwarding branch from 515084a to ee6bc0e Compare August 20, 2025 14:39
@larsks larsks enabled auto-merge August 20, 2025 14:42
@larsks larsks merged commit b9c4d29 into CCI-MOC:master Aug 20, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants