Repository navigation
Fix custom proxy port support in SSH proxy tunnels - #332
Merged
jdhall75 merged 2 commits intoSep 30, 2025
Merged
Conversation
Fixed linting errors
Collaborator
|
Thanks!! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR ensures that the proxy.port value defined in devices.yaml is correctly passed into the SSH tunnel constructor. Previously Hyperglass always fell back to port 22 when opening a proxy tunnel, even if you specified a different port.
Motivation and Context
Operators might need to run their SSH jump hosts on non-standard ports (for example, 61440). Until now, those custom proxy.port settings were ignored, preventing Hyperglass from ever reaching the proxy on the intended port.
Tests