You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
How to specify the client listening port, the client listening port can not be modified, always 1234.
The text was updated successfully, but these errors were encountered: