OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Profile of AhnHEL »
  • Show Posts »
  • Messages
  • Profile Info
    • Summary
    • Show Stats
    • Show Posts...
      • Messages
      • Topics
      • Attachments

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.

  • Messages
  • Topics
  • Attachments

Messages - AhnHEL

Pages: [1] 2 3 ... 5
1
24.7 Production Series / Re: Temperature: Dashboard Temps differ massively from CLI
« on: December 01, 2024, 06:57:35 pm »
I think meyergru is tired of repeating his answers and he's not wrong.

You are using cpu cycles to run that command and one is a lot more intensive than the other which is why there is a difference in the temps.  That answers questions 1 and 2.

To answer your third, I would rely on the "sysctl dev.cpu | grep temperature | sort" more since its showing the temperature with the command skewing the results the least.

2
23.7 Legacy Series / Re: CPU temp reporting
« on: November 29, 2024, 07:16:24 pm »
The 'pchtherm0.temperature' is the only relevant reading so the others should just be omitted/ignored for the widget.  Then again if the dev.cpu readings are available, do we even need the pchtherm at all for the widget?

3
Hardware and Performance / Re: Is this a good device for Opnsense?
« on: November 28, 2024, 03:23:05 am »
A Lenovo M920q is about $140.  Add the PCIE16 Riser Card 01AJ940 with baffle for $35 and attach that to a Intel i350-t2 or t4 and you'll have something much better and dependable than those Aliexpress boxes in my opinion.


https://forums.servethehome.com/index.php?threads/lenovo-thinkcentre-thinkstation-tiny-project-tinyminimicro-reference-thread.34925/

4
23.7 Legacy Series / Re: CPU temp reporting
« on: November 27, 2024, 07:50:05 pm »
Thank you, yes.

# configctl system sensors
dev.cpu.0.coretemp.tjmax
dev.cpu.0.temperature
dev.cpu.1.coretemp.tjmax
dev.cpu.1.temperature
dev.cpu.10.coretemp.tjmax
dev.cpu.10.temperature
dev.cpu.11.coretemp.tjmax
dev.cpu.11.temperature
dev.cpu.2.coretemp.tjmax
dev.cpu.2.temperature
dev.cpu.3.coretemp.tjmax
dev.cpu.3.temperature
dev.cpu.4.coretemp.tjmax
dev.cpu.4.temperature
dev.cpu.5.coretemp.tjmax
dev.cpu.5.temperature
dev.cpu.6.coretemp.tjmax
dev.cpu.6.temperature
dev.cpu.7.coretemp.tjmax
dev.cpu.7.temperature
dev.cpu.8.coretemp.tjmax
dev.cpu.8.temperature
dev.cpu.9.coretemp.tjmax
dev.cpu.9.temperature
dev.pchtherm.0.ctt
dev.pchtherm.0.pmtemp
dev.pchtherm.0.t0temp
dev.pchtherm.0.t1temp
dev.pchtherm.0.t2temp
dev.pchtherm.0.temperature

5
23.7 Legacy Series / Re: CPU temp reporting
« on: November 27, 2024, 07:12:04 pm »
@franco I applied the patch, can it omit the tjmax graph outputs?  Its not easy on the eyes.  I'm still having issue with the pchtherm.0 section that shows up as another CPU0.

6
23.7 Legacy Series / Re: CPU temp reporting
« on: November 27, 2024, 06:25:51 pm »
@meyergru  It looks like that second CPU0 belongs to dev.pchtherm.0 but then why does the formatting in the widget express it as CPU0?

7
23.7 Legacy Series / Re: CPU temp reporting
« on: November 27, 2024, 05:06:35 pm »
Quote from: meyergru on November 27, 2024, 10:22:52 am
I wonder what second CPU0 you had? Could you show the output of:

Code: [Select]
sysctl -e `sysctl -aN | fgrep temperature` | sort


root@angel:~ # sysctl -e `sysctl -aN | fgrep temperature` | sort
dev.cpu.0.temperature=32.0C
dev.cpu.1.temperature=32.0C
dev.cpu.10.temperature=33.0C
dev.cpu.11.temperature=33.0C
dev.cpu.2.temperature=40.0C
dev.cpu.3.temperature=40.0C
dev.cpu.4.temperature=34.0C
dev.cpu.5.temperature=34.0C
dev.cpu.6.temperature=32.0C
dev.cpu.7.temperature=32.0C
dev.cpu.8.temperature=39.0C
dev.cpu.9.temperature=39.0C
dev.pchtherm.0.temperature=35.0C

