dave/site
1
0
Fork 0
mirror of https://github.com/davegallant/davegallant.github.io.git synced 2025-08-09 10:02:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

deploy: 5af0df0e5568b5f976b0a52f78c06f5003ccec2b

Browse Source
This commit is contained in:
davegallant
2025-04-21 23:36:13 +00:00
parent a137542529
commit d77caeca2f
87 changed files with 93 additions and 92 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
js/flexsearch.3d18cfe5cabcb74b5b2680cbd8ae6aa72c35abbe94fffa45030fe126138897c8c918aac4c953efe1087fa738d011f4404c5cf915104e9ad804caf8659086fd6e.js → js/flexsearch.de4bafade54c47f36c1540311739bc2a5910ed65875daae3b0d10af870b8b0ed4ae53228529172f7b8d6f49eddfce1f1354d6aa9f75ae48461cf1caf8ca1bd08.js
View File

@@ -6,14 +6,15 @@ Environment# My environment consists of:
Proxmox 8.4 OPNsense 25.1 (Virtual Machine) Ethernet controller: Intel Corporation Ethernet Connection (5) I219-LM Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) Goal# The goal is to upgrade the OPNsense router from a single NIC to two NICs, where each NIC is dedicated to:
WAN: the connection to the internet (via the ONT) LAN: the internal network for computers, phones, iot devices, etc. Having two separate physical interfaces for WAN and LAN creates clear, physical separation between the untrusted external network and trusted internal network at the hardware level. This also should improve performance and throughput since the same physical connection is no longer shared between WAN and LAN.
Device Passthrough# For maximum performance and reduced hypervisor overhead, passing through a physical NIC for WAN directly to the VM seemed to make the most sense, so I passed it through to the OPNsense VM.
After adding the PCI device, I restarted the OPNsense VM and re-configured the WAN to use this device.
I received the WAN IP and everything appeared to be working. After running it for a couple of hours, I checked my instance of speedtest-tracker noticed that the download speeds were significantly slower than historical records:
After switching the WAN back to the original shared NIC, the download speeds returned to more average download speeds.
Realtek drivers# After some searching, I read that installing the OPNsense plugin os-realtek-re can help with stability issues.
I added the PCI device and restarted the OPNsense VM and re-configured the WAN to use this device.
I received the WAN IP and everything appeared to be working. I checked my instance of speedtest-tracker noticed that the download speeds were significantly slower than historical records:
These tests were going through a mullvad relay (which occasionally dips), but these tests were too consistent to be a coincidence.
I then switched the WAN back to the original shared NIC, and the download speeds returned to more average download speeds.
Realtek drivers# I did some searching and read that installing the OPNsense plugin os-realtek-re can help with stability issues.
After installing this plugin and ensuring the kernel module was loaded by following the post-install instructions, the throughput was still much slower than I was expecting.
I was starting to think that there might be a problem with the NIC itself (and began the process to return it to the vendor).
Virtualized NIC with a Linux bridge# As one last shot, I created Linux Bridge in the Proxmox GUI with the Realtek NIC and passed it through to the OPNsense VM:
After re-configuring the WAN interface in OPNsense to use the newly added network device, the download and upload speeds returned to average levels. This also bypasses the need for installing Realtek FreeBSD drivers on the OPNsense VM, since the network device is virtual and managed on the Proxmox host.
I re-configured the WAN interface in OPNsense to use the newly added network device, and the download and upload speeds returned to average levels. This also bypasses the need for installing Realtek FreeBSD drivers on the OPNsense VM, since the network device is virtual and managed on the Proxmox host.
Conclusion# Although I am not sure why passing through a Realtek NIC to an OPNsense VM causes so much degradation in throughput, I am glad that there is a workaround. If I get my hands on another NIC, I will try to see if the issue can be reproduced.
`}).add({id:1,href:"/blog/replicating-truenas-datasets-to-sftpgo-over-tailscale/",title:"Replicating TrueNAS datasets to sftpgo over Tailscale",description:`I’ve recently spun up an instance of TrueNAS SCALE after salvaging a couple hard drives from a past computer build and decided I could use additional network storage for various backups such as Proxmox VMs and home directory backups.
`,content:`I’ve recently spun up an instance of TrueNAS SCALE after salvaging a couple hard drives from a past computer build and decided I could use additional network storage for various backups such as Proxmox VMs and home directory backups.