Messages

Solved by disabling geoblock rules...

Hi,

Im running caddy as a reverse proxy with https. Its been working for many month but now it is not able to refresh the cert. The logs suggest "firewall problems" but I have not change any rules and all urls in the logs are accessable (from a browser).

OPNSESNSE: 27.5

Code Select Expand

"error","ts":"2025-07-27T12:17:15Z","logger":"tls.renew","msg":"could not get certificate from issuer","identifier":"xxxx.duckdns.org","issuer":"acme-v02.api.letsencrypt.org-directory","error":"HTTP 400 urn:ietf:params:acme:error:connection - 158.174.xx.xxx: Timeout during connect (likely firewall problem)"}

Code Select Expand

"error","ts":"2025-07-27T12:17:15Z","msg":"validating authorization","identifier":"xxx.duckdns.org","problem":{"type":"urn:ietf:params:acme:error:connection","title":"","detail":"158.174.xxx.xxx: Timeout during connect (likely firewall problem)","instance":"","subproblems":null},"order":"https://acme-v02.api.letsencrypt.org/acme/order/xxx/xxxx","attempt":2,"max_attempts":3,"stacktrace":"github.com/mholt/acmez/v3.(*Client).ObtainCertificate\n\tgithub.com/mholt/acmez/v3@v3.1.2/client.go:152\ngithub.com/caddyserver/certmagic.(*ACMEIssuer).doIssue\n\tgithub.com/caddyserver/certmagic@v0.23.0/acmeissuer.go:489\ngithub.com/caddyserver/certmagic.(*ACMEIssuer).Issue\n\tgithub.com/caddyserver/certmagic@v0.23.0/acmeissuer.go:382\ngithub.com/caddyserver/caddy/v2/modules/caddytls.(*ACMEIssuer).Issue\n\tgithub.com/caddyserver/caddy/v2@v2.10.0/modules/caddytls/acmeissuer.go:288\ngithub.com/caddyserver/certmagic.(*Config).renewCert.func2\n\tgithub.com/caddyserver/certmagic@v0.23.0/config.go:906\ngithub.com/caddyserver/certmagic.doWithRetry\n\tgithub.com/caddyserver/certmagic@v0.23.0/async.go:104\ngithub.com/caddyserver/certmagic.(*Config).renewCert\n\tgithub.com/caddyserver/certmagic@v0.23.0/config.go:982\ngithub.com/caddyserver/certmagic.(*Config).RenewCertAsync\n\tgithub.com/caddyserver/certmagic@v0.23.0/config.go:768\ngithub.com/caddyserver/certmagic.(*Config).manageOne.func2\n\tgithub.com/caddyserver/certmagic@v0.23.0/config.go:469\ngithub.com/caddyserver/certmagic.(*jobManager).worker\n\tgithub.com/caddyserver/certmagic@v0.23.0/async.go:73"}

Code Select Expand

