fleet-tunnel

Establish autossh-based SSH tunnels for NATS and HTTP traffic on macOS and Linux nodes.

2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/supportersimulator/multi-fleet --skill fleet-tunnel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fleet-tunnel
Source: https://github.com/supportersimulator/multi-fleet/tree/main/skills/fleet-tunnel
Command: npx skills add https://github.com/supportersimulator/multi-fleet --skill fleet-tunnel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

SSH tunnels carry fleet traffic through restricted networks when non-SSH ports are blocked, avoiding direct exposure and enabling communication.

Core Features & Use Cases

  • Setup autossh-based tunnels between worker and chief, forwarding NATS and Chief relay ports to localhost on the worker.
  • Manage tunnels with start, stop, status, restart, and uninstall commands; supports daemon persistence and environment overrides.
  • Configuration-driven operation reading from .multifleet/config.json, with prerequisites and environment variables for flexibility in varied networks.

Quick Start

Run the installer to configure and start the SSH tunnel on the worker node using bash scripts/fleet-tunnel.sh install.

Frequently Asked Questions about fleet-tunnel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I establish SSH tunnels for fleet traffic through restricted networks with strict firewalls?

You can establish secure SSH tunnels by using autossh to route NATS and HTTP traffic, forwarding blocked ports to localhost. This approach avoids direct exposure and enables communication across strict firewalls and NATs.

When do I need SSH tunneling for NATS and HTTP traffic in my fleet?

You need SSH tunneling when non-SSH ports are blocked by restricted networks, strict firewalls, or NATs. It bridges worker and chief nodes by securely forwarding NATS and Chief relay ports to localhost.

Can I run autossh tunnels as a persistent daemon on macOS and Linux nodes?

Yes, autossh tunnels can persist as a daemon across both macOS and Linux nodes. The setup provides automated provisioning and reads configuration from a .multifleet/config.json file for per-node operation.

How do I manage and monitor the status of SSH tunnels across my fleet nodes?

You can manage SSH tunnels using a CLI that offers start, stop, status, restart, and uninstall commands. This allows direct management of daemon persistence and environment overrides for each node.

What is the best way to set up automated SSH tunnels without manual intervention?

The best way is running an installer script that configures and starts the SSH tunnel automatically. It applies environment overrides and reads from a centralized config.json to provision per-node tunnels.