Well, it pretty much has to be bad hardware and almost certainly bad RAM. You don't need 20GB so I'd try removing some until the error goes away.

@stephenw10 Thank you Stephen!

The only way this is possible currently is to use the syslogng package. There you can set a location to use for log storage which can be a different drive or partition. If you then set /var as a ram drive system logging does not write to the drive. BUT.... there is no built in management of different drives in pfSense so you need to use custom scripts to do that. Hence it's not supportable.

Both will work with VLANs. It may not have some offloading but you can do VLANs entirely in software if needed.

@matyi-szabolcs Hey, I also have the N100. You can monitor CPU freq via pfSense command line using this command: while ( 1 ) clear sysctl dev.cpu | grep freq: sleep 1 end Paste that as-is directly into the pfSense shell (using the terminal not UI). It'll refresh every second and show you all core frequencies like: dev.cpu.0.freq: 1800 dev.cpu.1.freq: 1600 ... Then you can do something CPU heavy like restart Suricata or something.

@stephenw10 i have strange fetish for this kind of devices,i'd like to get my hands on them,but still,i'll have to use some bigger pc-like or passive and keep those for tinker purposes... i didn't even installed windows 10/11 there yet..just for fun addon card eats about 2.5W idle unconnected.i'm now down to ~23.8W

OK, Thanks Stephen

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.

@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

@sleleeeee Welcome! I use an external LTE modem for failover WAN. Makes it transparent to pfSense. Depending which country and provider. US: https://www.netgear.com/home/mobile-wifi/lte-modems/lm1200/ EU: https://www.netgear.com/uk/home/mobile-wifi/lte-modems/lm1200/