"error","ts":"2025-07-27T12:17:15Z","msg":"challenge failed","identifier":"xxx.duckdns.org","challenge_type":"tls-alpn-01","problem":{"type":"urn:ietf:params:acme:error:connection","title":"","detail":"158.174.xxx.xxx: Timeout during connect (likely firewall problem)","instance":"","subproblems":null},"stacktrace":"github.com/mholt/acmez/v3.(*Client).pollAuthorization\n\tgithub.com/mholt/acmez/v3@v3.1.2/client.go:557\ngithub.com/mholt/acmez/v3.(*Client).solveChallenges\n\tgithub.com/mholt/acmez/v3@v3.1.2/client.go:378\ngithub.com/mholt/acmez/v3.(*Client).ObtainCertificate\n\tgithub.com/mholt/acmez/v3@v3.1.2/client.go:136\ngithub.com/caddyserver/certmagic.(*ACMEIssuer).doIssue\n\tgithub.com/caddyserver/certmagic@v0.23.0/acmeissuer.go:489\ngithub.com/caddyserver/certmagic.(*ACMEIssuer).Issue\n\tgithub.com/caddyserver/certmagic@v0.23.0/acmeissuer.go:382\ngithub.com/caddyserver/caddy/v2/modules/caddytls.(*ACMEIssuer).Issue\n\tgithub.com/caddyserver/caddy/v2@v2.10.0/modules/caddytls/acmeissuer.go:288\ngithub.com/caddyserver/certmagic.(*Config).renewCert.func2\n\tgithub.com/caddyserver/certmagic@v0.23.0/config.go:906\ngithub.com/caddyserver/certmagic.doWithRetry\n\tgithub.com/caddyserver/certmagic@v0.23.0/async.go:104\ngithub.com/caddyserver/certmagic.(*Config).renewCert\n\tgithub.com/caddyserver/certmagic@v0.23.0/config.go:982\ngithub.com/caddyserver/certmagic.(*Config).RenewCertAsync\n\tgithub.com/caddyserver/certmagic@v0.23.0/config.go:768\ngithub.com/caddyserver/certmagic.(*Config).manageOne.func2\n\tgithub.com/caddyserver/certmagic@v0.23.0/config.go:469\ngithub.com/caddyserver/certmagic.(*jobManager).worker\n\tgithub.com/caddyserver/certmagic@v0.23.0/async.go:73"}

Hi,
I have been running Caddy and DuckDNS for a while now but now im not able to start the Caddy service.
When Im trying to start the service I get this error.

Code Select Expand

Error: adapting config using caddyfile: parsing caddyfile tokens for 'dynamic_dns': getting module named 'dns.providers.duckdns': module not registered: dns.providers.duckdns, at /usr/local/etc/caddy/Caddyfile:21
I did follow this guide when I configured it. https://forum.opnsense.org/index.php?topic=38714.0

Resurecting this as I have tried playing with Powerd some more.

With Powerd enabled and set at Adaptive, my cpu temperateres are higher than when I disable Powerd (Powerd off and Powerd set to Minimum seem to be the same).
Is that normal/correct?

Using command Powerd -v in ssh, I can see the cpu goes to 1001MHz (base clock +1MHz)  regardless if Powerd is on or off.
I was expecting temps to be higher with Powerd off so just curious.

Thanks

Hi,
I struggled with a similar problem. https://forum.opnsense.org/index.php?topic=42125 and check that you have enabled c-states in the BIOS.

After a few reboots and uninstallation of the intel-ipsec-mb package and its tunabled the speeds are back... All other settings are the same.
Tanks for your time @DEC670airp414user

Now I have tested with MTU 1412 and it doesn't get any better. I even uninstalled the intel-ipsec-mb package but it didn't matter. Have tried both Mullvad and Proton, two different companies and servers.
Speedtests that are going outside the tunnels gives me the expected speed and no package loss at the wan interface.

Hi!
I use MTU 1420, set in Wireguard > Instances. I have tried 1280 but the packet loss did still exist. https://mullvad.net/en/help/wireguard-and-mullvad-vpn
Max mss 1380, set in Normalization. I have tried to disable this but it doesn't help.
CPU = i7-8550U CPU @ 1.80GHz (4 cores, 4 threads)
When I utilize the Mullvad tunnel I also get packet loss at the Proton tunnel even when it is not used.
Please see the attached screenshots.

Hi,
I've been running a WG tunnel to Mullvad for over a year now without any problems. Great speed but it's capped to 70MB/s.
Now I noticed that I only get up to around 10MB/s and I see alot of packet loss.
I have followed the guides provided by opnsense.
https://docs.opnsense.org/manual/how-tos/wireguard-client-mullvad.html
https://docs.opnsense.org/manual/how-tos/wireguard-selective-routing.html

I have even tried to create a new tunnel to ProtonVPN and I see the same issues with that tunnel. So I guess that the problem is somewhere in my setup...

What could be wrong and how do I troubleshoot this?

And if you are lazy like me..
https://calculat.io/en/number/dec-to-bin/2
Use the bit position...

What to set for a 2 core system?

