Messages

1

22.1 Legacy Series / Re: powerD seem not working

« on: August 15, 2022, 12:45:07 pm »

Thermal Sensors are set to Intel, of course. PowerD is enabled and set to Hiadaptive. The same settings as in the other ...sense. CPU clock goes up (max 2.9 GHz) if needed but never below 2 GHz whenever I checked.

2

22.1 Legacy Series / Re: powerD seem not working

« on: August 15, 2022, 11:24:24 am »

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

Code: [Select]

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.

3

22.1 Legacy Series / Re: powerD seem not working

« on: August 14, 2022, 04:14:44 pm »

I can confirm this even with 22.7. PowerD doesn't seem to work at all. On a system with a Intel Celeron N5105, the CPU clock stays all the time at 2 GHz while in another ...sense you can see frequencies as low as 800 MHz on the same hardware.

4

German - Deutsch / Re: CARP Status verschwindet nach failover

« on: June 15, 2018, 11:44:07 pm »

Mir ist etwas aufgefallen und zwar, daß advertising skew (advskew) bei Master und Backup den gleichen Wert hat:

Code: [Select]

        carp: BACKUP vhid 2 advbase 1 advskew 100
        carp: BACKUP vhid 1 advbase 1 advskew 100
        carp: MASTER vhid 4 advbase 1 advskew 100
        carp: MASTER vhid 3 advbase 1 advskew 100


Laut der man-Seite zu pfsync sollte man aber bei der Backup-Firewall einen höheren Wert, z.B. 100, verwenden. Für die Master-Firewall empfiehlt sich der Wert 0.

It is preferable that one firewall handle the forwarding of all the traffic, therefore the advskew on the backup firewall's carp(4) vhids should be set to something higher than the primary's.

https://www.freebsd.org/cgi/man.cgi?pfsync%284%29

Zum Verständnis:

advskew 0 is an optional parameter specifying how much to skew the advbase when sending CARP advertisements. The default value of advbase is one(1) which equates to sending a CARP advertisement 1/256 of a second. If the advskew is zero(0) then the advbase plus advskew still equals one; CARP advertisements will be sent out one per second. By manipulating advskew, the master CARP host can be chosen or forced. The lower the advskew value, the MORE preferred the host will be when choosing a master. The default is 0. Acceptable values are from 0 to 254. Notice the advskew on the master is 0 and the advskew on the backup is 100. If the BACKUP firewall (fw1) ever becomes the master the CARP advertisements will be sent out once every 1.391 seconds (advbase of 1 plus skew of 100/256 seconds).

https://calomel.org/pf_carp.html

Vielleicht liegt es ja einfach daran.