-
Notifications
You must be signed in to change notification settings - Fork 1.3k
rportfwd issue #1906
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
Comments
I think I know what's going on, I'll try to push a fix when I get some time. |
This is the culprit: sliver/server/handlers/sessions.go Lines 229 to 235 in a89675d
I wrongly assumed that |
Thank you very much, will you release a binary version? |
Yes, probably 1.5.44 when I get to it. |
Can you fix the rportfwd issue? I'm trying to manage two mapped ports and am having a lot of trouble. It seems like when two or more ports are created, they get corrupted. Thanks!! |
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
There seems to be a problem when I use "rportfwd" in the implant:
rportfwd add -b 192.168.100.51:9000 -r 127.0.0.1:9000
[*] Reverse port forwarding 127.0.0.1:9000 <- 192.168.100.51:9000
What I want is for the 192.168.100.51 machine to connect to port 9000, and it will be redirected to port 9000 on my machine.
It only works the first time I connect to 192.168.100.51:9000. On subsequent connections, the tunnel seems to close.
On machine 127.0.0.1:9000 I have a web server.
To Reproduce
rportfwd add -b 192.168.100.51:9000 -r 127.0.0.1:9000
Expected behavior
That the tunnel does not close.
Versions:
Additional context
Log:
The text was updated successfully, but these errors were encountered: