Messages

Hey all,

I'm seeing an odd issue that so far I've been unable to resolve or find a similar problem posted.

I can successfully create two different OpenVPN server instances (different ports, protocols, and TUN subnets).

The issue arrises when I try to use them at the same time. Whichever server is "first" works fully correctly. The second is unable to reach internal networks. If I disable either, the one that is enabled works as expected.

My current assumption is that there is a bug here somewhere, as the rules seem to allow either server to work correctly as long as it is the only active server.

Any suggestions?

Thanks!

Spent an unfortunate amount of time trying to enable DCO for a TCP OpenVPN Server in Opnsense.

There either needs to be a prominent note, error log entry, or configuration validation error thrown when trying to use DCO with TCP connections.

Not a direct answer, but instead of jellyfin music, have you considered Roon? https://roon.app/en/

I found a forum post about your WiiM mini and Vlans here, maybe that helps also: https://forum.wiimhome.com/threads/app-option-for-fixed-ip-devices-on-another-network.127/

I have a seemingly identical issue. Did you come to a solution?

UPDATE:

Flashed a new bios from here (https://www.changwang.com/down/59.html) on the off-chance it works and solves the issue.

Solved the issue. The frequency now scales up and down based on usage.

Here's a dump of my tunables as well:

Code Select Expand

dev.hwpstate_intel.0.epp Intel Speed Shift Efficiency runtime 100
dev.hwpstate_intel.1.epp Intel Speedshift Efficiency runtime 100
dev.hwpstate_intel.2.epp Intel Speedshift Efficiency runtime 100
dev.hwpstate_intel.3.epp Intel Speedshift Efficiency runtime 100
dev.igc.0.fc Flow Control on Interface runtime 0
dev.igc.1.fc Flow Control on Interface runtime 0
dev.igc.2.fc Flow Control on Interface runtime 0
dev.igc.3.fc Flow Control on Interface runtime 0
hint.hwpstate_intel.0.disabled disable speed shift unsupported 0
hw.acpi.cpu.cx_lowest C-States runtime C1
machdep.hwpstate_pkg_ctrl Intel Pstate boot-time 0

I'm seeing the same behavior unfortunately. Same processor.

Unfortunately ? Did you decide to ignore all other posts (specifically the last one from Taunt9930) on purpose ?

Don't be obtuse. I was replying specifically to @torob2. The vendor for my N5105 unit seems to have an outdated BIOS. The frequency was never scaling on usage with Speed Shift enabled. Ended up flashing a different BIOS from a similar line of units to get an update.

Seems to have done the trick. My CPU now actually scales depending on the load and the Speed Shift efficiency setting.

I ended up flashing a newer BIOS. That seemed to enable the CPU frequency to actually scale.

Hi guys, I have recently bought one of these and am having CPU temperature issues with OPNSense. In Debian, I get CPU temps of around 55C idle, but in OPNSense, by default they are 85C and above, even with the hardware modifications regarding the head-spreader and thermal pads.

I get temps down to 65C by disabling powerd (apparently this is not needed with FBSD v13 with the Intel Speed Shift driver) and typing in:

Code Select Expand

sysctl dev.hwpstate_intel.0.epp=100
which puts it in maximum efficiency mode (for all cores at once). (At the moment I am struggling to get this setting to be applied at boot because it seems to be being ignored in /etc/systcl.conf!)

If you have this hardware, can you please let me know the output of the following?

Have you been able to set epp to non-100 values and still see the frequency down-shift? I can't get speedshift to work properly on this CPU for some reason. Others on other Intel processors aren't seeing this issue.

Well, that's not what's happening here with an Intel Celeron N5105 system:

Code Select Expand

dev.cpu.0.temperature: 53.0C
dev.cpu.0.coretemp.throttle_log: 0
dev.cpu.0.coretemp.tjmax: 105.0C
dev.cpu.0.coretemp.resolution: 1
dev.cpu.0.coretemp.delta: 52
dev.cpu.0.cx_method: C1/mwait/hwc C2/mwait/hwc C3/mwait/hwc
dev.cpu.0.cx_usage_counters: 10643 0 0
dev.cpu.0.cx_usage: 100.00% 0.00% 0.00% last 134us
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_supported: C1/1/1 C2/2/253 C3/3/1048
dev.cpu.0.freq_levels: 1996/-1
dev.cpu.0.freq: 2096
dev.cpu.0.%parent: acpi0
dev.cpu.0.%pnpinfo: _HID=none _UID=0 _CID=none
dev.cpu.0.%location: handle=\_SB_.PR00
dev.cpu.0.%driver: cpu
dev.cpu.0.%desc: ACPI CPU


It has nothing to do with the BIOS settings because the same settings are used for the other ...sense system which is able to throttle the CPU below 2 GHz. I would have expected an opposing result because the other system is based on FreeBSD 12.3 while OPNsense 22.7 is using FreeBSD 13.1 and the Intel Celeron N5105 (Jasper Lake) is still quite new given its release in 2021.

I'm seeing the same behavior unfortunately. Same processor.