"Recent posts
#1
26.7 Series / Re: Services widget
Last post by franco - Today at 09:58:33 PMPatrick, I addressed your concerns here: https://github.com/opnsense/core/issues/10553#issuecomment-5062751182
Cheers,
Franco
Cheers,
Franco
#2
General Discussion / Re: Help needed to update boot...
Last post by hushcoden - Today at 09:55:50 PMI'm not particularly tech-savvy, and judging by the number of typos I make, I may well have undiagnosed dyslexia or something similar 😄
So yes, I ask questions that may seem obvious or "silly" to more experienced users. But hey, why someone would spend his/her own time writing unhelpful replies that don't actually answer the question is totally beyond my comprehension.
That said, I must have installed the script at some point in the past, I just don't remember when or why.
I can see the output of the option help, but it doesn't help ma at all:
That's precisely why I'm asking about the correct way to update the bootloader, so if anyone knows the current recommended method, I'd genuinely appreciate the information.
So yes, I ask questions that may seem obvious or "silly" to more experienced users. But hey, why someone would spend his/her own time writing unhelpful replies that don't actually answer the question is totally beyond my comprehension.
That said, I must have installed the script at some point in the past, I just don't remember when or why.
I can see the output of the option help, but it doesn't help ma at all:
Code Select
loaders-update v1.3.2
Usage: loaders-update mode [-befgqry] [-m efi_mount_dir] [-s loaders_source_dir]
mode can be one of:
show-me: just show the commands to type, change nothing.
shoot-me: may update the loader(s), but ask for confirmation before each one.
Options:
-b: scan only BIOS loaders (excludes EFI loaders).
-e: scan only EFI loaders (excludes BIOS loaders).
-f: won't check the freebsd-boot content for BIOS loaders update.
-g: force to use 'gpart show' for disk detection.
-q: quiet mode. No output to the console.
-r: won't check the root file system for BIOS loaders update.
-y: answer yes for shoot-me mode. Use with caution!
Return codes:
0: no error.
1: an error occured.
2: at least one loader isn't up-to-date.
3: = 1 + 2.
That's precisely why I'm asking about the correct way to update the bootloader, so if anyone knows the current recommended method, I'd genuinely appreciate the information.
#3
Intrusion Detection and Prevention / Suricata not exiting on stop i...
Last post by jordanwmcdonald - Today at 09:47:49 PMThe old "suricata in IPS mode won't stop cleanly, GUI says stopped but the process is still running, needs a manual kill" behavior is well known from the netmap days (opnsense/core#3868, #4257, #710; and here on the forum, "Hanging at reboot: stopping suricata" back on 21.7). I ran into what looks like the same class of thing in the newer Divert mode, and in my case it hung a reboot badly enough to be worth flagging. I put the reboot details in opnsense/core#10567.
Setup here: 27.1.a devel, Divert (IPS), 12 divert threads (-d 8000 x12), a single narrow divert-to flow that sees very little traffic. On stop, suricata caught SIGTERM (procstat -i: TERM --C) and started shutting down but never exited. rc.d/suricata stop then sat in pwait for over 90 minutes. procstat showed the divert worker threads parked in sbwait/select on the divert socket, plus a few in umtx waits. My best guess is the workers are blocked reading the divert socket with nothing to wake them on this quiet flow, so the shutdown never completes, but it's only a guess.
Is the divert-mode stop hang tracked separately from the old netmap lockups, or is it the same known "kill it and move on" behavior? I can characterize it further if that helps (traffic during the stop, thread count, PCAP vs divert). Otherwise I'll keep a kill -9 in my stop path and leave it there.
Setup here: 27.1.a devel, Divert (IPS), 12 divert threads (-d 8000 x12), a single narrow divert-to flow that sees very little traffic. On stop, suricata caught SIGTERM (procstat -i: TERM --C) and started shutting down but never exited. rc.d/suricata stop then sat in pwait for over 90 minutes. procstat showed the divert worker threads parked in sbwait/select on the divert socket, plus a few in umtx waits. My best guess is the workers are blocked reading the divert socket with nothing to wake them on this quiet flow, so the shutdown never completes, but it's only a guess.
Is the divert-mode stop hang tracked separately from the old netmap lockups, or is it the same known "kill it and move on" behavior? I can characterize it further if that helps (traffic during the stop, thread count, PCAP vs divert). Otherwise I'll keep a kill -9 in my stop path and leave it there.
#4
26.7 Series / Re: Services widget
Last post by Patrick M. Hausen - Today at 09:46:57 PMQuote from: franco on Today at 09:30:59 PMWhich part of https://github.com/opnsense/core/issues/7887 made it seem like we didn't want feedback from the community since 2024 about the subject?
I never noticed any discussion of this on the forum and I do not follow Github unless I open an issue or a merge request. First time I saw this: today.
Also I still do not quite understand what was bad about the old widget. But then I never work from mobile devices. "Working" means I am at my desk with a real keyboard and a reasonably sized monitor and I design all my dashboards of all products I use for that environment alone. Resolution of a Macbook Pro is large enough to not notice much of a difference when e.g. traveling.
Was that the initial motivation? Smaller screens? But then the entire dashboard is not specifically mobile friendly, so I'm still a bit puzzled why this effort was made at all. It is/was a long list. So be it :-)
Kind regards,
Patrick
#5
General Discussion / Re: Help needed to update boot...
Last post by franco - Today at 09:46:35 PMQuote from: meyergru on Today at 09:23:57 PMBesides: loaders-update is neither installed nor available on OpnSense, is it?
May make sense to add it if it's safe for our standard installation modes, but we need to have a few conversations first.
Cheers,
Franco
#6
Tutorials and FAQs / Re: OPNsense aarch64 firmware ...
Last post by Maurice - Today at 09:43:04 PMOPNsense 26.7.1 aarch64 packages and sets released. Includes hotfix 26.7.1_1.
#7
26.7 Series / Re: Services widget
Last post by franco - Today at 09:30:59 PM> Criticism is a natural part of any project and something that has to be accepted and dealt with constructively.
It has to be a pretty big misunderstanding.
Which part of https://github.com/opnsense/core/issues/10553 made it seem like I wasn't listening last week already?
Which part of https://github.com/opnsense/core/issues/7887 made it seem like we didn't want feedback from the community since 2024 about the subject?
Cheers,
Franco
It has to be a pretty big misunderstanding.
Which part of https://github.com/opnsense/core/issues/10553 made it seem like I wasn't listening last week already?
Which part of https://github.com/opnsense/core/issues/7887 made it seem like we didn't want feedback from the community since 2024 about the subject?
Cheers,
Franco
#8
General Discussion / Re: Help needed to update boot...
Last post by RES217AIII - Today at 09:28:10 PMHello.
I'm not sure if I'm in the right place here or if I'm hijacking the forum thread. If so, please accept my apologies.
My installation is getting on in years, too—four years old.
The update to 26.7 went smoothly, as usual.
Many thanks to the team!
However, before I could bring myself to proceed, I closely followed the discussion regarding the bootloader update and the "microcode problem." There were several discussions about it. This raises the question for me: who actually needs a bootloader update? And how do I determine whether I need this bootloader update?
Many thanks,
Bernd
I'm not sure if I'm in the right place here or if I'm hijacking the forum thread. If so, please accept my apologies.
My installation is getting on in years, too—four years old.
The update to 26.7 went smoothly, as usual.
Many thanks to the team!
However, before I could bring myself to proceed, I closely followed the discussion regarding the bootloader update and the "microcode problem." There were several discussions about it. This raises the question for me: who actually needs a bootloader update? And how do I determine whether I need this bootloader update?
Many thanks,
Bernd
#9
General Discussion / Re: Help needed to update boot...
Last post by meyergru - Today at 09:23:57 PMBesides: loaders-update is neither installed nor available on OpnSense, is it?
#10
26.7 Series / Re: Services widget
Last post by fuskadoo - Today at 09:23:16 PMQuote from: Mabub on Today at 09:14:40 PMI think it may have been misunderstood.
Please consider the entire post.
Completely agree, and please consider those of us trying to help with suggestions.
@Franco, #10553 above is brilliant! Thank you!
