mingang.he

@tangr Fixing this issue based on the [commit](https://github.com/hmgle/graftcp/commit/52d79e23cd116640139b20296772810d72f65898) above. Feel free to reopen/comment or create a new one if the problem still exists. Thank you.

Could you provide the version information for curl? I'm not sure whether modifying the address parameter of the connect(2) will impact curl. It's possible that curl checks this parameter after...

~~I've reviewed the code and found that this error occurs before the connect(2) syscall returns, so it's not for the reason mentioned above but due to some other cause.~~

@CaledoniaProject I have added some logs to track the PIDs and their IP address infomation in local, and pushed them to a new branch(debug-local). You can switch to this new...

@CaledoniaProject Thank you for your feedback. Is this bug consistently or reliably reproducible for `curl` in the Amazon Linux? Does the same issue occur with other commands, such as `wget`?...

I think I have found out the cause of this issue. The Amazon Linux host you are using seems to have rewritten packets with a source address of 127.0.0.1 to...

@CaledoniaProject I have updated the [`getPidByAddr`](https://github.com/hmgle/graftcp/commit/11c0c7e51f1f1b60af7381418f0f4ebac8a805b6#diff-28b5602b66ba5bfacacd48c30423065bf23d616dc8a61b3256be1b120f3fc166) function to handle cases where the source IP address in the IP packet header has been modified. However, there is still an unusual case...

> any workaround to solve this ? > > ``` > graftcp-local -socks5 23.230.167.1XX:1080 -listen :7777 > ``` > > results > > ``` > root@pentest:/var/www# graftcp curl ipinfo.io/ip >...

> nvm i just figured that out @hmgle , it seems that i changed the default listen port on graftcp-local but i didn't specify it on graftcp command via `-n`...

Closing this issue based on the [commit](https://github.com/hmgle/graftcp/commit/2dfe81a1182d09640add3c4b2fd11e634fa2607a) above. Feel free to reopen/comment or create a new one if the problem still exists. Thank you.