ok, now the hwpstate_intel (hint.hwpstate_intel.0.disabled =1) is disabled and powerd enabled.

Code Select Expand


$ sysctl dev.cpufreq.0.freq_driver
dev.cpufreq.0.freq_driver: est0


Code Select Expand

sysctl dev.cpu.0.freq_levels
dev.cpu.0.freq_levels: 2001/15000 2000/15000 1900/14088 1800/13193 1700/12317 1600/11459 1500/10617 1400/9796 1200/8199 1100/7426 1000/6670 900/5932 800/5209 700/4502 600/3812 500/3137


Code Select Expand


sysctl dev.cpu.0.freq
dev.cpu.0.freq: 2001
sysctl dev.cpu.1.freq
dev.cpu.1.freq: 1400
sysctl dev.cpu.1.freq
dev.cpu.1.freq: 2001
sysctl dev.cpu.1.freq
dev.cpu.1.freq: 2001
sysctl dev.cpu.1.freq
dev.cpu.1.freq: 2001


Code Select Expand

kalle@OPNsense:~ $ sysctl dev.cpu | grep cx
dev.cpu.1.cx_method: C1/mwait/hwc C2/mwait/hwc C3/mwait/hwc
dev.cpu.1.cx_usage_counters: 389873 923520 7477225
dev.cpu.1.cx_usage: 4.43% 10.50% 85.05% last 6625us
dev.cpu.1.cx_lowest: C3
dev.cpu.1.cx_supported: C1/1/1 C2/2/148 C3/3/506
dev.cpu.0.cx_method: C1/mwait/hwc C2/mwait/hwc C3/mwait/hwc
dev.cpu.0.cx_usage_counters: 442746 917207 7759320
dev.cpu.0.cx_usage: 4.85% 10.05% 85.08% last 125us
dev.cpu.0.cx_lowest: C3
dev.cpu.0.cx_supported: C1/1/1 C2/2/148 C3/3/506


Code Select Expand

