The best choice is to use Firefox, because Firefox allows you to configure the browser to also send DNS requests through the proxy. If you use Internet Explorer, your DNS requests are still made via the local network you connect from and thus can still be monitored. Perhaps you are connecting from a hotel, a client site, or from work (you didn't learn that from me) and you do not want others monitoring your traffic. It is also useful if you are surfing on a network where you may be concerned about others observing your traffic. If you are able to get out on port 22 (or any other port, you'll just have to set up your SSH server accordingly), then you'll be able to surf wherever you want without issue through the dynamic tunnel. You may be on a network with some sort of firewall or content filtering that you wish to bypass.
#WINDOWS SSH TUNNEL WINDOWS#
So in the example I'm going to provide, we will say the home network has two computers. One is a Linux box running the SSH server and the other is a Windows box with Remote Desktop enabled. We want to set up two tunnels: a dynamic tunnel and a local tunnel to connect to the Windows machine via Remote desktop. I won't go through any examples on setting up a remote port in this article. You are probably less likely to use this, but it would allow machines on the SSH server network to access a machine and port on the network where your SSH client resides.
#WINDOWS SSH TUNNEL HOW TO#
One useful example that I will show you is how to connect to a Windows computer running Remote Desktop. Local - A local tunnel will allow you to connect to the specified port on a machine residing on the same network as the SSH server.You can then configure applications that support SOCKS proxies (such as a web browser) to take advantage of it. I'll demonstrate how to set up Firefox to work through a dynamic tunnel. Dynamic - This acts as a SOCKS proxy that can be used to tunnel traffic through the network where the SSH server resides.
0 kommentar(er)
