Closed freidenker closed 1 year ago
looks like graftcp redirected aws internal dns requests. it make connection refused.
[2023-05-18 17:44:11] [INFO] Request PID: 45, Source Addr: 127.0.0.1:43100, Dest Addr: 99.84.140.88:443 [2023-05-18 17:44:14] [INFO] Request PID: 45, Source Addr: 127.0.0.1:43106, Dest Addr: 10.16.0.2:53
[18/May/2023:09:50:39 UTC] [15254] 52.82.106.138 winter "CONNECT" STARTED 0 0 0 (52.82.106.138:8054 -> 74.125.204.82:443) [18/May/2023:09:50:43 UTC] [15152] [ERRO] $ConnectServing$: (Connection timed out). [18/May/2023:09:50:43 UTC] [15152] 52.82.106.138 winter "CONNECT" CONNREFUSED 0 0 - (52.82.106.138:46722 -> 10.16.0.2:53) [18/May/2023:09:51:04 UTC] [15254] 52.82.106.138 winter "CONNECT" TERMINATED 9456971 21159 25 (52.82.106.138:8054 -> 74.125.204.82:443)
This tool does not have the ability to redirect UDP traffic, and since DNS belongs to UDP traffic, DNS resolution will not be affected by this tool.
looks like graftcp redirected aws internal dns requests. it make connection refused.
graftcp node log:
ss5 proxy server log: