|S-chain| -<>- 127.0.0.1:9050-<--timeout
|DNS-response|:
ipinfo.io
does not exist
This happens because proxychains reads a proxy configured over the 9050
port of your computer by default, i.e. in local with 127.0.0.1 as the IP. To let it
read a list of your proxies, you have to create a config file.
Using the terminal,
launch the following:
$ mkdir $HOME/.proxychains
$ nano $HOME/.proxychains/proxychains.conf
This way, we firstly created the folder containing the config file, then we
launched the nano text editor over the “secret”
path in our user folder. Please
note the first call of
$HOME, a variable allowing you to immediately access the
absolute folder of your user.
In my case, the user is named
stefano9lli, so the
folder path will be
/home/stefano9lli, which is in turn appended to the rest of the
string.
You may also notice that the
.proxychains folder is called after $HOME
variable. In the UNIX world, a period before a folder name means that it must be
hidden when you use a file manager. Now, we will create the
proxychains.conf
file within the folder. And we are ready to add some values:
strict_chain
proxy_dns
[ProxyList]
http proxy port
Save using the
CTRL+X combination, the
Y key and pressing
ENTER.
Remember: you can use one of the following configurations to use different
protocols:
strict_chain
proxy_dns
[ProxyList]
http proxy port
socks4 proxy port
socks5 proxy port
Launch again wget with the new configuration (in this example,
the proxy is
177.73.177.25 and the port is 8080):
$ proxychains wget
http://ipinfo.io/ip
-qO -
ProxyChains-3.1 (
http://proxychains.sf.net
)
|DNS-request|
ipinfo.io
|S-chain|-<>-177.73.177.25:8080-<><>-4.2.2.2:53-<><>-OK
|DNS-response|
ipinfo.io
is 54.164.157.29
|S-chain|-<>-177.73.177.25:8080-<><>-54.164.157.29:80-<><>-OK
177.73.177.25
|DNS-response|:
ipinfo.io
does not exist
As we can see, this time the ipinfo.io website returns the proxy IP instead the
one of yours, indicating that proxychains worked successfully.
Keep in mind
that, actually, many proxies could be already configured to work under certain
conditions only, so they could refuse to respond to some types of domain
requests or to programs without user-agent. Naturally, trying is the best option.
All the use cases for proxychains are explained in the following manual:
$ man proxychains
Proxycap
Maybe the most popular Windows
counterpart to proxychains is Proxycap
[11]
(Figure 9), a program developed by the Initex team for over 10 years. Just like
Do'stlaringiz bilan baham: