<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Hardware]]></title><description><![CDATA[Discussions about pfSense hardware support]]></description><link>https://forum.netgate.com/category/6</link><generator>RSS for Node</generator><lastBuildDate>Sat, 16 May 2026 02:22:45 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/category/6.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 10 May 2026 18:21:30 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Intermittent WAN packet loss - wcpu?]]></title><description><![CDATA[Nothing shown there is unexpected. The idle processes shown as using high CPU are normal. That's what shows as using CPU cycles when nothing else requires them.
I assume it was not dropping packets at that time?
You should not run Kea on the 3100. There are known upstream bugs in arm32 that affect it. That wouldn't cause packet loss though.
You should upgrade. 24.03 is now a very old release.
]]></description><link>https://forum.netgate.com/topic/200664/intermittent-wan-packet-loss-wcpu</link><guid isPermaLink="true">https://forum.netgate.com/topic/200664/intermittent-wan-packet-loss-wcpu</guid><dc:creator><![CDATA[stephenw10]]></dc:creator><pubDate>Sun, 10 May 2026 18:21:30 GMT</pubDate></item><item><title><![CDATA[pfsense appliance crashing after being on for days]]></title><description><![CDATA[Exactly how 'frozen' is it? Like the console stops responding?
But, yes, you should upgrade anyway.
]]></description><link>https://forum.netgate.com/topic/200647/pfsense-appliance-crashing-after-being-on-for-days</link><guid isPermaLink="true">https://forum.netgate.com/topic/200647/pfsense-appliance-crashing-after-being-on-for-days</guid><dc:creator><![CDATA[stephenw10]]></dc:creator><pubDate>Thu, 07 May 2026 11:31:55 GMT</pubDate></item><item><title><![CDATA[RTL8126 NIC Speed reduction on 2.8.1 compared to Intel NIC.]]></title><description><![CDATA[No set timeline for that yet.
]]></description><link>https://forum.netgate.com/topic/200585/rtl8126-nic-speed-reduction-on-2.8.1-compared-to-intel-nic.</link><guid isPermaLink="true">https://forum.netgate.com/topic/200585/rtl8126-nic-speed-reduction-on-2.8.1-compared-to-intel-nic.</guid><dc:creator><![CDATA[stephenw10]]></dc:creator><pubDate>Fri, 24 Apr 2026 12:26:32 GMT</pubDate></item><item><title><![CDATA[WatchGuard XTM 5 – Full Repurpose Guide (BIOS Unlock + OPN&#x2F;pfSense Working)]]></title><description><![CDATA[@stephenw10 said in WatchGuard XTM 5 – Full Repurpose Guide (BIOS Unlock + OPNsense Working):

Mmm, I assume pfSense also runs fine there. It does for me.

As does mine..
]]></description><link>https://forum.netgate.com/topic/200481/watchguard-xtm-5-full-repurpose-guide-bios-unlock-opn-pfsense-working</link><guid isPermaLink="true">https://forum.netgate.com/topic/200481/watchguard-xtm-5-full-repurpose-guide-bios-unlock-opn-pfsense-working</guid><dc:creator><![CDATA[chpalmer]]></dc:creator><pubDate>Mon, 06 Apr 2026 16:01:06 GMT</pubDate></item><item><title><![CDATA[7100 to 8200 swap - Success]]></title><description><![CDATA[<p dir="auto">I swapped my 7100 for a 8200.  With help from TAC the config was moved.<br />
For future generations, a WAS-110 (XGS-PON) does work in an 8200.  The only problem is the SFP+ ports are upside down, so the heat sink is down instead of up, this makes it tight for a few ports on my switch which the 8200 sits on.</p>
<p dir="auto"><img src="/assets/uploads/files/1774192559851-c7a1181d-3ecd-4575-8229-9d96d02b5542-img_2953-resized.jpeg" alt="c7a1181d-3ecd-4575-8229-9d96d02b5542-IMG_2953.jpeg" class=" img-fluid img-markdown" /></p>
]]></description><link>https://forum.netgate.com/topic/200398/7100-to-8200-swap-success</link><guid isPermaLink="true">https://forum.netgate.com/topic/200398/7100-to-8200-swap-success</guid><dc:creator><![CDATA[AndyRH]]></dc:creator><pubDate>Sun, 22 Mar 2026 15:17:39 GMT</pubDate></item><item><title><![CDATA[SafeXcel EIP-97 only registering AES-CBC with OCF on SG-2100 (pfSense Plus 24.03)]]></title><description><![CDATA[@JonathanLee said in SafeXcel EIP-97 only registering AES-CBC with OCF on SG-2100 (pfSense Plus 24.03):

