https://trustserv.de/en/tags/802.1x/ Recent content in 802.1x on trustserv.de Hugo en-US Mon, 17 Aug 2026 08:45:00 +0200 https://trustserv.de/en/post/homelab-teil-7/ Mon, 17 Aug 2026 08:45:00 +0200 https://trustserv.de/en/post/homelab-teil-7/ <h2 id="what-this-is-about"> What this is about <a class="heading-link" href="#what-this-is-about"> <i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"></i> <span class="sr-only">Link to heading</span> </a> </h2> <p><a href="https://trustserv.de/en/post/homelab-teil-1/" >Part 1</a> established that one SSID per VLAN doesn&rsquo;t work — every SSID costs airtime, and with five or six of them you lose measurable throughput.</p> <p>The alternative is the one companies use: <strong>a single SSID, and the network decides per device.</strong> The device authenticates with its own credentials, a RADIUS server checks them and sends the VLAN assignment back with the answer.</p> https://trustserv.de/en/post/homelab-teil-1/ Sat, 15 Aug 2026 14:52:30 +0200 https://trustserv.de/en/post/homelab-teil-1/ <h2 id="what-this-is-about"> What this is about <a class="heading-link" href="#what-this-is-about"> <i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"></i> <span class="sr-only">Link to heading</span> </a> </h2> <p>My home network grew the way most of them do: add a device, it works, stop thinking about it. Eventually everything hung off one box and lived in one subnet.</p> <p>That works fine for a surprisingly long time. But at some point I wanted to do things the setup had no room for — separate devices from each other, push Wi-Fi clients automatically to where they belong, issue my own certificates. That needs a different foundation.</p>