I saw the hot fix for Kernal panics which suggests the correct version
identifies itself as "stable/24.7-n267981-8375762712f" using uname - v
I get the following
root@home:~ # uname -v
FreeBSD 14.1-RELEASE-p6 stable/24.7-n267979-0d692990122 SMP
I have tried to issue the
opnsense-update -fk
and reboot but no change.
Am I miss reading the update notes
Depends on mirror and if it already synced. If in doubt use default mirror.
Cheers,
Franco
sorry to be dumb how do I ensure its the default mirror from the shell
Which one is it then?
# opnsense-update -M
To make quick work of it...
# opnsense-update -sd
# opnsense-update -M
Note setting defaults with opnsense-update is not permanent.
Cheers,
Franco
changed the mirror to default in GUI then tried again from console
root@home:~ # uname -v
FreeBSD 14.1-RELEASE-p6 stable/24.7-n267981-8375762712f SMP
All is good again.
Thanks
always nice to hear from you although it's only when I screw up :D
That is why we don't speak often it's very rare you do
Oh and Orange France is behaving themselves now which makes life much easier.
> Oh and Orange France is behaving themselves now which makes life much easier.
Splendid, when did that happen? Or just no more custom changes on their end to make our lives harder?
Cheers,
Franco
Orange published a list of connection requirements some time ago. If you stick to them (various send options in defined format etc), the connections are very stable.
TLDR
https://lafibre.info/remplacer-livebox/durcissement-du-controle-de-loption-9011-et-de-la-conformite-protocolaire/
Ah neat to have this on file, thanks!
Interestingly, I'm facing the exact same issue even though I'm on the default mirror.
For info, none of my upgrades picked up the new kernel although I think all are using the default mirror, to which I had returned after a previous problem.
I have two production (bravely titled for a home user) routers, one being perimeter and one internal, and a backup/test machine. All were updated from 24.7.9 to 24.7.10_1, then _2 and none finished with the newer kernel. Only the perimeter router kept panicking, slipping past my prior updates on the less critical machines which did not at all. It was stable overnight but panicky in use. All the machines/CPUs are different, not ideal for QC.
The terminal procedures for kernel update appear to have fixed it, and the others updated likewise.
Quote from: passeri on December 05, 2024, 12:41:46 AM
The terminal procedures for kernel update appear to have fixed it, and the others updated likewise.
Can you clarify "the terminal procedures for kernel update" so that I can give that a shot myself?
Quote from: Malmoth on December 05, 2024, 05:02:16 AM
Can you clarify "the terminal procedures for kernel update" so that I can give that a shot myself?
See this link
https://forum.opnsense.org/index.php?topic=44413.msg221775#msg221775
> Interestingly, I'm facing the exact same issue even though I'm on the default mirror.
"uname -v" please. We've already had one user using "opnsense-update -fk" wondering why they land on a 24.7.8 kernel which is entirely correct when you are not on 24.7.10 yet in which case the kernel hotfix procedure doesn't matter anyway. :)
Cheers,
Franco
Quote from: franco on December 05, 2024, 08:37:50 AM
"uname -v" please. We've already had one user using "opnsense-update -fk" wondering why they land on a 24.7.8 kernel which is entirely correct when you are not on 24.7.10 yet in which case the kernel hotfix procedure doesn't matter anyway. :)
Apologies if I haven't been clear. By the exact same issue, I did mean the exact same issue. I did receive the original update, and than 24.7.10_2. And I currently am stuck at stable/24.7-n267979-0d692990122.
Quote from: AhnHEL on December 05, 2024, 05:53:16 AM
See this link
https://forum.opnsense.org/index.php?topic=44413.msg221775#msg221775
But these are already the steps outlined in the release notes themselves. These are the steps that I've tried, just like nivek1612, but despite the fact that I'm on the default mirror, it just doesn't update the kernel.
I misunderstood what passeri was talking about when they mentioned "the terminal procedures." I thought they were using "terminal" in reference to "last" or "final," as in they were referring to some sort of last ditch option that wasn't referenced earlier. That was just me being silly.
Maybe I was doing something wrong with the GUI option. I basically used the "Reinstall" button for the "opnsense" package. I assume that's what the "reinstall from the GUI" meant in the release notes. Am I right?
Regardless though, "opnsense-update -fk" should work, but it doesn't.
Did you reboot to boot into the updated kernel? The Cloudflare mirror could be playing tricks again if you have that one set.
Cheers,
Franco
Of course. That was part of the manual update instructions.
Didn't realize the default mirror relies on Cloudflare. I guess I'll just have to wait until Cloudflare invalidates caches on their backend.
I can assure you the default mirror is fine. It only has one kernel file and it's the right one.
Cheers,
Franco