I haven't yet done this myself so I am not speaking from experience. You might be able to use "Secure Socket Funneling", but it requires setting up a server somewhere that both your socks client and your windows client can reach, and it requires running the SSF client on your windows client.You could try to find a later version of PLINK hoping that the SOCKS feature has been added to it like it has in OpenSSH 7.6+.You could identify an existing socks proxy that is already doing what you want.You could identify another server on the same network as your windows client that you can connect to with PLINK and run your SOCKS proxy there.You could install an SSH server on your windows client and use localhost above.1, 2, and 3 work with the changes outlined above, while 4 and 5 require research. Alas, this is only available in tools that are build with OpenSSH 7.6+, AFAIK. and the SSH client would act as the proxy server (no need for a separate proxy server). To set up port forwarding in PuTTY over an SSH VPN connection, you will need to follow these steps: Start PuTTY and open the Configuration window. If you do, change it to AllowTCPForwarding yes and restart the SSH server service. If you were using OpenSSH 7.6 or later, the SSH client does have the SOCKS feature, meaning you could connect back to your client box with the command. If you are getting a message indicating the server has disabled port forwarding do you have AllowTCPForwarding no in the SSHD configuration file The configuration file will likely be /etc/ssh/sshdconfig on a Linux SSH server. Without an SSHd to connect to, you can't do it because PLINK (0.63) is a client that does not have a SOCKS implementation. For 'Destination', enter the destination address and port in the form remoteaddress:remoteport. Furthermore, if you don't know of any SOCKS proxy's serving that network, your options are greatly reduced. For example, localhost does not have an SSHd (server) running and you don't have an account on another SSH enabled server on that network. So, a problem often arises when you don't have an SSH Server on the targeted network that you can connect to. But, to accomplish your goal, which ever server you choose must be on the network you want to proxy. You can replace localhost with another SSH server that can do Dynamic Port Forwarding or you can forward traffic to a SOCKS proxy server. Plink.exe -N -L 8888:SOCKSPROXYIP:SOCKPORT ![]() # when a dedicated SOCKS proxy server is available Plink.exe -N -D 127.0.0.1:8888 -P 22 localhost If you just want to access your pi, easiest method is to forward the pi ssh port through your router. What you would need is the following: plink.exe -N -R 2222:127.0.0.1:8888 -P 22 REMOTEIP ![]() In the forward port in the PuTTY I set that putty. And that won't accomplish the reverse dynamic port forwarding you were hoping for. So I do the following steps: I use the PuTTY and create a tunnel from the Linux server to the IBM blade center management VIA port 443. This is an old question, but it keeps coming up.Īs mentioned in the comments to your question, your attempts result in a dynamic port forward to the system you wish to initiate the communications from (the SOCKS client).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |