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
Currently, when proxied application makes a connection, it immediately succeeds as if port is always open. This works very differently from proxychains, which waits to establish connection with the remote. It is a subtle difference, but it breaks software that needs to check if port is truly open.
Is it possible with current tun2socks architecture to implement feature (or is this a bug?) where tun2socks would first try to connect to the port, and only if it succeeds, report success on the client side?
Is this feature related to a specific bug?
No response
Do you have a specific solution in mind?
No response
The text was updated successfully, but these errors were encountered:
This feature has been mentioned in issue #83, and we have a closed/incomplete pr #235 for this kind of scenario.
Unfortunately, this feature is not yet planned to implement. But if you would like to contribute, a pr is always welcome!
xjasonlyu
changed the title
Do not accept connection locally before connection with remote is established, is it possible?[Feature]
[Feature] Do not accept connection locally before connection with remote is established
Dec 25, 2023
Description
Currently, when proxied application makes a connection, it immediately succeeds as if port is always open. This works very differently from proxychains, which waits to establish connection with the remote. It is a subtle difference, but it breaks software that needs to check if port is truly open.
Is it possible with current tun2socks architecture to implement feature (or is this a bug?) where tun2socks would first try to connect to the port, and only if it succeeds, report success on the client side?
Is this feature related to a specific bug?
No response
Do you have a specific solution in mind?
No response
The text was updated successfully, but these errors were encountered: