In the previous entry, Creating TCP / IP (port forwarding) tunnels with SSH: The 8 scenarios possible using OpenSSH, we saw all the possibilities we have at our disposal for port forwarding… but for static port forwarding. That is, we only saw cases where we wanted to access only a port of another system by chan- ging it through the SSH connection.
However, in that entry we left in the forefront the dynamic forwarding of ports and several, eral readers missed it, so that this entry will try to complement it (thanks to those who suggest this).
When we talk about doing dynamic port forwarding with SSH, what we are talking about is exactly converting SSH into a SOCKS server. And what is a SOCKS server?
Do you know what a web proxy is for? Probably yes, many companies use one. It is a system directly connected to the Internet that allows clients of an intranet without Internet access to navigate the web if they configure their browsers to make their requests through the proxy ( although there are also transparent proxies ). A web proxy, besides allowing the output to the Internet, will also cache pages, images, etc. Already downloaded by some client so you do not have to download them for another client. In addition, it allows to filter the contents and to monitor the activity of the users. However, its basic function is to forward HTTP and HTTPS traffic.
A SOCKS server would give a service similar to the intranet of a company that provides a proxy server but is not limited to HTTP / HTTPS, but allows to forward any TCP / IP traffic (with SOCKS 5 also UDP).
For example, imagine that we want to use our mail using POP3 or ICMP and SMTP with Thunderbird from an intranet without direct Internet access. If we only have a web proxy available, the only simple one we would use would be to use some webmail (although if it is a webmail we could also use the Thunderbird Webmail extension ). We could also take advantage of the proxy by tunneling over HTTP. But the simplest thing would be that the network had a SOCKS server available that would allow us to use POP3, ICMP and SMTP through it without any inconvenience.
Although there is a lot of software to configure very specialized SOCKS servers, setting up one with OpenSSH could be as simple as:
Clientessh $ ssh -D 1080 user @ servidorssh
Or we could improve it a bit with:
Clientessh $ ssh -fN -D 0.0.0.0:1080 user @ servidorssh
- The option
-Dis similar to the options
-Rstatic port forwarding. Like these, with this we can make the client listen only the local requests or those arriving from other nodes, depending on which address we associate the request:
-D [bind_address:] port
While in static port forwarding we saw that we could do reverse port forwarding with the option
-R, with dynamic forwarding is not possible. We can only create the SOCKS server on the SSH client side, not on the SSH server side.
- 1080 is the typical port for SOCKS servers, just as 8080 is typical for web proxy servers.
- The option
-Nprevents a remote shell interactive session from actually being launched. It is useful when we only do the
sshto establish this tunnel.
- The option
sshit to stay in the background and disassociates itself from the current shell, so that the process becomes a daemon. It does not work without the option
-N(or without specifying a command), otherwise an interactive shell would be incompatible with the process being in the background.
Using PuTTY is also very simple to redirect ports. The equivalent of a ”
ssh -D 0.0.0.0:1080” would be to use this configuration:
For an application to access another network through a SOCKS server, it is convenient (although not necessary) that the application specifically supports it, just as browsers support using a proxy server. Browsers, such as Firefox or Internet Explorer, are examples of applications prepared to use a SOCKS server to access another network:
Note: Capture has been obtained using IEs 4 Linux : Highly recommended if you need Internet Explorer and use Linux!
However, it is not precisely the browsers that most often require a SOCKS server, since they usually are better arranged with the proxy server.
But for example, the Thunderbird also allows and that is useful:
Another example: the Spotify client also supports SOCKS:
Something to keep in mind is name resolution. Sometimes we will find that in the current network we can not resolve the names of the systems that we want to access on the other side of the SOCKS server. SOCKS 5 also allows us to tunnel DNS requests (as is UDP allows us to SOCKS 5) and send them to the other end: It is possible to specify if we want to resolve locally or remotely (or maybe test both). Applications that support this also have to take this into account. For example, Firefox has the parameter network.proxy.socks_remote_dns (in it
about:config) that allows us to specify that it is resolved remotely. By default it is resolved locally.
Thunderbird also supports the parameter
network.proxy.socks_remote_dns, but since we do not have an address bar to place
about:config, we can change it, as we read in MozillaZine: about: config, in Tools → Options → Advanced → General → Config Editor (button).
Applications that do not specifically support SOCKS can be “socksified”. This will work well with many applications that use TCP / IP without problems, but not with all. “Socksifier” consists of loading an additional library that detects requests to the TCP / IP stack and modifying them to redirect them through the SOCKS server, so that the communication goes through without the application being specifically programmed with SOCKS support .
There are “Socksifiers” for Windows and for Linux.
For Windows we have for example the SocksCap, a closed but free product for non-commercial use that I have used very satisfactorily for a long time. SocksCap was made by a company called Permeo which was the company that created SOCKS reference technology. Permeo was bought by Blue Coat and it discontinued the SocksCap. You can still find the file very well
sc32r240.exeon the Internet. Also for Windows, and free code, there is the FreeCap, of appearance and use very, very similar to the SocksCap. However, it works much worse and has been maintenance-free for years. It seems that its author has preferred to dedicate his efforts to a new product this time of payment, the WideCap.
This is the aspect of the SocksCap when we have “socksified” several applications. These applications will access the network through the SOCKS server when we launch them from here:
In the configuration dialog we will see that if we choose the protocol SOCKS 5, we can choose where the names have to be resolved, locally or remotely:
On Linux, as always, we have many alternatives to a single remote command. In Debian / Ubuntu, the output of the command:
$ Apt-cache search socks
Will show us many of them
The best known to me are the tsocks and the proxychains. They work in much the same way: Just launch the application that we want to “socksify” with them and that’s it. An example using
$ Proxychains wget http://www.google.com ProxyChains-3.1 (http://proxychains.sf.net) --19: 13: 20-- http://www.google.com/ Resolving www.google.com ... DNS-request | Www.google.com | S-chain | - <- - 10.23.37.3:1080-<><>-18.104.22.168:53-<><>-OK | DNS-response | Www.google.com is 22.214.171.124 126.96.36.199 Connecting to www.google.com | 188.8.131.52 |: 80 ... | S-chain | - <- - 10.23.37.3:1080-<><>-184.108.40.206:80-<><>-OK Connected. HTTP request sent, awaiting response ... 200 OK Length: unspecified [text / html] Saving to: `index.html ' [<=>] 6,016 24.0K / s in 0.2s 19:13:21 (24.0 KB / s) - `index.html 'saved 
For this to work, you must specify the proxy server that we want to use in
[ProxyList] Socks5 clientessh 1080
We can also tell you that DNS requests are made remotely:
# Proxy DNS requests - no leak for DNS data Proxy_dns
Also, in the previous output, we have seen several informative messages of the same
wgetin lines marked with strings
|DNS-response|. If we do not want to see them, we can also adjust it in the configuration:
# Quiet mode (no output from library) Quiet_mode