ma6174

Results 29 comments of ma6174

I also tested some other software similar to proxychains, [kneesocks](https://github.com/inaz2/kneesocks)(with some [fix](https://github.com/ma6174/kneesocks/commit/aa6515975fb1d953a994b9545ef544b074d8ad02)) works well on linux with MongoDB version 3.2 and 3.4, so there must be some potential bug in...

After some debugging, I found after this commit https://github.com/mongodb/mongo/commit/b256b88c78c28e37b033fcb0134e75649fbe3d5c proxychains don't work. It looks proxychains not work well with asio network library?

MongoDB removed the thread based network interface from code: https://github.com/mongodb/mongo/commit/a998887902dfd9cb6f125233c86361064f80c57e after switch network interface to ASIO, it cannot be simply revert this two commit because some future changes may not...

Here is the full log of mongod and proxychains both with debug open: ``` $ ./proxychains4 -f proxychains.conf ./mongod --dbpath data1 --replSet test --port 1111 -vv [proxychains] config file found:...

I use gdb debugged at `timed_connect()` in proxychains and `connect_proxy` in [kneesocks](https://github.com/inaz2/kneesocks/blob/master/libkneesocks.c#L84-L96), for proxtchains, and change the type of addr from `struct sockaddr *` to `struct sockaddr_in *`. `addr` in...

if I commenting out line 184 in core.c, still connect failed, `connect ret=-1`: ``` 2017-05-04T06:21:06.701+0800 I ASIO [NetworkInterfaceASIO-Replication-0] Connecting to 10.200.20.56:1112 DEBUG:getaddrinfo: 10.200.20.56 1112 DEBUG:pid[36566]:proxy_getaddrinfo DEBUG:freeaddrinfo 0x7f724a028140 DEBUG:pid[36566]:proxy_freeaddrinfo DEBUG:pid[36566]:connect DEBUG:target:...

with the patch, `connect ret=0`, connect success, but still got `Operation timed out` ``` 2017-05-04T09:27:58.321+0800 I ASIO [NetworkInterfaceASIO-Replication-0] Connecting to 10.200.20.56:1112 DEBUG:getaddrinfo: 10.200.20.56 1112 DEBUG:pid[15371]:proxy_getaddrinfo DEBUG:freeaddrinfo 0x7f85f0141000 DEBUG:pid[15371]:proxy_freeaddrinfo DEBUG:pid[15371]:connect DEBUG:target:...

now `connect ret=-1`, connect failed ``` 2017-05-04T10:30:45.192+0800 I ASIO [NetworkInterfaceASIO-Replication-0] Connecting to 10.200.20.56:1112 DEBUG:getaddrinfo: 10.200.20.56 1112 DEBUG:pid[36723]:proxy_getaddrinfo DEBUG:freeaddrinfo 0x7f570429e140 DEBUG:pid[36723]:proxy_freeaddrinfo DEBUG:pid[36723]:connect DEBUG:target: 10.200.20.56 DEBUG:port: 1112 DEBUG:pid[36723]:connect_proxy_chain DEBUG:[busy] socks5 127.0.0.1:2345 [proxychains]...

yes, both the one-line change and the new patch don't work, connect failed ```diff diff --git a/src/core.c b/src/core.c index 19cd3da..510400d 100644 --- a/src/core.c +++ b/src/core.c @@ -155,7 +155,8 @@ static...

I'm sure it's in latest nonblock branch: here is the git info: ```bash $ git branch master * nonblock $ git log | head commit cbddf15b19191257de302687df558adfae10aeb5 Author: rofl0r Date: Thu...