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

rcsocks does not always exchange data #7

Open
KVPV opened this issue Oct 23, 2020 · 0 comments
Open

rcsocks does not always exchange data #7

KVPV opened this issue Oct 23, 2020 · 0 comments

Comments

@KVPV
Copy link

KVPV commented Oct 23, 2020

I run it like this: ./rcsocks -p 10001 -l 5001 -b

Correct work:
[+] The reverse client connects successfully to 10001 and listens.
[+] I am successfully connecting to 5001 and sending data.
[+] rcsocks - successfully binds two clients.

Sometimes I get problems like this:
[-] The reverse client receives 0 data from port 10001.
[-] The socket with my connection to port 5001 is closed.

I have to kill the process and start it over and over again until I get it working properly.

Reverse client - this Socks5-client written in C ++ for Windows.

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

1 participant