Messages

Looks like that is working!

Thanks.

Having the same issue with the mobile view of the dashboard.

See attached screenshots.
1 menu invisible, 2 after some clicking around found the menu butten.

Hunsn N100 4x i226-v

Code Select Expand

root@router:~ # sysctl dev.cpu.0.temperature
dev.cpu.0.temperature: 26.0C
root@router:~ # sysctl dev.cpu | fgrep dev.cpu.0.temperature
dev.cpu.0.temperature: 27.0C
root@router:~ # sysctl -a | fgrep dev.cpu.0.temperature
dev.cpu.0.temperature: 30.0C
root@router:~ # configctl system sysctl values dev.cpu
{"dev.cpu.3.temperature":"32.0C","dev.cpu.3.coretemp.throttle_log":"0","dev.cpu.3.coretemp.tjmax":"105.0C","dev.cpu.3.coretemp.resolution":"1","dev.cpu.3.coretemp.delta":"73","dev.cpu.3.cx_method":"C1\/mwait\/hwc C2\/mwait\/hwc C3\/mwait\/hwc","dev.cpu.3.cx_usage_counters":"9038 206303 33787","dev.cpu.3.cx_usage":"3.62% 82.81% 13.56% last 1671us","dev.cpu.3.cx_lowest":"C3","dev.cpu.3.cx_supported":"C1\/1\/1 C2\/2\/127 C3\/3\/1048","dev.cpu.3.freq_levels":"806\/-1","dev.cpu.3.freq":"3407","dev.cpu.3.%parent":"acpi0","dev.cpu.3.%pnpinfo":"_HID=ACPI0007 _UID=3 _CID=none","dev.cpu.3.%location":"handle=\\_SB_.PR03","dev.cpu.3.%driver":"cpu","dev.cpu.3.%desc":"ACPI CPU","dev.cpu.2.temperature":"31.0C","dev.cpu.2.coretemp.throttle_log":"0","dev.cpu.2.coretemp.tjmax":"105.0C","dev.cpu.2.coretemp.resolution":"1","dev.cpu.2.coretemp.delta":"74","dev.cpu.2.cx_method":"C1\/mwait\/hwc C2\/mwait\/hwc C3\/mwait\/hwc","dev.cpu.2.cx_usage_counters":"8177 209330 33176","dev.cpu.2.cx_usage":"3.26% 83.50% 13.23% last 804us","dev.cpu.2.cx_lowest":"C3","dev.cpu.2.cx_supported":"C1\/1\/1 C2\/2\/127 C3\/3\/1048","dev.cpu.2.freq_levels":"806\/-1","dev.cpu.2.freq":"3407","dev.cpu.2.%parent":"acpi0","dev.cpu.2.%pnpinfo":"_HID=ACPI0007 _UID=2 _CID=none","dev.cpu.2.%location":"handle=\\_SB_.PR02","dev.cpu.2.%driver":"cpu","dev.cpu.2.%desc":"ACPI CPU","dev.cpu.1.temperature":"31.0C","dev.cpu.1.coretemp.throttle_log":"0","dev.cpu.1.coretemp.tjmax":"105.0C","dev.cpu.1.coretemp.resolution":"1","dev.cpu.1.coretemp.delta":"74","dev.cpu.1.cx_method":"C1\/mwait\/hwc C2\/mwait\/hwc C3\/mwait\/hwc","dev.cpu.1.cx_usage_counters":"95908 1201303 634","dev.cpu.1.cx_usage":"7.38% 92.56% 0.04% last 76us","dev.cpu.1.cx_lowest":"C3","dev.cpu.1.cx_supported":"C1\/1\/1 C2\/2\/127 C3\/3\/1048","dev.cpu.1.freq_levels":"806\/-1","dev.cpu.1.freq":"3426","dev.cpu.1.%parent":"acpi0","dev.cpu.1.%pnpinfo":"_HID=ACPI0007 _UID=1 _CID=none","dev.cpu.1.%location":"handle=\\_SB_.PR01","dev.cpu.1.%driver":"cpu","dev.cpu.1.%desc":"ACPI CPU","dev.cpu.0.temperature":"30.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":"75","dev.cpu.0.cx_method":"C1\/mwait\/hwc C2\/mwait\/hwc C3\/mwait\/hwc","dev.cpu.0.cx_usage_counters":"15920 135827 46052","dev.cpu.0.cx_usage":"8.04% 68.66% 23.28% last 399us","dev.cpu.0.cx_lowest":"C3","dev.cpu.0.cx_supported":"C1\/1\/1 C2\/2\/127 C3\/3\/1048","dev.cpu.0.freq_levels":"806\/-1","dev.cpu.0.freq":"3218","dev.cpu.0.%parent":"acpi0","dev.cpu.0.%pnpinfo":"_HID=ACPI0007 _UID=0 _CID=none","dev.cpu.0.%location":"handle=\\_SB_.PR00","dev.cpu.0.%driver":"cpu","dev.cpu.0.%desc":"ACPI CPU","dev.cpu.%parent":""}

