rofl0r

until @zhangjunphy's branch is ready for primetime, the following small patch should be able to workaround the ::1 issue ```diff --- a/src/libproxychains.c +++ b/src/libproxychains.c @@ -589,6 +589,9 @@ int connect(int...

i guess we could add a config item like RANDOM_CHAIN_FIXED_ENTRIES for that purpose. PR's welcome.

that would require incompatible config files. the change i suggested can be implemented with minimal effort and changes, while this would require a lot of refactoring.

hmm... since 3proxy can do this already, why not configure the chain sections via 3proxy, then run `proxychains4 -f connect_local_3proxy.conf myapp` ?

i can't, as i never used "dante socksify" though i guess the latter doesn't support chaining of proxies.

it seems you are using random proxies from some proxylist. those often either don't work at all or are really slow, so they need a high timeout. additionally the sandbox...

proxychains.conf is a textfile, not a shell script. as such, variable expansion naturally doesn't work. however, you can create your proxychains.conf dynamically using a shell script, e.g. as proposed in...

> Can I run proxychains4 with microsocks in a docker container?) i'm certain you can, but that just makes it more difficult to generate a dynamic proxychains.conf. what's the advantage...

> it installed just with snap... the cool kids on github install stuff from source... )

- provide log output - compile with -DDEBUG in CFLAGS and provide more log output