At the 'OK' loader prompt (with pfSense Plus Installer USB plugged in):
OK run usbboot

That should be at the uboot (Marvell&gt;&gt;) prompt.
]]></description><link>https://forum.netgate.com/topic/200376/safexcel-eip-97-only-registering-aes-cbc-with-ocf-on-sg-2100-pfsense-plus-24.03</link><guid isPermaLink="true">https://forum.netgate.com/topic/200376/safexcel-eip-97-only-registering-aes-cbc-with-ocf-on-sg-2100-pfsense-plus-24.03</guid><dc:creator><![CDATA[stephenw10]]></dc:creator><pubDate>Tue, 17 Mar 2026 14:09:25 GMT</pubDate></item><item><title><![CDATA[NetGate 1537 running latest pfSense - SFP compat?]]></title><description><![CDATA[@stephenw10 Very cool. Thank you for the assist.
]]></description><link>https://forum.netgate.com/topic/200375/netgate-1537-running-latest-pfsense-sfp-compat</link><guid isPermaLink="true">https://forum.netgate.com/topic/200375/netgate-1537-running-latest-pfsense-sfp-compat</guid><dc:creator><![CDATA[SEWA_Cty]]></dc:creator><pubDate>Mon, 16 Mar 2026 21:42:27 GMT</pubDate></item><item><title><![CDATA[PFSense XG-1540 fails to POST]]></title><description><![CDATA[Well you will need at least some RAM. It's unlikely all RAM sticks would fail though.
Otherwise you might try a different PSU. Beyond that I'm not sure what else you could do. The Supermicro board manual might have some info on the diagnostic LEDs.
]]></description><link>https://forum.netgate.com/topic/200333/pfsense-xg-1540-fails-to-post</link><guid isPermaLink="true">https://forum.netgate.com/topic/200333/pfsense-xg-1540-fails-to-post</guid><dc:creator><![CDATA[stephenw10]]></dc:creator><pubDate>Wed, 11 Mar 2026 12:14:14 GMT</pubDate></item><item><title><![CDATA[SFP Cat6 insert not recognized (I think)]]></title><description><![CDATA[It cannot on those CPUs. It's a limitation of the SoC as noted by Intel:
https://docs.netgate.com/pfsense/en/latest/solutions/netgate-6100/io-ports.html#sfp-ethernet-ports
If the module defaults to the required rate it can work which is why some module do even though we don't officially support it.
I assume you're trying to have it link at 1G and it's failing to link at 10G?
]]></description><link>https://forum.netgate.com/topic/200266/sfp-cat6-insert-not-recognized-i-think</link><guid isPermaLink="true">https://forum.netgate.com/topic/200266/sfp-cat6-insert-not-recognized-i-think</guid><dc:creator><![CDATA[stephenw10]]></dc:creator><pubDate>Sat, 28 Feb 2026 19:23:44 GMT</pubDate></item><item><title><![CDATA[[Solved] Motherboard Replacement and ZFS RAID]]></title><description><![CDATA[In answering my own question, I discovered that the continuous # symbols was not a rebuild and so I restarted and checked the bios.  I changed from Legacy/UEFI to UEFI and the system restarted without a hitch!
A+ pfSense!!!
]]></description><link>https://forum.netgate.com/topic/200243/solved-motherboard-replacement-and-zfs-raid</link><guid isPermaLink="true">https://forum.netgate.com/topic/200243/solved-motherboard-replacement-and-zfs-raid</guid><dc:creator><![CDATA[mgc6288]]></dc:creator><pubDate>Wed, 25 Feb 2026 20:07:59 GMT</pubDate></item><item><title><![CDATA[6100 SFP+ Port negotiation speeds]]></title><description><![CDATA[Hmm, I'm not aware of that specifically. Only that the modules will generally run at their 'native speeds only because the rate cannot be set. For most dual speed modules that means 10G but some will select 1G and run fine.
The actual restriction as noted by Intel is shown here: https://docs.netgate.com/pfsense/en/latest/solutions/netgate-6100/io-ports.html#sfp-ethernet-ports
]]></description><link>https://forum.netgate.com/topic/200227/6100-sfp-port-negotiation-speeds</link><guid isPermaLink="true">https://forum.netgate.com/topic/200227/6100-sfp-port-negotiation-speeds</guid><dc:creator><![CDATA[stephenw10]]></dc:creator><pubDate>Tue, 24 Feb 2026 14:26:48 GMT</pubDate></item><item><title><![CDATA[Homelab Firewall Experiencing Odd Behavior Since Converting Back to CE Build]]></title><description><![CDATA[Yup I'd be amazed if it was anything but soemthing worn and/or blocked in the cooling system.
]]></description><link>https://forum.netgate.com/topic/200220/homelab-firewall-experiencing-odd-behavior-since-converting-back-to-ce-build</link><guid isPermaLink="true">https://forum.netgate.com/topic/200220/homelab-firewall-experiencing-odd-behavior-since-converting-back-to-ce-build</guid><dc:creator><![CDATA[stephenw10]]></dc:creator><pubDate>Mon, 23 Feb 2026 04:18:44 GMT</pubDate></item><item><title><![CDATA[Build help please - urgent]]></title><description><![CDATA[@stephenw10
Thanks again. I just need it to install pfsense. I will be using a HDMI computer monitor.
Then the webgui will take over.
]]></description><link>https://forum.netgate.com/topic/200123/build-help-please-urgent</link><guid isPermaLink="true">https://forum.netgate.com/topic/200123/build-help-please-urgent</guid><dc:creator><![CDATA[Waqar.UK]]></dc:creator><pubDate>Mon, 09 Feb 2026 18:01:28 GMT</pubDate></item><item><title><![CDATA[Netgate 4200 freeze and a possible fix]]></title><description><![CDATA[Just checking in to confirm that everything is still running smoothly without any issues.
I did end up setting up additional services like Avahi but all freezes are history.
]]></description><link>https://forum.netgate.com/topic/200121/netgate-4200-freeze-and-a-possible-fix</link><guid isPermaLink="true">https://forum.netgate.com/topic/200121/netgate-4200-freeze-and-a-possible-fix</guid><dc:creator><![CDATA[belajasmert]]></dc:creator><pubDate>Mon, 09 Feb 2026 17:47:48 GMT</pubDate></item><item><title><![CDATA[Sanity Check My New Build]]></title><description><![CDATA[@stephenw10 Whoops! Should be Xeon E-2174G (4c/8t 3.8/4.7GHz)
]]></description><link>https://forum.netgate.com/topic/200077/sanity-check-my-new-build</link><guid isPermaLink="true">https://forum.netgate.com/topic/200077/sanity-check-my-new-build</guid><dc:creator><![CDATA[MeCJay12]]></dc:creator><pubDate>Wed, 04 Feb 2026 15:39:22 GMT</pubDate></item><item><title><![CDATA[Verification needed: disabling bypasses on CloudGenix ION 3000]]></title><description><![CDATA[OK, complete and total replication. Ran the routine on two more ION 3000 devices, verified the disablement of bypasses by bridging all eight ports on the expansion board into a single network, connecting multiple devices to those ports, and accessing one device from another, including making the remotely accessed device access the Internet.
Found a small refinement: you can actually install pfSense on the device (no need to resort to installing on another device), as long as you remember to use the right settings.
Anyway, here's the refined procedure:
One. Turn off the device (completely, as in, disconnect the power cable) and open up the case (there are four screws holding the top in place, one on each side and two in the back; once you remove the screws, the top slides off).
Two. Disconnect the SATA SSD and remove the CF card.
Three. Reposition a jumper on the expansion board and do some OpenWrt magic. For details on this step, see my post on the OpenWrt forum:
https://forum.openwrt.org/t/report-openwrt-on-cloudgenix-ion-3000/246014
Briefly, you prepare a bootable device with OpenWrt (I used a CF card, but there's no reason you can't use a USB stick), boot the device from it, install three additional packages, make a slight edit to /boot/grub/grub.cfg to configure the disablement of bypasses, reboot the device (which should disable the bypasses), let the boot sequence run, then shut the device down.
Four. Remove OpenWrt media, reconnect the SATA SSD, connect a USB  stick with pfSense installer, and install pfSense. Remember the settings: UFS file system, entire drive, MS-DOS partitions (the layout suggested by the installer should work).
Once the install is complete, shut the device down, disconnect the installer media, and boot the device. It should boot from the SSD, and bypasses should be disabled, so you can assign interfaces and as usual.
Remember, the port map is weird:
                                           = Expansion board =
