Tunnel goes up to the host db access via the proxy command. The connection looks like the ASCII art below. The comments, agent forwarding must be enabled on the bastion hosts to Host and have the appropriate keys loaded. L 6035:DBHOST:3306 For a password less login peagent must be running on the desktop With the -nc option to create a tunnel up to the db access host.įor your topology the command executed on desktop machines this on theĬommand prompt looks like this: plink -A ^ Then click the 'Add' button and it will be added to the list of tunnels. Then enter the destination IP address (10.10.1.143), followed by a colon then the port number (1433). It doesĮxecute a local command and uses it as a proxy. To add a tunnel, enter a port number into the 'source port' field (1435 in our example) this is the port on the local machine you will connect to. Unfortunately there is not much help for the -proxycmd option. This works much better than trying to reconfigure the whole VPN setup, which is tricky. Using this new functionality yields a more robust less Option 2: Through a SSH tunnel (say Secure Shell tunnel) As you only wanna route one specific port you need to do this through a SSH tunnel to the other server. L $ the release of PuTTY 0.68 plink got a new command line optionĬalled -proxycmd. I am looking for a putty/plink solution for use for access from windows boxes. I am able to connect to it with ssh from my Mac (code shown below), so I know that the current configuration of the boxes permits this kind of access. What is the (probably very lengthy) putty and/or plink command line that will enable this?įrom my interpretation of the manual, I've tried this: plink -ssh -2 -i C:\temp\key.ppk -agent -A -t -l user -L 6035:127.0.0.1:6035 ssh -v -L 6035:DBHOST:3306 gets me to the bastion, but it then looks for a private key on the bastion to make the connection to db access. ppk files for the private keys that the script can refer to. To make this as easy to deploy as possible, I want to specify all the configuration on the command line without referring to any saved session data configured in the Putty UI. (For example Source port: 5050) Next, In the Destination field, enter the destination address followed by the port number. In the Source port field, enter the port number to use on your local system. Select Local to define the type of SSH port forward. Navigate to the Connection > SSH > Tunnels. My co-workers will then use this connection in a desktop db query tool. In the left sidebar under the Category options. Under List scope, select the compartment where the bastion was created. To connect to a Windows instance using an RDP client and a Port Forwarding session: Open the navigation menu and click Identity & Security. I need to write a script for some co-workers to connect over the following topology, using a private key for authentication (the same key for each person works on both bastion and db access): ┌────────────┐ ┌────────────┐ ┌────────────┐ ┌────────────┐ To create the SSH tunnel using PuTTY instead of OpenSSH (the ssh command), see Connect to Windows using RDP and PuTTY.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |