Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - TomT

#1
25.1, 25.4 Production Series / Re: CPU Temperature
March 19, 2025, 11:22:08 PM
Quote from: Patrick M. Hausen on March 19, 2025, 01:29:37 PMThe GUI itself is causing the CPU to work increasing the temperature by a couple of degrees.
The command line temperatures were recorded while I had the GUI open, surely they should be the same ?
#2
25.1, 25.4 Production Series / CPU Temperature
March 19, 2025, 01:27:56 PM
Hi,
I'm running OPNsense 25.1.2 on a Trigkey G5 which uses the Intel N100 CPU.
At the command line I've run 'sysctl -a | grep temperature' and I get the following:

hw.acpi.thermal.tz0.temperature: 27.9C
dev.cpu.3.temperature: 45.0C
dev.cpu.2.temperature: 44.0C
dev.cpu.1.temperature: 44.0C
dev.cpu.0.temperature: 44.0C

At the same time the GUI is showing the CPU cores at 49C. Why is there a difference between the two results ?

Thanks
#3
Thanks for explaining this, very much appreciated. 🙂
#4
Hi,
I've been having a look around my Opnsense server and was hoping someone could explain what system information quality is showing me.

I've attached an image of what I get.
Thanks
#5
I've updated my MTU and restarted my server.
So far things are looking ok.

Thanks for your help and advise and the How To.
#6
Thanks again.

My confusion is related to what I set vs what is computed.
If I enter the value from the MTU script, that makes the computed a lower value.

Should the WAN MTU be the script value, or should the computed value be the script value ?

Thanks
#7
Quote from: meyergru on February 04, 2025, 07:21:20 PM1. You have to set the MTU to a value <= your possible MTU, or you will have problems with sites without PMTU discovery.
2. To optimize that, it should be = your possible MTU.
3. With some hardware setups and ISPs, you can use even more than 1500 bytes on the underlying physical link, thus giving you again 1500 bytes even with PPPoE and / or VLANs in use, which overheads would normally have to be deducted from the physical link's MTU (often 1500).

To reiterate on #3, I gave detailed instructions here: https://forum.opnsense.org/index.php?topic=44271.msg220936#msg220936, this was linked in my instructions under point #9 already.


Please correct me on this.. Should my MTU be set to 1500, so the calculated will then be 1492 ?
I've never understood how this is meant to work.

Thanks
#8
Quote from: meyergru on February 04, 2025, 12:20:05 AMSince you use PPPoE: Did you optimize your MTU? 20-30 Mbps less with 900 MBps theoretical limit means 2% lesser throughput. If your MTU is not optimized to yield 1500 bytes after PPPoE and VLAN overhead, speed may decrease even (or especially) if you clamp your MSS to counter other problems.

See point 9 here.

Also, you can try traffic shaping (see official docs).

Thanks.
I've run the mtu.sh script and it recommended 1484
Looking in the GUI the MTU was set to 1492 ( Calculated PPP MTU: 1484 )

Does that mean I need to change it ?

Thanks
#9
Everything seems to be running ok.
Reading another blog there are suggestions for the following tuneables.

hw.ibrs_disable = 1
net.inet.ip.intr_queue_maxlen = 3000
hw.igc.max_interrupt_rate = 20000
hw.igc.rx_process_limit = 5000

Are these worth doing, will they help me get similar speeds to my ISPs router ?
Thanks
#10
I'm not sure what's happened, but the VPN is connecting today.
#11
Thanks,

I've disabled PowerD is there anything specific I need to check in the logs ?

Does System: Settings: Miscellaneous:  Hardware acceleration need enabling ? if it does, is that Intel Quick Assist ?

Thanks
#12
Quote from: pouakai on February 03, 2025, 06:40:50 AMI ended up disabling PowerD on an N100 and used this post:

Do I need to enable PowerD

Note that the thread mixes up SpeedStep and Speed Shift in a few places!  I think this is the right way around:

QuoteSpeedStep is the "old" method - needs PowerD.
Speed Shift is the new method and its available since 6th Gen of Intel CPUs (I think) - doesn't need PowerD.

Thanks is this as simple as disabling PowerD or do tuneables ned setting?
Thanks
#13
Quote from: newsense on February 03, 2025, 03:58:40 AMThis is a must for N100 and later CPUs, reboot after installation.

pkg install os-cpu-microcode-intel-1.1
You can fix the missing plugins in the Firmware section.

Thanks I'll install that and reboot.

I ran the plugin conflict checker which install the kissing plugins. I then uninstalled them as they aren't needed.
#14
I've still got powerd enabled, should it be for an Intel N100 ?
If I have to disable it, is there anything else I need to enable or configure?
Thanks
#15
Hi.
I've moved my config from an AMD GX-420CA system to an Intel N100 system, apart from updating the temperature sensors and adding the following tuneables, is there anything else I need to update or change to get the max performance out of this ?

net.isr.dispatch: deferred
net.isr.bindthreads: 1
net.isr.maxthreads: -1
net.inet.rss.bits: 2
net.inet.rss.enabled: 1

Speedtests seem good, may be 20/30Mbps slower than the ISP router.
Any tips for tweaking the last bit out of the connection ?

I have IPSec and WireGuard VPNs configured, do I need to do anything else for them ?

In plugins I have two entries in red.
os-realtek-re (missing)
os-udpbroadcastrelay (missing)

I don't need either of those, how do I clear the red entries ?

Thanks