====== Onboard controllers ======          igb6 igb7 igb8 igb9
igb10 igb11 igb12 igb13 igb0 igb1          igb2 igb3 igb4 igb5 

so by default, the rightmost onboard port (igb1) will be LAN and the one to the left of it (igb0), WAN.
Five. To get the little LCD screen working, install lcdproc and configure it to use parallel port (/dev/lpt0) with 2x20 screen size and the Watchguard Firebox with SDEC driver.
]]></description><link>https://forum.netgate.com/topic/200073/verification-needed-disabling-bypasses-on-cloudgenix-ion-3000</link><guid isPermaLink="true">https://forum.netgate.com/topic/200073/verification-needed-disabling-bypasses-on-cloudgenix-ion-3000</guid><dc:creator><![CDATA[NC1]]></dc:creator><pubDate>Tue, 03 Feb 2026 22:02:03 GMT</pubDate></item><item><title><![CDATA[Intel X550-T2 Dual Port - RJ-45 10G Low Profile PCIe3.0-x4 CNA]]></title><description><![CDATA[@Waqar.UK the X550 is supported well, yes.
]]></description><link>https://forum.netgate.com/topic/200054/intel-x550-t2-dual-port-rj-45-10g-low-profile-pcie3.0-x4-cna</link><guid isPermaLink="true">https://forum.netgate.com/topic/200054/intel-x550-t2-dual-port-rj-45-10g-low-profile-pcie3.0-x4-cna</guid><dc:creator><![CDATA[patient0]]></dc:creator><pubDate>Sat, 31 Jan 2026 21:21:43 GMT</pubDate></item><item><title><![CDATA[igc interfaces not seeing link when plugged into a 2.5G modem]]></title><description><![CDATA[@stephenw10 It could be a combination of a bad patch cable AND a faulty igc3 port on the 6100.  After swapping cables and ports, igc0 sees the LAN and igc1 sees the ISP/WAN.  However, switching the working cable from icg1 to igc3, no link is detected.  @patient0 my WAN connection is pure DHCP.
I'll open a ticket with Netgate.
Thanks, Tim
]]></description><link>https://forum.netgate.com/topic/200051/igc-interfaces-not-seeing-link-when-plugged-into-a-2.5g-modem</link><guid isPermaLink="true">https://forum.netgate.com/topic/200051/igc-interfaces-not-seeing-link-when-plugged-into-a-2.5g-modem</guid><dc:creator><![CDATA[timbaeten]]></dc:creator><pubDate>Sat, 31 Jan 2026 17:54:56 GMT</pubDate></item><item><title><![CDATA[Kernel Panic upgrading from 24.11 to 25.11]]></title><description><![CDATA[@stephenw10 - This is nice. Thank you very much. We will do the upgrade tonight.
]]></description><link>https://forum.netgate.com/topic/199994/kernel-panic-upgrading-from-24.11-to-25.11</link><guid isPermaLink="true">https://forum.netgate.com/topic/199994/kernel-panic-upgrading-from-24.11-to-25.11</guid><dc:creator><![CDATA[jeoff]]></dc:creator><pubDate>Mon, 26 Jan 2026 12:58:11 GMT</pubDate></item><item><title><![CDATA[Port Speed issue on 25.07.1 and Netgate 4200-S]]></title><description><![CDATA[@stephenw10 My experience (posted above), with the older firmware, showed that even if I set 2500BaseT and other side was auto-negotiate I still had flapping.  I still have 1000BaseT set now and it has been stable for months. This is on my WAN side, igc3.
LAN side, igc2, is set to auto-negotiate and other side is 1000BaseT and it has been stable since day one.
Looks like @workaholiker has proven that with new firmware setting speed to 2500Base-T stops flapping.
I also had purchased new 1m Cat6a cables to rule them out.
]]></description><link>https://forum.netgate.com/topic/199946/port-speed-issue-on-25.07.1-and-netgate-4200-s</link><guid isPermaLink="true">https://forum.netgate.com/topic/199946/port-speed-issue-on-25.07.1-and-netgate-4200-s</guid><dc:creator><![CDATA[scruzuser]]></dc:creator><pubDate>Tue, 20 Jan 2026 02:00:02 GMT</pubDate></item><item><title><![CDATA[CPU advice]]></title><description><![CDATA[A x4 PCIe 3.0 slot will pass 32Gbps. That shouldn't be a restriction.
]]></description><link>https://forum.netgate.com/topic/199928/cpu-advice</link><guid isPermaLink="true">https://forum.netgate.com/topic/199928/cpu-advice</guid><dc:creator><![CDATA[stephenw10]]></dc:creator><pubDate>Sat, 17 Jan 2026 15:07:47 GMT</pubDate></item><item><title><![CDATA[High latency to gateway and ISP when multiple switches are connected – possible pfSense overload?]]></title><description><![CDATA[@joy786 said in High latency to gateway and ISP when multiple switches are connected – possible pfSense overload?:

