<?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>Vmware on Bill's Blog</title><link>https://billalrehmani.pages.dev/tags/vmware/</link><description>Recent content in Vmware on Bill's Blog</description><image><title>Bill's Blog</title><url>https://billalrehmani.pages.dev/images/eft-bg.jpg</url><link>https://billalrehmani.pages.dev/images/eft-bg.jpg</link></image><generator>Hugo</generator><language>en-AU</language><lastBuildDate>Sun, 12 Jul 2026 21:30:00 +1000</lastBuildDate><atom:link href="https://billalrehmani.pages.dev/tags/vmware/index.xml" rel="self" type="application/rss+xml"/><item><title>Virtual VLAN Segmentation on pfSense — Three Isolated Zones, No Managed Switch</title><link>https://billalrehmani.pages.dev/posts/vlan-segmentation-pfsense/</link><pubDate>Sun, 12 Jul 2026 21:30:00 +1000</pubDate><guid>https://billalrehmani.pages.dev/posts/vlan-segmentation-pfsense/</guid><description>Building three firewall-isolated network segments — Trusted, IoT, and Guest — entirely in virtual machines, with no managed-switch hardware, and proving the isolation holds.</description></item><item><title>Debugging a Dead VMware NAT and Hardening My pfSense Containment Lab</title><link>https://billalrehmani.pages.dev/posts/pfsense-lab-recovery-and-hardening/</link><pubDate>Thu, 02 Jul 2026 21:46:00 +1000</pubDate><guid>https://billalrehmani.pages.dev/posts/pfsense-lab-recovery-and-hardening/</guid><description>A Windows update silently re-enabled the hypervisor and killed my VMware lab&amp;#39;s networking. The diagnosis, the fix, and the pfSense rebuild — bridged WAN plus egress rules — that came out of it.</description></item></channel></rss>