Skip to main content

Port Forwarding with a Bastion Host (Accessing a VM on Private IP)

Port Forwarding with a Bastion Host (Accessing a VM on Private IP)



In cloud or private network setups, VMs are often on private subnets for security. Direct access to these VMs isn't allowed from outside. Instead, you use a Bastion Host as a jump point to access the private VM. Port forwarding is a technique that allows you to securely connect to the private VM using the bastion host as a middleman.


Flow Explanation:

  1. Bastion Host: A publicly accessible server in a secure zone that has SSH access to the private network.
  2. VM on Private IP: The machine you want to connect to, which is unreachable directly from outside the network.
  3. Port Forwarding:
    • You create a tunnel (via SSH) from your local machine to the private VM through the bastion host.
    • Your local machine forwards requests to a local port (e.g., localhost:8888) which are routed through the bastion host to the private VM's port (e.g., 192.168.1.50:22).

How to Set Up Port Forwarding

  1. Prerequisites:

    • SSH access to the bastion host.
    • SSH key or credentials for the private VM.
    • A terminal or SSH client.

Command Syntax:


ssh -L [local_port]:[target_vm_ip]:[target_port] [user]@[bastion_host]

Explanation:

  • -L: Specifies local port forwarding.
  • [local_port]: A port on your local machine (e.g., 8888).
  • [target_vm_ip]: The private IP of the VM (e.g., 192.168.1.50).
  • [target_port]: The port you want to forward to (e.g., 22 for SSH, 80 for HTTP).
  • [user]: Your SSH username for the bastion host.
  • [bastion_host]: Public IP or hostname of the bastion host.
  1. Example Command:


    ssh -L 8888:192.168.1.50:22 user@bastion.example.com
    • Connects your local machine's port 8888 to the private VM's port 22 via the bastion host.
  2. Access the Private VM:

    • Open a new terminal.
    • Use SSH to connect to the VM via the forwarded port:

      ssh -p 8888 user@localhost

Example Scenario

  • Bastion Host: Public IP: 35.198.120.10
  • Private VM: Private IP: 192.168.1.100
  • Port to Access: 22 (SSH)

Steps:

  1. Run the following command to set up the tunnel:

    ssh -L 8888:192.168.1.100:22 user@35.198.120.10
  2. In a new terminal, SSH into the private VM:

    ssh -p 8888 user@localhost

Representation:

Here’s a step-by-step flowchart for this scenario:


  1. User's Local Machine:

    • Sends request to localhost:8888.
    • Local forwarding forwards it to the bastion host.
  2. Bastion Host:

    • Receives the forwarded request.
    • Relays it to the private VM (192.168.1.100:22) inside the private network.
  3. Private VM:

    • Processes the request and sends the response back via the same path.






Please do like and subscribe to my youtube channel: https://www.youtube.com/@foalabs If you like this post please follow,share and comment

Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...

How to make flash work on IE or Edge with IE Compatibility

How to make flash work on IE or Edge with IE Compatibility With flash been ended from 1-Jan-2021, many applications using flash have stopped working the way they were built (like OEM, OBIEE, etc). The option you have to upgrade.  This method will give a workaround in IE or Edge in IE compatibility mode without upgrading. 1. Verify you have installed flash.ocx on your desktop. Typically, flash.ocx file is located in C:\Windows\System32\Macromed\Flash or C:\Windows\SysWOW64\Macromed\Flash according to your laptop OS system. 2. Edit mms.cfg from the location as a System Administrator In the case of the 64bit system, it might have mms.cfg under C:\Windows\SysWOW64\Macromed\Flash 3. Add below options into mms.cfg file. Note: AllowListUrlPattern list is an example. The URLs need to be replaced to your hosts those have Flash pages. SilentAutoUpdateEnable=0 AutoUpdateDisable=1 EOLUninstallDisable=1 EnableAllowList=1 AllowListUrlPattern=http://www.google.com/ AllowListUrlPattern=http://goo...