<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gns3 on Jeremiah Windle</title><link>https://7f57629a.jeremiahwindle.pages.dev/tags/gns3/</link><description>Recent content in Gns3 on Jeremiah Windle</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 15 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://7f57629a.jeremiahwindle.pages.dev/tags/gns3/index.xml" rel="self" type="application/rss+xml"/><item><title>My CCNA Study Plan: Resources, Schedule, and How I'm Using Physical Lab Gear</title><link>https://7f57629a.jeremiahwindle.pages.dev/blog/ccna-study-plan/</link><pubDate>Thu, 15 Jan 2026 00:00:00 +0000</pubDate><guid>https://7f57629a.jeremiahwindle.pages.dev/blog/ccna-study-plan/</guid><description>Target date: June 2026. Here&amp;rsquo;s the actual plan — resources, schedule, lab setup, and where I&amp;rsquo;m struggling.
Why the CCNA Matters for Me Specifically I&amp;rsquo;ve been managing Cisco Meraki, Fortinet, and UniFi networks across 40+ client organizations for four years. I can configure a FortiGate firewall policy, troubleshoot a VLAN trunk, set up a site-to-site VPN, and triage a flapping BGP session at 2am. The CCNA doesn&amp;rsquo;t teach me most of this — I&amp;rsquo;m already doing it.</description></item></channel></rss>