<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://henryguidry.org/feed.xml" rel="self" type="application/atom+xml" /><link href="https://henryguidry.org/" rel="alternate" type="text/html" /><updated>2026-09-30T03:08:44+00:00</updated><id>https://henryguidry.org/feed.xml</id><title type="html">Henry Guidry</title><subtitle>Cybersecurity student at Christopher Newport University writing about homelabs, network defense, and the things I break while learning.</subtitle><author><name>Henry Guidry</name><email>guidryhenry77@gmail.com</email></author><entry><title type="html">Welcome to my blog</title><link href="https://henryguidry.org/blog/2026/09/29/welcome-to-my-blog.html" rel="alternate" type="text/html" title="Welcome to my blog" /><published>2026-09-29T00:00:00+00:00</published><updated>2026-09-29T00:00:00+00:00</updated><id>https://henryguidry.org/blog/2026/09/29/welcome-to-my-blog</id><content type="html" xml:base="https://henryguidry.org/blog/2026/09/29/welcome-to-my-blog.html"><![CDATA[<p>This is where I’ll be writing about what I’m building and learning in cybersecurity.</p>

<!-- TODO: rewrite in your own voice. -->

<h2 id="what-to-expect">What to expect</h2>

<ul>
  <li><strong>Homelab write-ups.</strong> How my Proxmox lab is put together, and what broke along the way.</li>
  <li><strong>Competition notes.</strong> Lessons from CCDC and CTF-style challenges.</li>
  <li><strong>Concept breakdowns.</strong> Networking and security topics I’m studying, explained plainly.</li>
</ul>

<p>If something here helps you, or you spot a mistake, reach out.</p>]]></content><author><name>Henry Guidry</name><email>guidryhenry77@gmail.com</email></author><category term="blog" /><category term="intro" /><category term="meta" /><summary type="html"><![CDATA[What this site is and what's coming next.]]></summary></entry><entry><title type="html">Building my Proxmox cybersecurity homelab</title><link href="https://henryguidry.org/projects/2026/09/28/building-my-proxmox-homelab.html" rel="alternate" type="text/html" title="Building my Proxmox cybersecurity homelab" /><published>2026-09-28T00:00:00+00:00</published><updated>2026-09-28T00:00:00+00:00</updated><id>https://henryguidry.org/projects/2026/09/28/building-my-proxmox-homelab</id><content type="html" xml:base="https://henryguidry.org/projects/2026/09/28/building-my-proxmox-homelab.html"><![CDATA[<p>My lab runs on a single Proxmox host I call <code class="language-plaintext highlighter-rouge">lanServer</code>. I built it following <em>The Homelab Almanac</em> by Michael Taggart.</p>

<!-- TODO: add hardware specs, why you built it, and screenshots. -->

<h2 id="network-layout">Network layout</h2>

<p>Everything routes through an OPNsense VM, with three bridges keeping traffic separated.</p>

<pre><code class="language-mermaid">flowchart LR
  WAN((WAN)) --&gt; OPN[OPNsense router]
  OPN --&gt; INFRA[Infrastructure&lt;br/&gt;192.168.99.0/24]
  OPN --&gt; ISO[IsolationLab&lt;br/&gt;10.1.99.0/24]
  INFRA --&gt; JB[KDE Neon jumpbox]
  INFRA --&gt; SPL[Splunk SIEM]
  ISO --&gt; KALI[Kali]
  ISO --&gt; AD[Active Directory lab]
</code></pre>

<table>
  <thead>
    <tr>
      <th>Bridge</th>
      <th>Subnet</th>
      <th>Purpose</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>WAN</td>
      <td>upstream</td>
      <td>Internet uplink</td>
    </tr>
    <tr>
      <td>Infrastructure</td>
      <td>192.168.99.0/24</td>
      <td>Management and core services</td>
    </tr>
    <tr>
      <td>IsolationLab</td>
      <td>10.1.99.0/24</td>
      <td>Attack and target machines</td>
    </tr>
  </tbody>
</table>

<!-- TODO: double-check which VMs live on which bridge and fix the diagram above. -->

<h2 id="infrastructure-as-code">Infrastructure as code</h2>

<p>Once the core was up, I automated builds instead of clicking through installers:</p>

<ol>
  <li><strong>Packer</strong> builds VM templates.</li>
  <li><strong>Terraform</strong> provisions VMs on Proxmox from those templates.</li>
  <li><strong>Ansible</strong> configures them after boot.</li>
  <li><strong>HashiCorp Vault</strong> holds secrets.</li>
</ol>

<h2 id="things-that-broke">Things that broke</h2>

<p><strong>KDE login loop after <code class="language-plaintext highlighter-rouge">pkcon update</code>.</strong> The jumpbox stopped letting me log in after an update. I rolled back to a Proxmox snapshot, which is the best argument I know for taking snapshots before every update.</p>

<p><strong>Login loop after <code class="language-plaintext highlighter-rouge">chsh</code> to fish.</strong> Changing the default shell locked me out of the desktop session. Lesson: test a new login shell in a terminal before making it the default.</p>

<h2 id="whats-next">What’s next</h2>

<!-- TODO: your next steps. -->]]></content><author><name>Henry Guidry</name><email>guidryhenry77@gmail.com</email></author><category term="projects" /><category term="homelab" /><category term="proxmox" /><category term="networking" /><category term="iac" /><summary type="html"><![CDATA[A segmented lab with OPNsense, Splunk, and an Active Directory environment, provisioned with Packer, Terraform, and Ansible.]]></summary></entry></feed>