-
Notifications
You must be signed in to change notification settings - Fork 235
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
Could you add a option to bind the client port on 0.0.0.0 in the ssfc ? #24
Comments
Planned for the next release. We may also add a way to specify the listening network interface in the config file. |
We mimic SSH behavior. To listen on the wildcard interface, you will need the following command line: You can also indicate a specific network listening interface: This syntax will be available on all client features (local or remote). (cf. We are making some final check before tagging the new version and we will release the new binaries :-) |
2.2.0 binaries are out. Feel free to test them and make us feedback. |
Just like the
-g
option inssh -g -L 6667:localhost:6667 192.168.1.101
.I create a UDP port forwarding and I notice that I can only access the client port on localhost, but I need to let another device (my phone) to access the client port.
So could you add the option to let the client port can be accessed anywhere?
The text was updated successfully, but these errors were encountered: