Messages

I think I had similar issue after update from 22.1 direct to 22.1.2_1. Yes I skipped 22.1.1
Initially I thought it's my ISP with ipv6 routing issue. I get ipv6 on all local devices just unable to browse the Internet e.g. browser and dns ipv6 lookup failed. No issue with ipv4.

I didnt investiage further and fixed it with delaying the opnsense boot up not sure which work , i just slap both of these in /boot/loader.conf.local
autoboot_delay="60" <--- in second
kern.cam.boot_delay="60000" <--- in millisecond

FYI, I have other devices that need time to boot up, hence I put long delay, if you use these setting please change the value accordingly...

Guys/Gals , please be courteous when reporting and be specific with the problem and make sure it's related to the open thread/topic.

Without giving more information how it crash/logs/etc , i dont think one can help much, except from guessing or by experience guessing.

For myself I dont have any issue at all with unbound since upgraded from 20.7 -> 20.7.6 -> 20.7.7_1. I only run max 23 hours per day and the system will be power-off. Since I saw the report of unbound terminate abnormally, i keep tab on the unbound processes & logs, it's been fine for me - no issue starting from cold boot, no issue of process terminating abnormally, no unbound SIGSEGV/segfault .

I do have custom setting for unbound; e.g.
Bind to certain interface only
DNS over TLS <few IPaddress@853>
DNSSEC enabled
Message Cache size 10MB
Access List <few internal IPaddress>


Of course I do want similar patched applied similar in freebsd ports (https://github.com/NLnetLabs/unbound/issues/376 OR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251821) if this fixes for certain scenario. If there is a need of example on how people log an issue , please refer to the links. They provide at least some log info, description, and possible with scenario, etc.


For the login screen that didnt work, I'm guessing seperate issue that was posted in this forum and/or, something related to HTTP redirect that is fixed on 20.7.7_1 OR related to https://forum.opnsense.org/index.php?topic=20514.0

In all best cases all update/upgrade works, some times we have to work with temporary solution and ofcourse have a permanent solution at a later time. OPNSense provide us an option to roll back , so i dont see any issue with it. I am in no position to say in what scenario warrant a pull of package / release, I'm confident OPNSense team will be able to make the right decision.

If there's something critical to your production and not able to single handed and deal with the situation , i guess it's best to subscribe to the business support.

p/s: my first post , yes i register just for purpose of posting in this specific thread. I dont usually want to post and i just wanted to read topic that interest me. what makes me post this , i guess i cannot escape from my conscious of xxxxxx - does not matters :)