- Linux Administration Cookbook
- Adam K. Dean
- 133字
- 2021-07-02 14:24:23
Using an SSH config file
The same can be accomplished, as shown previously, by using an SSH config file:
Host *
Port 22
Host CentOS2-V4
Hostname 192.168.33.11
User vagrant
DynamicForward 9999
We can now be confident our proxy will be available each time we connect:
[vagrant@centos1 ~]$ ssh -f CentOS2-V4 sleep 120
And again, look at the contents of the web server:
[vagrant@centos1 ~]$ all_proxy="socks5://127.0.0.1:9999" curl 127.0.0.1:8888
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"><html>
<title>Directory listing for /</title>
<body>
<h2>Directory listing for /</h2>
<hr>
<ul>
<li><a href=".bash_history">.bash_history</a>
<li><a href=".bash_logout">.bash_logout</a>
<li><a href=".bash_profile">.bash_profile</a>
<li><a href=".bashrc">.bashrc</a>
<li><a href=".lesshst">.lesshst</a>
<li><a href=".mysql_history">.mysql_history</a>
<li><a href=".ssh/">.ssh/</a>
</ul>
<hr>
</body>
</html>
Just to prove we were really using our proxy, let's try the curl command without an established session (you will have to wait for SSH to time out, or kill the process if it's not already died):
[vagrant@centos1 ~]$ all_proxy="socks5://127.0.0.1:9999" curl 127.0.0.1:8888
curl: (7) Failed connect to 127.0.0.1:9999; Connection refused