so for those noctua 'fans' out there,since the fan is moving such a low volume,you should probably seal everything you can on the path between fans and cpu cooler(careful around power stage to keep air flowing there a bit maybe),and that means mainly:space under board,space under cooler,space around those 2 aluminium rails(mainly below,big holes),i have 4590t(also does not reboot well,with v6 bios,thanks for the mod btw!)

i have similar/same machine(lanner was busy:) )

i think(early testing) it is making massive difference on silent mode,since it is not pulling air through the gaps

i also tried updating microcode in bios,but i did it wrong,or it did not work (you don't actually need bios update for microcode update),but still locked on reboot..no clue why it freezes

@jwt without going into the weeds on this, i will say that i paid out of my own pocket for the update to the openbgp status page in 2.0. before that the status would never load. now its code has been carried over and continues to benefit the ffr packages for both CE and PRO. ive even purchased multiple appliances from netgate and pfsense.

i will tell you that seeing someone with a netgate tag represent negate this way is a little alarming.

i wish you wellness

@Seeking-Sense

Yes, this was all done in a FreeBSD 15 VM using VirtualBox. I had to change the default network card to VirtIO I believe since the performance with the other NICs was like dial-up modem speeds. I also had to install pkg manually using pkg-static since the auto installer when running pkg didn't work and just hung. I don't remember if I tried installing pkg before or after I fixed the slow network issue.

I just installed all the packages mentioned throughout the page since I wasn't trying to optimize size since I intended to throw away the VM when I was done.

Finding a working commit for the kernel was one of the main challenges. I looked for a commit right before a merge from main that was still 1500029.

OK, Thanks Stephen

Trim: yes, SWAP: no IMO.

Looks identical to this: https://redmine.pfsense.org/issues/16101

It would for that Cron job but you could run it more often or on a different day etc.

You shouldn't need to load a driver for those, it's in kernel:

[25.03-BETA][admin@4200.stevew.lan]/root: kldstat -v | grep mlx 586 mlx4en 585 mlx4 587 pci/lkpi_mlx5_core_pci_table 584 pci/lkpi_mlx4_pci_table 233 pci/mlx 232 mlx/mlxd

BTW that ALTQ setting only applies to hn(4) NICs, so only in Hyper-V or Azure.

Just go to Interfaces > Assign and set LAN to a different NIC. But I'd want to have some other way to access the firewall first so you can revert the change if you need to. The direct console for example.

@hangmansnoose001380 Can you DM me the BIOS-File please?

@stephenw10 yea I only got 10G NICs. I tested on the host itself for today to get the setup right. Tomorrow I am going to test with my 2 Servers which are capable of doing 10G via SFP+

@patient0 Once it hits what it shows in the picture there's zero response from they keyboard. That's just my terminal monitor and keyboard that I connect to my hypervisor and pfSense box if I need direct access.

@Sergei_Shablovsky said in Screen fonts & mode in local terminal issue:

Already have in /etc/loader.conf

:charset=UTF-8:
:lang=en_US.UTF-8:
:setenv=LC_COLLATE=C:
:umask=022:

But unsuccessfully, - the result You able to see above….

Those are not loader.conf configuration directives, those look like /etc/login.conf configuration. (And read the note at the top of that file, especially the part where you have to run cap_mkdb /etc/login.conf after any edits)

It does seem like you have some sort of issue/mismatch with UTF-8 handling somewhere, but it's hard to say exactly where. I have no issues with UTF-8 in my terminals over serial or SSH but I have no idea what that KVM setup might be doing.

Hi! At the moment, the average traffic is around 4 Gbps

That's a fun thread. 😁

Normally not but if you're relying on NAT reflection that would be via the firewall in both directions. Both devices on the LAN would see the traffic as via the LAN interface.

I was going to go with EIG44ET but then I discovered the i350-T4 V2 which is newer than the i340.

https://www.amazon.com/dp/B01DIT7GH4?ref=fed_asin_title