<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nat-Workaround on /var/log/janio</title><link>https://devops.sarmento.org/en/tags/nat-workaround/</link><description>Recent content in Nat-Workaround on /var/log/janio</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 16 Apr 2026 19:42:00 +0000</lastBuildDate><atom:link href="https://devops.sarmento.org/en/tags/nat-workaround/index.xml" rel="self" type="application/rss+xml"/><item><title>SSH Behind NAT? SSH-J.com Solves It.</title><link>https://devops.sarmento.org/en/posts/ssh-behind-nat-ssh-jcom-solves-it/</link><pubDate>Wed, 25 Mar 2026 22:26:00 +0000</pubDate><guid>https://devops.sarmento.org/en/posts/ssh-behind-nat-ssh-jcom-solves-it/</guid><description>&lt;p&gt;You work remotely, have a server at home, a Raspberry Pi running services, or a machine at the office you need to reach every now and then. The scenario is common and the obvious solution is SSH — already installed, secure, and battle-tested for decades. The problem is that between your machine and the rest of the internet sits a router, a NAT, and possibly an ISP that does not give you a fixed public IP or blocks incoming ports. Suddenly, the most reliable protocol in system administration becomes unreachable from outside your local network.&lt;/p&gt;</description></item></channel></rss>