sudo powerd -v
powerd: unable to determine AC line status
load   0%, current freq 2001 MHz ( 0), wanted freq 1938 MHz
changing clock speed from 2001 MHz to 2000 MHz
load   0%, current freq 2000 MHz ( 1), wanted freq 1877 MHz
changing clock speed from 2000 MHz to 1900 MHz
load   0%, current freq 1900 MHz ( 2), wanted freq 1818 MHz
load   0%, current freq 1900 MHz ( 2), wanted freq 1761 MHz
changing clock speed from 1900 MHz to 1800 MHz
load   0%, current freq 1800 MHz ( 3), wanted freq 1705 MHz
load   3%, current freq 1800 MHz ( 3), wanted freq 1651 MHz
changing clock speed from 1800 MHz to 1700 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 1599 MHz
changing clock speed from 2001 MHz to 1600 MHz
load   0%, current freq 1600 MHz ( 5), wanted freq 1549 MHz
load   3%, current freq 1600 MHz ( 5), wanted freq 1500 MHz
changing clock speed from 1600 MHz to 1500 MHz
load   3%, current freq 1500 MHz ( 6), wanted freq 1453 MHz
load  45%, current freq 1500 MHz ( 6), wanted freq 1743 MHz
changing clock speed from 1500 MHz to 1800 MHz
load   0%, current freq 1800 MHz ( 3), wanted freq 1688 MHz
changing clock speed from 1800 MHz to 1700 MHz
load   0%, current freq 1700 MHz ( 4), wanted freq 1635 MHz
load   3%, current freq 1700 MHz ( 4), wanted freq 1583 MHz
changing clock speed from 1700 MHz to 1600 MHz
load   0%, current freq 1600 MHz ( 5), wanted freq 1533 MHz
load   0%, current freq 1600 MHz ( 5), wanted freq 1485 MHz
changing clock speed from 1600 MHz to 1500 MHz
load   0%, current freq 1500 MHz ( 6), wanted freq 1438 MHz
load   0%, current freq 1500 MHz ( 6), wanted freq 1393 MHz
changing clock speed from 1500 MHz to 1400 MHz
load   0%, current freq 1400 MHz ( 7), wanted freq 1349 MHz
load   0%, current freq 1400 MHz ( 7), wanted freq 1306 MHz
load   5%, current freq 1400 MHz ( 7), wanted freq 1265 MHz
load  14%, current freq 1400 MHz ( 7), wanted freq 1225 MHz
load  82%, current freq 1400 MHz ( 7), wanted freq 4002 MHz
changing clock speed from 1400 MHz to 2001 MHz
load   4%, current freq 2001 MHz ( 0), wanted freq 3876 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3754 MHz
load   3%, current freq 2001 MHz ( 0), wanted freq 3636 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3522 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3411 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3304 MHz
load  26%, current freq 2001 MHz ( 0), wanted freq 3304 MHz
load  66%, current freq 2001 MHz ( 0), wanted freq 4002 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3876 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3754 MHz
load  20%, current freq 2001 MHz ( 0), wanted freq 3636 MHz
load  51%, current freq 2001 MHz ( 0), wanted freq 4002 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3876 MHz
load   4%, current freq 2001 MHz ( 0), wanted freq 3754 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3636 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3522 MHz
load   3%, current freq 2001 MHz ( 0), wanted freq 3411 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3304 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3200 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3100 MHz
load   3%, current freq 2001 MHz ( 0), wanted freq 3003 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2909 MHz
load   4%, current freq 2001 MHz ( 0), wanted freq 2818 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2729 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2643 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2560 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2480 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2402 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2326 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2253 MHz
load  44%, current freq 2001 MHz ( 0), wanted freq 2643 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2560 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2480 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2402 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2326 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2253 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2182 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2113 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2046 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 1982 MHz
changing clock speed from 2001 MHz to 2000 MHz
load   0%, current freq 2000 MHz ( 1), wanted freq 1920 MHz
load  56%, current freq 2000 MHz ( 1), wanted freq 2867 MHz
changing clock speed from 2000 MHz to 2001 MHz
load  15%, current freq 2001 MHz ( 0), wanted freq 2777 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2690 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2605 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2523 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2444 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2367 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2293 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2221 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2151 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2083 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2017 MHz
load 120%, current freq 2001 MHz ( 0), wanted freq 4002 MHz
load  38%, current freq 2001 MHz ( 0), wanted freq 4002 MHz
load   3%, current freq 2001 MHz ( 0), wanted freq 3876 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3754 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3636 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3522 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3411 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3304 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3200 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3100 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3003 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2909 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2818 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2729 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2643 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2560 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2480 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2402 MHz
load   3%, current freq 2001 MHz ( 0), wanted freq 2326 MHz
load  45%, current freq 2001 MHz ( 0), wanted freq 2791 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2703 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2618 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2536 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2456 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2379 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2304 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2232 MHz
load   4%, current freq 2001 MHz ( 0), wanted freq 2162 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2094 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2028 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 1964 MHz
changing clock speed from 2001 MHz to 2000 MHz
load  63%, current freq 2000 MHz ( 1), wanted freq 3299 MHz
changing clock speed from 2000 MHz to 2001 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3195 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3095 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2998 MHz
load   8%, current freq 2001 MHz ( 0), wanted freq 2904 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2813 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2725 MHz
load  14%, current freq 2001 MHz ( 0), wanted freq 2639 MHz
load 154%, current freq 2001 MHz ( 0), wanted freq 4002 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3876 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3754 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3636 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3522 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3411 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3304 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3200 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3100 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 3003 MHz
load   4%, current freq 2001 MHz ( 0), wanted freq 2909 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2818 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2729 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2643 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2560 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2480 MHz
load   3%, current freq 2001 MHz ( 0), wanted freq 2402 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2326 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2253 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2182 MHz
load   6%, current freq 2001 MHz ( 0), wanted freq 2113 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2046 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 1982 MHz
changing clock speed from 2001 MHz to 2000 MHz
load  47%, current freq 2000 MHz ( 1), wanted freq 2484 MHz
changing clock speed from 2000 MHz to 2001 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2406 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2330 MHz
load   0%, current freq 2001 MHz ( 0), wanted freq 2257 MHz

