Open
Conversation
adds support for "forwarding rules" whereby rules of the form match_name:match_port,[user:pass@]upstream_name:upstream_port,remote_name:remote_port cause microsocks to forward the *match* request to the *upstream* SOCKS5 server using the name *remote*. this is particularly useful for accessing webuis of devices attached to various remote private networks: one can run a private microsocks (or other SOCKS5 server) on the PC attached to the remote network, and point a local microsocks instance at that server, allowing specific names to be forwarded to the private network without affecting normal browser traffic.
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
1 participant
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.
This may be well out of scope for microsocks, but it was useful for me so sharing it here:
adds support for "forwarding rules" whereby rules of the form
match_name:match_port,[user:pass@]upstream_name:upstream_port,remote_name:remote_port`
cause microsocks to forward the match request to the upstream SOCKS5 server using the name remote.
this is particularly useful for accessing webuis of devices attached to various remote private networks: one can run a private microsocks (or other SOCKS5 server) on the PC attached to the remote network, and point a local microsocks instance at that server, allowing specific names to be forwarded to the private network without affecting normal browser traffic.