I successfully configured the QLogic QLE8152. The issue with "if_qlxge_load="YES"" not working stems from the absence of the if_qlxge.ko module in the pfSense release. My initial solution was to install FreeBSD 14.0 and manually copy the module to boot/kernel. However, this approach failed due to a version mismatch error when attempting to load it with "kldload."

To resolve this, I took the following steps on a fresh installation of FreeBSD 14.0:
Cloned the FreeBSD source repository from the pfSense GitHub:

cd /usr
git clone git@github.com:pfsense/FreeBSD-src.git
cd FreeBSD-src

Switched the branch from master to the version I'm using, in this case, RELENG_2_7_2

git checkout RELENG_2_7_2
Added the qlxge module to the GENERIC configuration file as per the documentation (https://man.freebsd.org/cgi/man.cgi?query=qlxge&sektion=4&format=html):

device qlxge

Executed the following commands:

make buildkernel

After the kernel was built, use make installkernel to copy the new kernel and modules to boot/kernel.

Copied if_qlxge.ko to pfSense and added "if_qlxge_load="YES"" to /boot/conf/loader.conf.

Rebooted the system.

For your convenience, I've attached the module for the 2.7.2 version: if_qlxge.zip.
if_qlxge.zip

@VW_Factor said in NBASE-T Support for Intel X550:

@stephenw10 Yep. I've opened a support ticket with Netgate and they told me will transfer the TAC Lite to a new hardware ID.

Also looks like Intel-X710-T2L is also supported without the hacks.

Interesting, I wonder who you got in support. I didn't expect a response today, however I did get a response and..

I was told this morning (after a hardware change) that Netgate would not transfer to the new NDI.

I opened a ticket with Netgate support several days ago and they said they will do it as a one time courtesy.

@AlexanderL Good luck.

@SteveITS Great news, thank you.

It's unlikely that will be possible on the 6100, the blinkboot bios doesn't have much customization ability. But perhaps that could be added to future devices.

@InstanceExtension said in PSA: Do not attempt Intel NVM Updates on NICs embedded onto Supermicro MBs:

Patrick Kennedy February 7, 2023 At 9:41 am

Ok, understood - these 2 interfaces are hanging off OpenFabric rather than PCIe - so not exactly short of bandwidth then!

☕️

Just to be clear the workstations using a VPN are using the OpenVPN link on firewall? Rather than VPNs from each workstation directly?

@sjstein There are a few, I've used https://docs.netgate.com/pfsense/en/latest/monitoring/graphs/bandwidth-usage.html#bandwidthd. If memory serves it only works on one interface.

@stephenw10 I have the cron job for it set to scrub once a month.

In general those NICs are compatible. If you're running Proxmox though it has to be compatible there.

Yes we need to know the total bandwidth the firewall will be required to pass. And if you're using VPNs what bandwidth does the VPN have to pass. All of it? Just for remote access?

Probably.

It's not ideal though. Intel NICs are better supported in general. Raid controllers can be an issue, it's almost always better to disable them and use a ZFS mirror instead if you need raid.
The graphics hardware should be irrelevant.
It's probably massively overpowered for a firewall!

If it supports FreeBSD pfSense will run there. I don't see that listed but it's probably just untested.

Steve

I bought a usb to ethernet adapter (two actually) set it to a simple static IP like 192.168.1. 40/24. Pfsense couldn't ping my connected laptop (192.168.1.41/24) and my laptop couldn't ping pfsense. Verified cables were good, both devices could ping THEMSELVES, even switched usb to ethernet adapters and verified mac addresses were seen using arp -a. But, still no pings.

So, from the menu i did a reset. And reconfigured pfsense to be the DHCP server and use the usb to ethernet adapter interface. BINGO, i can ping back and forth. I can also access the gui!

Over first hurdle, now find out how to upgrade to Plus.

Thank you for your help guys/gals.

First check the system logs for watchdog timeouts from the Realtek driver.

If you do see those you can try the alternative re(4) driver.

Steve

Had you connected to the console before?

What do you see when you try to connect to the console?

You're going to need a functioning serial console connection to either recover it or to reinstall clean.

Steve

Yup, you could certainly do that. Though I would personally choose any other hypervisor.

But I would test FreeBSD 14 on it bare metal if you can. If it throws the same panic there we can open an upstream bug for it.

Steve

Yes, only the x550 supports N-baseT like that.

@stephenw10 Thanks for the info. I only have a low profile expansion slot available on my pfSense box. I found a low profile bracket on the popular online auction site and got it for a few bucks, then I can try it once it comes in the mail. FWIW Amazon lists it as a currently available product priced at $676 (!) so there might be support for it.

Make sure the IP it's giving you is not conflicting with any other subnet on the firewall.