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

server verbose logging does not print out the remote address #233

Closed
matti opened this issue Dec 30, 2020 · 2 comments
Closed

server verbose logging does not print out the remote address #233

matti opened this issue Dec 30, 2020 · 2 comments

Comments

@matti
Copy link

matti commented Dec 30, 2020

$ chisel server --reverse -v
2020/12/31 00:08:04 server: Reverse tunnelling enabled
2020/12/31 00:08:04 server: Fingerprint 1mS6n2APlkBh30oiqG1yb79RHzQezhGQqj3ogVTrauI=
2020/12/31 00:08:04 server: Listening on http://0.0.0.0:8080
2020/12/31 00:08:20 server: session#1: Handshaking...
2020/12/31 00:08:20 server: session#1: Verifying configuration
2020/12/31 00:08:20 server: session#1: tun: Created
2020/12/31 00:08:20 server: session#1: tun: SSH connected
2020/12/31 00:08:20 server: session#1: tun: proxy#R:1080=>socks: Listening
2020/12/31 00:08:20 server: session#1: tun: Bound proxies

^-- would be nice to know the client address

@jpillora
Copy link
Owner

jpillora commented Dec 31, 2020 via email

@mrdc
Copy link

mrdc commented Mar 31, 2021

@jpillora
Hi,
Can we also add in debug logs some simple detection for probing (if somebody wants to get in for example)? Using -v I see requests to chisel when reverse proxy mode is enabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants