ssh-dev-suite/tunnel

SSH tunnel lifecycle management automates creating and tracking background port forwarding processes. It launches tunnels via profile configurations, records active sessions to ~/.ssh/tunnels.json, and provides commands to stop or list running tunnels for stable remote access.

The best way to set up local port forwarding and SOCKS proxy profiles is using a dedicated tunnel script. You specify a profile name and target host:port to quickly establish background SSH connections, bypassing manual configuration for reliable remote DevOps workflows.

Yes, you need python, ssh, and sshpass installed to automate SSH reverse proxy and tunnel creation. These dependencies allow the script to handle authentication and execute the underlying SSH commands required for managing local and remote port forwards.

You can track active SSH tunnels and clean up invalid sessions using built-in status tracking. The system records all active port forwarding sessions in ~/.ssh/tunnels.json, enabling you to list running tunnels and automatically clean up orphaned or invalid connections.

Yes, you can configure a single profile to handle local port forwarding, remote port forwarding, and SOCKS proxy modes. The tunnel script applies these configurations to launch background SSH processes suitable for various remote-access scenarios.

Manually configured SSH tunnels often drop because they lack lifecycle management and auditable tracking. Using a tunnel script maintains stable connections by running processes in the background and actively tracking their status in a centralized JSON registry.