What’s strange is that everything becomes stable as soon as I disconnect any one of my access switches. It doesn’t matter which switch I unplug — the problem immediately disappears.
Current behavior
Ping to pfSense gateway becomes unstable and increases significantly
Ping to public IP / first ISP hop also increases
pfSense CPU usage goes high during the issue
As soon as one switch is disconnected:
CPU drops
Ping stabilizes

This sounds like you are introducing then removing a Layer 2 loop.
]]></description><link>https://forum.netgate.com/topic/199914/high-latency-to-gateway-and-isp-when-multiple-switches-are-connected-possible-pfsense-overload</link><guid isPermaLink="true">https://forum.netgate.com/topic/199914/high-latency-to-gateway-and-isp-when-multiple-switches-are-connected-possible-pfsense-overload</guid><dc:creator><![CDATA[Derelict]]></dc:creator><pubDate>Fri, 16 Jan 2026 15:59:16 GMT</pubDate></item><item><title><![CDATA[pfsense on lanner 7551w]]></title><description><![CDATA[@susamlicubuk
The two rightmost pairs of ports have bypasses on them. You need to disable those bypasses. The steps below assume that you have BIOS in factory configuration. If you already made changes, adjust accordingly.


Turn off the FW-7551.


Set console speed on your computer to 9600 bps and connect your computer to the FW-7551 using its console port.