vs.

sysctl -e `sysctl -N dev.cpu hw.acpi.thermal | fgrep temperature` | sort

sysctl: unknown oid 'hw.acpi.thermal'
dev.cpu.0.temperature=32.0C
dev.cpu.1.temperature=32.0C
dev.cpu.10.temperature=32.0C
dev.cpu.11.temperature=32.0C
dev.cpu.2.temperature=30.0C
dev.cpu.3.temperature=30.0C
dev.cpu.4.temperature=33.0C
dev.cpu.5.temperature=33.0C
dev.cpu.6.temperature=31.0C
dev.cpu.7.temperature=31.0C
dev.cpu.8.temperature=32.0C
dev.cpu.9.temperature=32.0C

8
23.7 Legacy Series / Re: CPU temp reporting
« on: November 27, 2024, 06:47:28 am »
Works for my box, I prefer it @Meyergru's way.

I have a i5-10500 and I have two CPU0's displayed and judging by the temps, the second CPU0 was the Zone.  A minor gripe but with dev.cpu I just have CPU0 - CPU11 and I like it better like that.

9
General Discussion / Re: GEOip list update rate
« on: November 25, 2024, 11:32:31 pm »
According to my Maxmind Download History, an attempt is indeed made every 24 hours.  What you're seeing is that there hasnt been a newer file to download since 11/22.   All is fine.

10
24.7 Production Series / Re: DDNS with Porkbun - Req to update API hostname
« on: November 07, 2024, 08:45:07 pm »
Thank you both for your replies.

I've currently switched to Caddy to avoid any timing issues if the plugin isnt updated in time.  The maintainers at ddclient seem to be slow to get the commit merged.

11
24.7 Production Series / DDNS with Porkbun - Req to update API hostname
« on: November 06, 2024, 11:48:26 pm »
I've been using the ddclient backend with Porkbun for some time now and its been working flawlessly.  I've recently have been getting notifications from my Porkbun account that the API Hostname is going to be changed and that if I dont update the API hostname that the API will cease to work and it gives me a deadline of 12/1/24 to sort this out.

Is it possible someone can update the os-ddclient plugin to reflect this change please?  The letter I received is pasted below.

Code: [Select]
Hello there,

The reason you are receiving this email is because you have an API key associated with your account and are sending commands to a deprecated API hostname. We sent a previous warning on 2024-10-11. In order to ensure that any apps or tools you may have that utilize our API continue to work, we wanted to let you know about some upcoming critical updates.

We know these kinds of changes are annoying but the time has come to separate the processing of incoming API commands from our website. In previous documentation the hostname porkbun.com was used for the API but we have recently updated it to api.porkbun.com and in the near future will start enforcing its use. Please update the hostname for our API to api.porkbun.com as soon as possible.

CRITICAL UPDATE DETAILS

Type: API Hostname Change

Old Value: porkbun.com

New Value: api.porkbun.com

Deadline: 2024-12-01 00:00:00 UTC

Please note that after the deadline, API calls made to the old hostname will no longer be allowed. If you have any questions or concerns please contact support.


Thank you,
The Porkbun Team

12
24.7 Production Series / Re: UPnP no sessions appearing
« on: September 21, 2024, 04:50:43 pm »
Check your port forward rules, looks like one of your redirects is causing a conflict.

13
24.7 Production Series / Re: Disable hardware checksum offload
« on: September 21, 2024, 04:44:40 pm »
If you have SSH or console access, you  can select Option 13 and choose a backup prior to the changes that locked you out.

14
General Discussion / Re: UPnP service doesn't seem to work
« on: September 04, 2024, 11:56:16 pm »
Have you tried using the following port range?

allow 88-65535 192.168.1.100 88-65535

Source ports are randomized so using a static port wont match unless you've made a specific static outbound NAT rule.  And check off Log Packets if you like.

My UPnP Service Status shows multiple connections to the Gaming Consoles I use UPnP for.

15
24.7 Production Series / Re: FQ-Codel for bufferbloat reduces upload speed by 4
« on: August 21, 2024, 05:03:02 am »
I have the same config as you with some minor differences in the bandwidth speeds and I don't use ECN within the Queues.  ECN is only enabled on the Pipes.  I'm not seeing the symptoms you're seeing though.  How's your CPU usage when running these speedtests?

Pages: [1] 2 3 ... 5
OPNsense is an OSS project © Deciso B.V. 2015 - 2024 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2