PS.
"sysctl dev.cpu | grep temp" gives me another temperature then the webgui?!

Code Select Expand

sysctl dev.cpu | grep temp
dev.cpu.1.temperature: 43.0C
dev.cpu.1.coretemp.throttle_log: 1
dev.cpu.1.coretemp.tjmax: 105.0C
dev.cpu.1.coretemp.resolution: 1
dev.cpu.1.coretemp.delta: 62
dev.cpu.0.temperature: 46.0C
dev.cpu.0.coretemp.throttle_log: 1
dev.cpu.0.coretemp.tjmax: 105.0C
dev.cpu.0.coretemp.resolution: 1
dev.cpu.0.coretemp.delta: 59

I would suggest going through all the system bios options. Start with a reset to default to have a baseline and go from there. Possibly power management is currently disabled. Unfortunately, Qotom seems to have a tendency to leave each and every possible bios option visible, so this may be quite laborious.

In System - Settings - Miscellaneous, have you enabled 'powerd' and selected an appropriate governor (adaptive or high adaptive)?

I have now tried many settings in the bios but it seem to not help.
Could it be that the CPU doesent support "hwpstate_intel" (Intel Speed Shift Technology driver) and I need to disable it in OPNS?
https://ark.intel.com/content/www/us/en/ark/products/84992/intel-core-i7-5550u-processor-4m-cache-up-to-3-00-ghz.html

Hi,
How will the manual setup work/coexist with the new plugin?

Hi,
I have a Intel i7 5550U that seems to be stuck at 2001mhz even when the system are idling. The temperature are always very high, around ~80C.
Its a Qotom hw, Q5500UG4-P V1.1 with the latest BIOS (2024-01-02).

kalle@OPNsense:~ $ sysctl dev.cpufreq.0.freq_driver
dev.cpufreq.0.freq_driver: est0
kalle@OPNsense:~ $ sysctl dev.cpu.0.freq_levels
dev.cpu.0.freq_levels: 2001/15000 2000/15000 1900/14088 1800/13193 1700/12317 1600/11459 1500/10617 1400/9796 1200/8199 1100/7426 1000/6670 900/5932 800/5209 700/4502 600/3812 500/3137
kalle@OPNsense:~ $ sysctl dev.cpu.0.freq
dev.cpu.0.freq: 2001
kalle@OPNsense:~ $ sysctl dev.cpu.1.freq
dev.cpu.1.freq: 2001

kalle@OPNsense:~ $ sysctl dev.cpu | grep cx
dev.cpu.1.cx_method: C1/mwait/hwc C2/mwait/hwc C3/mwait/hwc
dev.cpu.1.cx_usage_counters: 251704 352780 1194540
dev.cpu.1.cx_usage: 13.99% 19.60% 66.39% last 4766us
dev.cpu.1.cx_lowest: C3
dev.cpu.1.cx_supported: C1/1/1 C2/2/148 C3/3/506
dev.cpu.0.cx_method: C1/mwait/hwc C2/mwait/hwc C3/mwait/hwc
dev.cpu.0.cx_usage_counters: 203383 253748 1245289
dev.cpu.0.cx_usage: 11.94% 14.90% 73.14% last 8539us
dev.cpu.0.cx_lowest: C3
dev.cpu.0.cx_supported: C1/1/1 C2/2/148 C3/3/506

I have added the following tunables but they doesn't seem to help.

dev.hwpstate_intel.0.epp = 99
dev.hwpstate_intel.1.epp = 99
hw.acpi.cpu.cx_lowest = C3 

Do any of you have any suggestions how to get the cpu go lower?

Hi,

I'm struggeling with the tcp_outgoing_address parameter, i cant get it to work. I have a working wireguard (road worrior setup) connection and a working squid proxy but when I add the tcp_outgoing_address parameter all the connections through the proxy time out.
Do I need any new routes or fw-rules to get this working?