I am not having any troubles with the temprature.
Only posting this because Patrick asked.

Running Intel4 after running Intel3 for 1.5 weeks.
No issues so far!

Running ICMP2 kernel for 22 hours now and not seeing any reconnect from the Chromecast!
I think my Chromecast is the problem.

With icmp2 kernel i see multiple reconnects of a google chromecast "google tv" in my unifi dashboard.

Running kernel pf4 for a while now. And it looks like the reconnects are gone.

Maybe the reverts are the best for 24.7.2

Ship the fix!

And a Confirmation from my side as well!

Windows 11 pro traceroute via IPv6 AND IPv4 is working fine!

Great!

Can't help you with that.
But if more testing is needed today i can help.

opnsense-update -zkr 24.7.1-pf4 restores traceroute functionality.

Experiencing the same behaviour here.

Yes over IPv6!
Tried IPv4, also all records available.

Windows 10 22h2, OPNsense 24.1.1

All records are comming through here!

Code Select Expand

Non-authoritative answer:
dhl.com text =

        "google-site-verification=MKYejQl1Mh9fB5dwrsO9d6xADpVZellFYmDBs6uHvI4"
dhl.com text =

        "mongodb-site-verification=0Crz9iHBXaQyTii6NECBJXDlmyUup51q"
dhl.com text =

        "ms-domain-verification=5253e385-6b1f-4621-b0a0-090e374e40ea"
dhl.com text =

        "Dynatrace-site-verification=8a64ad24-3b3a-4665-b8ac-0975fa5be9f6__a5mepuk85f2o7egbq5cmmlp8tu"
dhl.com text =

        "google-site-verification=HUVzQJOJmKyha5LCFbvFwjCDh5JMkC-85K5C-s44Lt0"
dhl.com text =

        "v=spf1 include:dpdhl._spf.dhl.com include:3a._spf.dhl.com include:3b._spf.dhl.com include:3c._spf.dhl.com include:3d._spf.dhl.com include:3e._spf.dhl.com include:3f._spf.dhl.com include:mrsc._spf.dhl.com include:e2ma.net include:spf.mandrillapp.com ~all"
dhl.com text =

        "docusign=6d733f59-f916-4426-9028-c800fc5e2ba1"
dhl.com text =

        "adobe-idp-site-verification=00c0593e27f3b625df20796c2aea6a9d18005694df716a444a53ac7242f672a1"
dhl.com text =

        "atlassian-domain-verification=mmsERGyn2rlOT8eOe12PbNcvgZ4mxzeOq+e75gQbAYUO3cOhU4Fr7+UfTRKRzrfs"
dhl.com text =

        "facebook-domain-verification=8vnu10tvn6novixz0fkg8ybx26kz1f"
dhl.com text =

        "amazonses:gtMOfHHBB2nwFoX+iXEWovWkRf66WFugJgKxjzCN9Rg="
dhl.com text =

        "onetrust-domain-verification=86d6b6dd18a743d9a30cf4cb40017e84"
dhl.com text =

        "nintex.625eb685a1608f0070bca981"
dhl.com text =

        "atlassian-domain-verification=zCudhHQPIDjcXLKuYWm5QqU2aeaWx4Ccq7RcoJj1KtTXDqxaYKpdcqkH3PnT8C8f"
dhl.com text =

        "cisco-ci-domain-verification=6f8bf0505ee35b0a464c20a0520dd8fd2da5bbfaa26ad53d20d6dc33cd536ab1"
dhl.com text =

        "smartsheet-site-validation=BwFwvtcb2t5Uqeanz8SefQ_4lIZvRQLd"
dhl.com text =

        "Dynatrace-site-verification=f913d8c2-f6d5-4265-9c7f-aae8784c0652__4u08f5qon49tv8mngsmruso1b0"
dhl.com text =

        "pardot1024731=05ff64dc9fea2fd92da4238a7c431480cd48736d513a8dfdeebf552c939afcd0"
dhl.com text =

        "sending_domain1024731=7b1368b64c62a7e74ebee33ffba6d1f1ea1a51f29564c1195a486733b0bc813f"
dhl.com text =

        "hm5bpdz3w772wpzb4xbw649h5dd7f6xs"
dhl.com text =

        "google-site-verification=QsnKi52v6M1z-N3dtyxAopCglJmE4GiEipCLZJxna1Y"
>

Hi,

When i try to issue an certificate for *.example1.com and *.example2.com with DNS alias mode enabled the CN name could not be verified.

It looks like the ACME client is generating twice a txt to the DNS alias provider.
This should be one so the cname record on example1 and 2 is the same and could be verified.

Temp solution
When issuing a certificate without an alternate name set it works.
Right after that adding the alternate name again is works! (Because the first domain is already verified.)


After all it was DuckDNS which doesnt support multiple txt records!
Now using "desec.io" and everything is working fine!