Messages

Let's just try this one:

# opnsense-update -zkr 24.7.r1_2

I placed a bet...


Cheers,
Franco

Sorry for partially missing the tests. Submited a crash report after boot with this one but didn't see a "panic" in dmesg-

We were wondering if this does this also crash with the beta kernel? Because it sort of indicates that it didn't before.

# opnsense-update -kr 24.7.b


Cheers,
Franco

Let's try it out ;-)
Already downloaded, reboot is happening in a sec.

I'm now running the following kernel:

Code Select Expand


FreeBSD OPNsense.localdomain 14.1-RELEASE FreeBSD 14.1-RELEASE stable/24.7-n267717-cf61c67cb34 SMP amd64


I will keep you updated, but directly after the reboot no panic happen.

did the same and also no panic after reboot

I can also confirm this issue and also submitted a report

Just to add to the discussion, I'm having a similar but different problem. I migrated to opnsense recently so I'm new with it but I'm experiencing a weird issue. I'm trying the combined use of opnsense and pihole so decided to add another pihole in a sbc I had stored somewhere. Now comes the weird part, it was assigned a dynamic IP but I changed it to a static one outside my dynamic pool. Now I have 2 IPs for the same device (they don't appear both in leases) and I can ssh using any of the IPs. Also the pihole management page can be reached with both IPs. I tried to erase the dynamic IP in some places like "/var/dhcpd/var/db/dhcpd.leases" but it always comes back. I also tried to remove the static IP but the device still gets that IP even after reboot as I can reach it with through it. Probably because of this, if I set it as my only pihole it doesn't receive any hits and is bypassed.
I don't know what else to do (the sbc is running ubuntu 18.04).

Sent from my Redmi Note 8 using Tapatalk