<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Proxmox on davegallant.ca</title><link>https://davegallant.ca/tags/proxmox/</link><description>Recent content in Proxmox on davegallant.ca</description><generator>Hugo</generator><language>en</language><copyright>Dave Gallant</copyright><lastBuildDate>Fri, 18 Sep 2026 07:29:01 -0400</lastBuildDate><atom:link href="https://davegallant.ca/tags/proxmox/index.xml" rel="self" type="application/rss+xml"/><item><title>pvectl: A CLI for Managing Proxmox</title><link>https://davegallant.ca/blog/pvectl-a-cli-for-proxmox/</link><pubDate>Mon, 20 Jul 2026 13:00:00 -0400</pubDate><guid>https://davegallant.ca/blog/pvectl-a-cli-for-proxmox/</guid><description>&lt;p&gt;My home Proxmox cluster has grown into two nodes, a few dozen LXC containers, and a handful of VMs. Recently I&amp;rsquo;ve been exploring ways to make this experience more streamlined, especially when creating new containers, shelling into containers, running migrations, restoring from backups, etc. Usually when I need to do this, I either SSH into one of the Proxmox nodes or open up the GUI. When on a node, I usually run &lt;code&gt;pct&lt;/code&gt; or &lt;code&gt;qm&lt;/code&gt;, and then immediately run into the issue: which ID was the thing I actually wanted? Which node was it running on?&lt;/p&gt;</description></item><item><title>Using a Realtek NIC with OPNsense</title><link>https://davegallant.ca/blog/using-a-realtek-nic-with-opnsense/</link><pubDate>Mon, 21 Apr 2025 17:17:46 -0400</pubDate><guid>https://davegallant.ca/blog/using-a-realtek-nic-with-opnsense/</guid><description>&lt;p&gt;For the past few years, I&amp;rsquo;ve been running pfSense (and more recently OPNsense) in a virtual machine within Proxmox. This has been running fine with a single onboard Intel NIC. A few months ago, I upgraded to a machine that has a CPU that supports hardware-accelerated transcoding, has more SATA ports, and has more PCI slots for future expansion. With the goal of having a dedicated NIC for WAN, I bought an inexpensive 1Gbps PCIe NIC (TG-3468) despite reading about some of the concerns around Realtek NICs (sluggish performance, driver instability, and in some cases system crashes).&lt;/p&gt;&#10;&lt;p&gt;I&amp;rsquo;ve been running a Realtek NICs reliably on Linux and Windows desktops, so I figured I could make it work without too much effort, but it turns out Realtek NICs really can be problematic when it comes to FreeBSD-based routers, and commonly documented workarounds did not solve my problems.&lt;/p&gt;</description></item><item><title>Virtualizing My Router with pfSense</title><link>https://davegallant.ca/blog/virtualizing-a-router-with-pfsense/</link><pubDate>Sat, 02 Apr 2022 18:50:09 -0400</pubDate><guid>https://davegallant.ca/blog/virtualizing-a-router-with-pfsense/</guid><description>&lt;p&gt;My aging router has been running &lt;a&#10; href="https://en.wikipedia.org/wiki/OpenWrt"&#10; &#10; &#10; class="link--external" target="_blank" rel="noreferrer"&#10; &#10;&gt;OpenWrt&lt;/a&gt; for years and for the most part has been quite reliable. OpenWrt is an open-source project used on embedded devices to route network traffic. It supports many different configurations and there exists a &lt;a&#10; href="https://openwrt.org/packages/index/start"&#10; &#10; &#10; class="link--external" target="_blank" rel="noreferrer"&#10; &#10;&gt;large index of packages&lt;/a&gt;. Ever since I&amp;rsquo;ve connected some standalone wireless access points, I&amp;rsquo;ve had less of a need for an off-the-shelf all-in-one wireless router combo. I&amp;rsquo;ve also recently been experiencing instability with my router (likely the result of a combination of configuration tweaking and firmware updating). OpenWrt has served me well, but it is time to move on!&lt;/p&gt;</description></item><item><title>Running K3s in LXC on Proxmox</title><link>https://davegallant.ca/blog/running-k3s-in-lxc-on-proxmox/</link><pubDate>Sun, 14 Nov 2021 10:07:03 -0500</pubDate><guid>https://davegallant.ca/blog/running-k3s-in-lxc-on-proxmox/</guid><description>&lt;p&gt;It has been a while since I&amp;rsquo;ve actively used Kubernetes and wanted to explore the evolution of tools such as &lt;a&#10; href="https://helm.sh"&#10; &#10; &#10; class="link--external" target="_blank" rel="noreferrer"&#10; &#10;&gt;Helm&lt;/a&gt; and &lt;a&#10; href="https://tekton.dev"&#10; &#10; &#10; class="link--external" target="_blank" rel="noreferrer"&#10; &#10;&gt;Tekton&lt;/a&gt;. I decided to deploy &lt;a&#10; href="https://k3s.io"&#10; &#10; &#10; class="link--external" target="_blank" rel="noreferrer"&#10; &#10;&gt;K3s&lt;/a&gt;, since I&amp;rsquo;ve had success with deploying it on resource-constrained Raspberry Pis in the past. I thought that this time it&amp;rsquo;d be convenient to have K3s running in a LXC container on Proxmox. This would allow for easy snapshotting of the entire Kubernetes deployment. LXC containers also provide an efficient way to use a machine&amp;rsquo;s resources.&lt;/p&gt;</description></item><item><title>What to Do with a Homelab</title><link>https://davegallant.ca/blog/what-to-do-with-a-homelab/</link><pubDate>Mon, 06 Sep 2021 01:12:54 -0400</pubDate><guid>https://davegallant.ca/blog/what-to-do-with-a-homelab/</guid><description>&lt;p&gt;A homelab can be an inexpensive way to host a multitude of internal/external services and learn &lt;em&gt;a lot&lt;/em&gt; in the process.&lt;/p&gt;</description></item></channel></rss>