<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Mab on trustserv.de</title>
		<link>https://trustserv.de/en/tags/mab/</link>
		<description>Recent content in Mab on trustserv.de</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Tue, 01 Sep 2026 13:30:00 +0200</lastBuildDate>
		
			<atom:link href="https://trustserv.de/en/tags/mab/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Homelab Rebuild Part 9: The Devices That Can&#39;t Do 802.1X</title>
				<link>https://trustserv.de/en/post/homelab-teil-9/</link>
				<pubDate>Tue, 01 Sep 2026 13:30:00 +0200</pubDate>
				<guid>https://trustserv.de/en/post/homelab-teil-9/</guid>
				<description>&lt;h2 id=&#34;what-this-is-about&#34;&gt;&#xA;  What this is about&#xA;  &lt;a class=&#34;heading-link&#34; href=&#34;#what-this-is-about&#34;&gt;&#xA;    &lt;i class=&#34;fa-solid fa-link&#34; aria-hidden=&#34;true&#34; title=&#34;Link to heading&#34;&gt;&lt;/i&gt;&#xA;    &lt;span class=&#34;sr-only&#34;&gt;Link to heading&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://trustserv.de/en/post/homelab-teil-7/&#34; &gt;Part 7&lt;/a&gt; ends with a piece of advice: for devices that&#xA;can&amp;rsquo;t do 802.1X, plan a second SSID with a classic shared key, hardwired to an&#xA;untrusted VLAN.&lt;/p&gt;&#xA;&lt;p&gt;I didn&amp;rsquo;t take my own advice.&lt;/p&gt;&#xA;&lt;p&gt;The reason is the same one I used in part 1 to argue against one SSID per VLAN:&#xA;once the assignment is glued to the SSID, every additional trust level needs&#xA;another SSID. My AV receiver and my games console both lack 802.1X, but they are&#xA;explicitly &lt;strong&gt;not&lt;/strong&gt; supposed to share a network. A hardwired SSID would have given&#xA;me exactly the catch-all VLAN I set out to get rid of.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
