Tunnelling UDP Traffic Through An SSH Connection: Difference between revisions
| Line 21: | Line 21: | ||
</div> | </div> | ||
In this example '''SSH''' is being '''NATed''' through a firewall. The '''SSH''' listening port is: "'''31222'''". We have choosen to use TCP port forward the "'''''non-used'''''" '''TCP''' port: "'''9999'''". The remote NST probe's IP address is: "'''55.44.22.178'''". | In this example '''SSH''' traffic is being '''NATed''' through a firewall. The '''SSH''' listening port is: "'''31222'''". We have choosen to use TCP port forward the "'''''non-used'''''" '''TCP''' port: "'''9999'''". The remote NST probe's IP address is: "'''55.44.22.178'''". | ||
Revision as of 11:28, 22 March 2007
Overview
This section describes how to use NST to tunnel a UDP traffic conversation through a SSH connection. For our example we will tunnel IPMItool traffic (UDP Port: 623) through an SSH connection to a Sun Fire X4200 server's Integrated Lights Out Manager (ILOM) service processor network interface. Three systems are involved, 2 NST probes and the x4200 server. Reference information was taken from: "Performing UDP tunneling through an SSH connection".
Step By Step:
Tunnel A TCP Forward Port Through SSH
First we need to establish the tunnel for a "non-used" TCP port from the local NST probe to the remote NST probe which shares the same LAN as the destination x4200 server.
root@55.44.22.178's password: Last login: Thu Mar 22 11:18:59 2007 from cpe-72-222-76-188.nycaper.res.rdr.com =============================================== = Linux Network Security Toolkit (NST v1.5.0) = ===============================================
In this example SSH traffic is being NATed through a firewall. The SSH listening port is: "31222". We have choosen to use TCP port forward the "non-used" TCP port: "9999". The remote NST probe's IP address is: "55.44.22.178".
