<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nic on davegallant.ca</title><link>https://davegallant.ca/tags/nic/</link><description>Recent content in Nic 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/nic/index.xml" rel="self" type="application/rss+xml"/><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></channel></rss>