-
Notifications
You must be signed in to change notification settings - Fork 1.3k
rportfwd do not work #1918
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
Closing as it's a duplicate of #1906 |
func createReverseTunnelHandler(implantConn *core.ImplantConnection, data []byte) *sliverpb.Envelope {
maybe it works?i tested this could be work in my local pc. but msf met toubles |
That could work, I was thinking about moving the call to |
Uh oh!
There was an error while loading. Please reload this page.
I compiled a sliver-server using the main branch, rportfwd do not work
rportfwd add -b 10.0.3.178:1000 -r 127.0.0.1:9911
[*] Reverse port forwarding 127.0.0.1:9911 <- 10.0.3.178:1000
sliver.log:
ERRO[2025-03-28T00:45:18+08:00] [sliver/server/handlers/sessions.go:231] Session d55d7a8f-fd3f-467a-9f12-e33b2ee0b1fe attempted to create reverse tunnel to 127.0.0.1:9900 without being initiated by a client
ERRO[2025-03-28T00:45:52+08:00] [sliver/server/handlers/sessions.go:231] Session d55d7a8f-fd3f-467a-9f12-e33b2ee0b1fe attempted to create reverse tunnel to 127.0.0.1:9900 without being initiated by a client
ERRO[2025-03-28T00:45:53+08:00] [sliver/server/handlers/sessions.go:231] Session d55d7a8f-fd3f-467a-9f12-e33b2ee0b1fe attempted to create reverse tunnel to 127.0.0.1:9900 without being initiated by a client
ERRO[2025-03-28T00:46:41+08:00] [sliver/server/handlers/sessions.go:231] Session d55d7a8f-fd3f-467a-9f12-e33b2ee0b1fe attempted to create reverse tunnel to 127.0.0.1:9900 without being initiated by a client
ERRO[2025-03-28T00:46:42+08:00] [sliver/server/handlers/sessions.go:231] Session d55d7a8f-fd3f-467a-9f12-e33b2ee0b1fe attempted to create reverse tunnel to 127.0.0.1:9900 without being initiated by a client
The text was updated successfully, but these errors were encountered: