http://localhost:1313/tags/networking/Recent content in Networking on LorbicHugoenWed, 01 Apr 2026 22:00:00 +0530http://localhost:1313/kubernetes-on-wsl2-macos-access/Wed, 01 Apr 2026 22:00:00 +0530http://localhost:1313/kubernetes-on-wsl2-macos-access/<p><strong>TL;DR:</strong> I run <strong>k3s</strong> on a Windows gaming PC via <strong>WSL2</strong> to master Kubernetes networking without cloud costs. This guide details a secure access model using <strong>SSH</strong> and <strong>kubectl port-forward</strong> to bypass NAT boundaries and maintain technical sovereignty.</p> <hr> <p>This guide omits Kubernetes feature tutorials. Instead, it details how to architect an environment where Kubernetes can exist without auxiliary hardware, idle cloud bills, or hidden networking realities.</p> <p>I wanted to learn Kubernetes properly, which meant understanding how <strong>scheduling</strong>, <strong>access paths</strong>, and <strong>network boundaries</strong> behave under real constraints. The problem was simple: I lacked a reasonable execution environment.</p>http://localhost:1313/outline-vpn-over-https/Tue, 12 Aug 2025 00:00:00 +0000http://localhost:1313/outline-vpn-over-https/<h2 id="what-we-are-doing">What We Are Doing<a class="anchorjs-link" href="#what-we-are-doing" aria-label="Link to section: What We Are Doing"></a></h2><p>If you are somewhere that blocks VPNs through deep packet inspection (DPI), SNI filtering, or crude port blocking, the goal is to make your VPN traffic look as boring as possible.<br> The quick win is to put it on port 443, the same port used by HTTPS. That is the lifeline of the modern web, so most firewalls are reluctant to block it.</p>