<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>MAC on Why did IT fail</title><link>https://www.why-did-it.fail/tags/mac/</link><description>Recent content in MAC on Why did IT fail</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © 2026 Dominik Textoris (formerly Zorgnotti). All Rights Reserved.</copyright><lastBuildDate>Mon, 07 Oct 2019 00:00:00 +0000</lastBuildDate><atom:link href="https://www.why-did-it.fail/tags/mac/index.xml" rel="self" type="application/rss+xml"/><item><title>An overview of the vSphere MAC address space</title><link>https://www.why-did-it.fail/blog/2019-05-vsphere-mac-address-space/</link><pubDate>Mon, 07 Oct 2019 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2019-05-vsphere-mac-address-space/</guid><description>Recently another TAM requested some infos on this topic in VMware’s slack, finally giving me the push to publish as I had this post for ages in my drafts. Given, it is somewhat of an edge case for only a hand full of customers and the problem itself is not new but here is my take. As always please do your own research before you put this untested into production.</description></item></channel></rss>