@bttech56 Hey, this was the only single tim IDs changed. Though I did move from LTE to optical cable, with terminal-only unit, so at the moment it is via ethernet port. Now I have about 3 months without reboot. No root cause identified.

@planedrop yep its an older thread, i arrived here through googling the issue i was having and this was one of the top results. whilst it is a virtualised environment, the commonality between them exists and my setup is largely indistinguishable from a non-virtualised setup. i'm using dedicated cores, binding IRQs to those cores, isolating them, using hardware passthrough. theres a variety of other threads who have had similar experiences with SR-IOV too. just to add this was with the default MTU of 1500 and rx / tx descriptors of 4k on the linux side improving this on the freebsd side (by placing into the loader.conf.local) #enable iflib overrides for ixv interfaces dev.ixv.0.iflib.override_qs_enable="1" dev.ixv.1.iflib.override_qs_enable="1" # Set 4K descriptors dev.ixv.0.iflib.override_nrxds="4096" dev.ixv.0.iflib.override_ntxds="4096" dev.ixv.1.iflib.override_nrxds="4096" dev.ixv.1.iflib.override_ntxds="4096" # Enable iflib overrides for ix interface dev.ix.0.iflib.override_qs_enable="1" # Set 4K descriptors for ix interface dev.ix.0.iflib.override_nrxds="4096" dev.ix.0.iflib.override_ntxds="4096" seems to have helped out with regard to rx_no_dma_resources issues, you can generally check if you are having those same issues by looking at sysctl dev.ix | grep -E "(r_drops|r_stalls|r_restarts|no_desc_avail|credits|override_n[rt]xds)"

@jra9511 where does it fail in the process.. What error does it present? I just created a new account and didn't have any issues. [image: 1750773199015-creation.jpg]

I think I figured it out my mistake to over commit CPU in a VM . Now seens to not get stuck at 100%

You might be able to get OpenWRT to run on there if you can get access. You should see something on the console though. I'd make sure your terminal setup is good, RJ-45 serial lead is correct etc.

@zeroepoch Thank you. That worked like a charm on a 2.5 GBE Realtek adapter. I had to modify the install command as the affected interface was the WAN-side, so I had no internet connection: pkg install --no-repo-update ./realtek-re-kmod198-198.00.150029.pkg Hope that Netgate will include this driver in future releases as it is a pain to get this running on a dedicated server at Hetzner.com when the have a 2.5 GBE as a default LAN adapter.

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.