A Practical Guide to SSH Tunnels: Local and Remote Port Forwarding

This old internet trick still runs the world — and the comments came in swinging

TLDR: The article explains a handy old trick for reaching hidden apps and machines through a secure connection, with cheat sheets to make the confusing commands easier to remember. Commenters instantly turned it into a debate over manuals vs AI, missing tips, and who really knows the “right” way to do it.

A how-to guide on SSH tunnels — basically a way to safely reach a computer or app hiding behind another computer — somehow turned into a mini comment-section cage match. The article itself is calm, useful, and even self-aware: the author admits they use this trick all the time and still forget which button does what, so they made visual cheat sheets and simple examples. The big pitch? Learning a few old-school connection tricks may be more valuable than chasing the latest shiny AI or cloud fad that could vanish by next season. That alone set the mood: grandpa tech is back, and it’s smug.

Then the crowd showed up. One camp went full grizzled veteran, with a classic eye-roll from teddyh: just read the manual. Another immediately spotted what they called possible AI fingerprints and basically asked, why read this at all if you can just ask a chatbot to explain it? That turned the thread into a subtle showdown between old manuals, modern prompts, and whether tutorials now need to defend their own humanity.

And because no tech thread can stay peaceful, one commenter jumped in with a “nice guide, but you forgot the cool shortcut,” dropping a jump-hosting trick like a mic. Another went deep into weird command inconsistency, asking why one option behaves one way and another doesn’t. Meanwhile, a sysadmin summed up the practical mood: if you work with computers for a living, mastering this stuff is huge return on investment. In other words: the article taught people how to open hidden doors, but the comments were really about who gets to be the smartest person in the room.

Key Points

  • The article explains SSH tunnels with an emphasis on local and remote port forwarding and how to remember the correct SSH flags.
  • It uses a four-host lab environment spanning home, public, and private VPC networks to illustrate how traffic flows through SSH tunnels.
  • Local port forwarding with `ssh -L` is described as sending traffic from a local port to a remote address and port reachable from the SSH-connected remote machine.
  • A lab example shows a web server bound only to `127.0.0.1:80` on a remote host, unreachable via its public IP but accessible locally on the workstation after forwarding to `localhost:8080`.
  • The tutorial notes that `ssh -L` can forward traffic not only to the SSH server itself but also to another machine reachable from that server, enabling bastion-host access patterns.

Hottest takes

“It’s amazing what you can learn by reading the manual.” — teddyh
“obvious AI tells at the top” — trollbridge
“the article mentions bastions, but no jumphosting?” — chasil
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.