Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client listening port can not be modified #5

Closed
integritybravery opened this issue Oct 24, 2017 · 2 comments
Closed

Client listening port can not be modified #5

integritybravery opened this issue Oct 24, 2017 · 2 comments

Comments

@integritybravery
Copy link

How to specify the client listening port, the client listening port can not be modified, always 1234.

@integritybravery
Copy link
Author

integritybravery commented Oct 25, 2017

IP can not bind the public network address, always 127.0.0.1:1234.

@blanu
Copy link
Contributor

blanu commented Jan 15, 2018

This issue should have been resolved in release 2.0.1: https://github.com/OperatorFoundation/shapeshifter-dispatcher/releases/tag/2.0.1

Please note that historically, there has not been a way to specify the client listening port. In the past, the SOCKS address was hardcoded to 127.0.0.1:0, which only allows binding to localhost and a random port.

Adding the new -proxylistenaddr command line flag allows for specifying both the IP and port to bind to for accepting client proxy requests, and has been added to PT2/SOCKS mode, transparent TCP mode, and both UDP modes.

This is currently an experimental extension not covered in the PT 2.0 specification and will be considered for inclusion in the PT 2.1 specification. If you have any feedback on how this feature should work, please discuss so that we can add the best possible version of this feature to the specification.

@blanu blanu closed this as completed Jan 15, 2018
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

No branches or pull requests

2 participants