Start the console software on your computer.


Turn on the FW-7551.


When you see the BIOS prompt asking you to hit Esc or Del, hit Tab. (This is a common occurrence when dealing with BIOS on the console; Tab tends to work best.)


Next, enter the password (usually, it's either Kilimanjaro1 or Cheyenne1). This will get you into BIOS.


In BIOS, go to Advanced.


Under Advanced, select Watchdog mode and set it to Disabled.


Next, still under Advanced, select Generation 2 LAN Bypass Configuration. On the screen that appears next, set LAN3-4 Runtime Bypass and LAN5-6 Runtime Bypass to Disabled. As to the two matching System Off Bypass options, you can leave them enabled (so when the device is off, data will pass through it, as if it were a mere keystone) or disable them (so when the device is off, there will be no data traffic through it).


Next (optionally), hit Esc to return to Advanced and select Serial Port Console Redirection. On the screen that follows, select Console Redirection Settings. On the screen that follows, select Bits per second and set it to your desired value (since pfSense operates at 115200 bps by default, it makes sense to set BIOS to the same data transfer rate).


Hit Esc two or three times to return to the main menu. Then, navigate to Save &amp; Exit and choose Save Changes and Exit.


This should do it.
]]></description><link>https://forum.netgate.com/topic/199818/pfsense-on-lanner-7551w</link><guid isPermaLink="true">https://forum.netgate.com/topic/199818/pfsense-on-lanner-7551w</guid><dc:creator><![CDATA[NC1]]></dc:creator><pubDate>Wed, 14 Jan 2026 14:31:37 GMT</pubDate></item><item><title><![CDATA[QNAP LAN-10G2T-X550]]></title><description><![CDATA[Yes, Windows 11 auto-detected and installed Intel driver for the card.
I'll need to do a test install with CE when I can find some extra time...
]]></description><link>https://forum.netgate.com/topic/199737/qnap-lan-10g2t-x550</link><guid isPermaLink="true">https://forum.netgate.com/topic/199737/qnap-lan-10g2t-x550</guid><dc:creator><![CDATA[mvikman]]></dc:creator><pubDate>Sun, 04 Jan 2026 18:51:14 GMT</pubDate></item><item><title><![CDATA[x540 t2]]></title><description><![CDATA[Yes I would expect it to link at 10G to that switch.
]]></description><link>https://forum.netgate.com/topic/199730/x540-t2</link><guid isPermaLink="true">https://forum.netgate.com/topic/199730/x540-t2</guid><dc:creator><![CDATA[stephenw10]]></dc:creator><pubDate>Sat, 03 Jan 2026 19:24:14 GMT</pubDate></item></channel></rss>