rofl0r / rofl0r/proxychains-ng
dynamic_chain - socket error or timeout!
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 10.7k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
proxychains isn't working when I use dynamic_chain.... Any idea why it fails?
nmap with dynamic proxychains
./proxychains4 -f proxychains4.conf nmap -p 1433 192.168.210.15 -Pn
[proxychains] config file found: proxychains4.conf
[proxychains] preloading ./libproxychains4.so
[proxychains] DLL init: proxychains-ng 4.16-git-15-g0c79508
Starting Nmap 7.94 ( https://nmap.org ) at 2023-08-17 16:13 EDT
[proxychains] Dynamic chain ... 127.0.0.1:1080 ... 127.0.0.1 :1081 <--socket error or timeout!
[proxychains] Dynamic chain ... 127.0.0.1:1080 ... 192.168.210.15:1433 <--socket error or timeout!
contents of proxychains4.conf(enabled options)
dynamic_chain
proxy_dns
tcp_read_time_out 25000
tcp_connect_time_out 12000
[ProxyList]
socks5 127.0.0.1 1080
socks5 127.0.0.1 1081
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported ./proxychains4 command with the shown proxychains4.conf and the two SOCKS5 endpoints, then inspect the dynamic-chain connection path. Compare the timeout and socket-error behavior for 127.0.0.1:1080, 127.0.0.1:1081, and the target; done means the failure has a confirmed cause and a concrete correction or explanation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100