You mean in the interrupts shown by vmstat? They do, but not for aes-gcm. Which is what I'm digging into.

350Mbps single core throughput is relatively easy to achieve. Any C3K CPU will pass that for example.

I would avoid an N100 system. There are several threads here with users trying to get those tuned correctly. It seems many are supplied with default thermal/power values that are very restrictive. In FreeBSD/pfSense at least.

@tapnet boot into a Linux Live USB, open Terminal and type lspci see If the card shows up. ESXi removes support.

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.

If you put the server there you wouldn't need and rules, outbound traffic to it from a client would already be allowed. Unless you have policy routing in which case you'd need a bypass rule.

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).

@stephenw10 Right?? I'm not sure I need it, a lot of my stuff runs over a VPN which is a bottle neck, but it's fun to say I have it. :)

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...

The i5-4670 has just been installed into the home network's M400 and the reboot test was successful. Certainly runs cooler than the i5-4670K.

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

Ill have to get a picture for you when I have a change to reboot.

@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.

@stephenw10

Hello,
of course, I have tried disabling and re-enabling Speed Shift in the BIOS, and I also tested powerd. I've already tried every possible option mentioned in the forums, but in reality, others in the forums were also just experimenting with these settings, and no one has managed to run the N100 processor at 3.4 GHz yet. I also installed FreeBSD 15 and tested all available options there.

I tried setting the P1 value to 9W, 10W, and 15W, and the P2 value to 20W, 25W, and 30W, etc., but nothing helped. In my BIOS, these options are available by default, so I don't need a modded BIOS or special keyboard combinations.

However, under Debian Linux, it works properly with the default BIOS settings, and no adjustments are needed. I think I'll return the device while I still can.

Regards