Practical aspects of using SSH tunneling are demostrated here, which can potentially replace services like ngrok, localtunnel, DDNS etc.

Setting up ssh server for port forwarding

by default ssh daemon's config are stored in `/etc/ssh/sshd_config` and does not allow port forwarding, to enable it set `AllowTcpForwarding yes` and also `GatewayPorts yes`

Using SSH as a proxy or VPN to use restricted websites

using local and dynamic port forwarding.

TODO
include suitable description and examples.

Using SSH Tunneling to expose local development servers

`$ssh local_port:remote_addr:remote_port username@remote`

Assume an example where we I have a development server running on my local machine on port 8080, (i.e. http://localhost:8080/), and I have ssh access to a remote server(IP 3.182.212.9) that is exposed to the internet.
To tunnel it

1. run below command on your computer.
`$ssh -R 8080:localhost:8080 username@3.182.212.9`
2. in a browser open 3.182.212.9:8080

   ________________           ________________            
  |                |         |                |           
  |  Local server  | <-----> |  Public server | <-------> [ Internet ]
  |________________|         |________________|           
  
  
This capability of ssh makes it pretty useful and competitive to services like ngrok,serveo, localtunnel etc.