@w0w said in pfSense 5Gb/s Ethernet NIC: @Craash X710-T2L or T4L should support directly with latest firmware, but really don't know about FreeBSD and some OEM versions like Dell, have seen some 10/1 Gbe versions only. Late to the party with this reply but you can flash the Dell versions of the X710-T2L and T4L to Intel firmware without too much hassle. This will enable the missing 2.5Gbps and 5Gbps speeds. https://forum.level1techs.com/t/crossflashing-intel-official-firmware-on-dell-lenovo-pcie-x710-da2-nics-solved/196357/7 Little bit of reading but it works great. I used Linux but the tools are available for FreeBSD too. I've done a T4L and a T2L and both worked as expected.

@stephenw10 You are right Stephen, I forgot about the issues with N100.

Not really. Only QAT based devices would really make much sense these days and I don't think I've ever seen one on an mPCIe card. Back in the day people used to use Hifn cards. But those are pretty much ancient at this point! I believe we removed the drivers since it eventually started causing problems. https://redmine.pfsense.org/issues/11426 Though we still build the modules for those if you really wanted to try it.

@stephenw10 Hmm i'm pretty sure it was the serial image. To be sure, i'm going to rufus the thumbdrive again and make certain its the serial image. Then i'll boot the laptop again with the setup and install to the mSATA. Going to take screenshots of securecrt when the m270 boots this time too.

Thought I would follow up on this topic: I ended up deciding to add a 10Gbit RJ45 card to the firewall so that the connection between ONT and firewall is copper to copper. Unfortunately, I still saw the disconnection issue described in the original post, which essentially rules out that it was a problem with SFP28 cages and/or transceiver. My next thought was that maybe it's issue with auto-negotiation of the link speed between firewall and ONT. I decided to force the speed on the firewall side to 10Gbit vs. Default and so far so good (no further connection drops since making the change).

Hmm, so the most recently created BE is still enabled? In that case it must have reverted the config if it couldn't load it. There should still be logs showing that.

@stephenw10 Thanks! I actually emailed him but haven't got an answer yet...

What pkgs do you have running? Check the RRD graphs. Do you see resource usage spike or something being exhausted?

Yes, you should be able to upgrade it with the Supermicro BIOS. Just be sure to retain the smbios values if you do. You may lose the Netgate splash screen. But there isn't any real requirement to do so.

What do the logs in pfSense show? That looks like the server side is complaining about the module though. Can you upgrade the NVM in the NIC like it suggests?

@smartcall Will do. At present, given multiple young but out of warranty Netgate hardware of mine that are becoming unrecoverable the only reason I was buying Netgate hardware in the first place is no the case.

I run a TS128GMTE452T, but wiht UPS and RAM Disk. Pfblocker drop xGB day if there is no RAM Disk.

@stephenw10 I had actually thought of doing a cross-compile from my ubuntu installation but it seemed too complicated to figure out how to compile it against FreeBSD headers and especially how to handle the hidapi library. Had I thought of doing a FreeBSD install on a VM at the very beginning, then compiling the code on the VM before copying to the pfSense box, it probably would have been faster and easier overall.

@binhex01 I already have a 120mm fan attached. Idles around +- 25° so that can't be a problem. I've PMed you with an offtopic question.

@stephenw10 Indeed, so I try but it doesn't work I build a freebsd VM and install the appropriate package to be able to compile... I get the source https://github.com/Aquantia/aqtion-freebsd But I get error: usr/src/aqtion-freebsd-0.0.5/aq_main.c:197:57: error: too many arguments provided to function-like macro invocation 197 | DRIVER_MODULE(atlantic, pci, aq_driver, aq_devclass, 0, 0); | ^ /usr/include/sys/bus.h:854:9: note: macro 'DRIVER_MODULE' defined here 854 | #define DRIVER_MODULE(name, busname, driver, evh, arg) | ^ fatal error: too many errors emitted, stopping now [-ferror-limit=] In the main the function put 5 arguments in the bus.h that function is only expecting 5 arguments.. mismatch the code is not working properly I study the C a long time ago (I'm old :-) ) and I never used after.

It's the Vendor and Product ID as reported by usbconfig: [24.11-RELEASE][admin@6100.stevew.lan]/root: usbconfig -d ugen0.4 -v ugen0.4: <ME906s LTE M.2 Module Huawei Technologies Co., Ltd.> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA) ugen0.4.0: u3g0: <Huawei Technologies Co., Ltd. HUAWEI Mobile, class 0/0, rev 2.10/1.02, addr 3> bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0210 bDeviceClass = 0x0000 <Probed by interface class> bDeviceSubClass = 0x0000 bDeviceProtocol = 0x00ff bMaxPacketSize0 = 0x0040 idVendor = 0x12d1 idProduct = 0x15c1 bcdDevice = 0x0102 iManufacturer = 0x0001 <Huawei Technologies Co., Ltd.> iProduct = 0x0002 <HUAWEI Mobile> iSerialNumber = 0x0003 <0123456789ABCDEF> bNumConfigurations = 0x0003

@stephenw10 I have re-tested tonight and checked I have 0 collisions. [image: 1738259104438-734ac97a-0fe7-4b84-bc7c-1fac7c85179e-image.png] The above is during the time I switched back to the 2.5GBE port and ran a test from my test machine. That is connected to a second 2.5GBE port. I complete more testing ever later tonight or tomorrow morning and post my results.

@stephenw10 Thank you.

@stephenw10 Yes Ive tried; different ports different cables different switches (net gear & unifi) updated firmware disabled sr-iov and i/oat in the bios just this morning I wiped pfsense and restored the configuration. Maybe the install was bad somehow. Either the nic is bad or the server is. That's the only two things left that I can think of. I just hope it's the nic!

Thank you all for the feedback. I suppose the discontinuation of the Plus upgrade for home labs was a financial one. Bummer, I still say. :)