-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Fix client dialer log #1568
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
Fix client dialer log #1568
Conversation
Log such as: tunneling request to tcp:www.google.com:80 via tcp:x.x.x.x:443 the second "tcp" is misleading when using mKcp or quic transport Remove the second "tcp" and add the correct logging for transport dialer: - transport/internet/tcp: dialing TCP to tcp:x.x.x.x:443 - transport/internet/quic: dialing quic to udp:x.x.x.x:443
Codecov Report
@@ Coverage Diff @@
## master #1568 +/- ##
==========================================
- Coverage 39.29% 39.21% -0.09%
==========================================
Files 602 605 +3
Lines 35480 35630 +150
==========================================
+ Hits 13941 13971 +30
- Misses 20003 20100 +97
- Partials 1536 1559 +23
Continue to review full report at Codecov.
|
Co-authored-by: 秋のかえで <autmaple@protonmail.com>
@@ -75,7 +75,7 @@ func (c *Client) Process(ctx context.Context, link *transport.Link, dialer inter | |||
if err != nil { | |||
return newError("failed to find an available destination").AtWarning().Base(err) | |||
} | |||
newError("tunneling request to ", destination, " via ", server.Destination()).WriteToLog(session.ExportIDToError(ctx)) | |||
newError("tunneling request to ", destination, " via ", network, ":", server.Destination().NetAddr()).WriteToLog(session.ExportIDToError(ctx)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it will be misleading when using mKCP and QUIC.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What if we change it to this:
tun... to... via ... drive...
or transport...
tun... to tcp:google.com:443 via tcp:127.0.0.1:1080 transport quic
Log such as:
tunneling request to tcp:www.google.com:80 via tcp:x.x.x.x:443
the second "tcp" is misleading when using mKcp or quic transport
Remove the second "tcp" and add the correct logging for transport dialer: