Reenvisioning SSH with ShellHub
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.
Infos
- ShellHub: https://shellhub-io.github.io
- ShellHub GitHub Repository: https://github.com/shellhub-io
- Docker: https://www.docker.com
- Compatability Matrix: https://docs.docker.com/compose/compose-file/compose-versioning/
- Docker Compose GitHub Repository: https://github.com/docker/compose/releases
- Connecting to a ShellHub Device: https://shellhub-io.github.io/guides/connecting-device
« Previous 1 2 3
Buy this article as PDF
(incl. VAT)
Buy Linux Magazine
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.
News
-
Linux Servers Targeted by Akira Ransomware
A group of bad actors who have already extorted $42 million have their sights set on the Linux platform.
-
TUXEDO Computers Unveils Linux Laptop Featuring AMD Ryzen CPU
This latest release is the first laptop to include the new CPU from Ryzen and Linux preinstalled.
-
XZ Gets the All-Clear
The back door xz vulnerability has been officially reverted for Fedora 40 and versions 38 and 39 were never affected.
-
Canonical Collaborates with Qualcomm on New Venture
This new joint effort is geared toward bringing Ubuntu and Ubuntu Core to Qualcomm-powered devices.
-
Kodi 21.0 Open-Source Entertainment Hub Released
After a year of development, the award-winning Kodi cross-platform, media center software is now available with many new additions and improvements.
-
Linux Usage Increases in Two Key Areas
If market share is your thing, you'll be happy to know that Linux is on the rise in two areas that, if they keep climbing, could have serious meaning for Linux's future.
-
Vulnerability Discovered in xz Libraries
An urgent alert for Fedora 40 has been posted and users should pay attention.
-
Canonical Bumps LTS Support to 12 years
If you're worried that your Ubuntu LTS release won't be supported long enough to last, Canonical has a surprise for you in the form of 12 years of security coverage.
-
Fedora 40 Beta Released Soon
With the official release of Fedora 40 coming in April, it's almost time to download the beta and see what's new.
-
New Pentesting Distribution to Compete with Kali Linux
SnoopGod is now available for your testing needs