Network Tweaks

To connect to your ShellHub server from outside the LAN, assign a static IP address to the machine running ShellHub. Then follow the router's manual for how to configure port forwarding on TCP port 22 for traffic addressed to the ShellHub server. (TCP port 22 is the default port for SSH, but you can also change the port assignment using the Docker Compose YAML file.) You only need to configure remote access through the firewall to the ShellHub server, and then you can connect to other devices on your LAN via ShellHub.

I made a point of mentioning the localhost change that you'll need to make. Aside from the simple router change, the other thing to do is, where possible, add a local alias for the ShellHub server's IP address in the /etc/hosts file on any devices that are running a ShellHub agent. Or, you could, of course, create a DNS entry somehow that points at the static LAN IP address. Adding a reference to the ShellHub server in the host's file or a DNS record will allow you to address the server by hostname rather than IP address.

Conclusion

Now that you have walked through the quick and simple setup of ShellHub, I hope you will be tempted to use it. It's slick, lightweight, and under active development. ShellHub lets you access multiple devices on your LAN through SSH with minimal firewall complications. You could also use ShellHub within the LAN itself, with no public access, if you just need a way for local devices to communicate.

Centralized management via a nicely crafted user interface offers easier admin for multiple devices. ShellHub provides a clever route to fixing a problem that's been around for a while. I hope you enjoy using it.