Hi all,
thanks to the team for the great work! Friction between OPNsense and upstream FreeBSD aside 15.1 is a big step forward for both projects.
- The update showed no major problems here.
- The mimugmail-single repo is not yet up to the new ${ABI}, but the old binaries still work, no service outage whatsoever.
- Nut is finally working again with the default packages.
- To get a consistent view of the plugins I needed to completely disable the mimugmail-single repo, perform "pkg update", then they switched from "orphaned" to "installed".
- I don't like the look of the new services widget. Like at all, sticks out like a sore thumb. But I can live with it. At least please put a proper header on it as someone else already suggested.
Again: double thumbs up!
Patrick
Hey,
I will join too, even though I did not yet upgrade to the official Major, but I did test the RCs.
- It is true that the new service widget is sticking out - its too eye candy, but I kinda like it due to 2 reasons:
* Its eye poking so its hard to miss something is down
* It takes less space compared to the old one
- The new Interfaces pane of view is a welcome change, its more consistent with the overall style
- The Additional MVC/API integrations - hell yea!
- Adjustments on the Live log widget, this is already there prior the Major, but I would like to still thank for it, its awesome
Thank you all for the hard work and I am personally glad we landed on FBSD 15.1!
Regards,
S.
Hi Patrick,
Thanks for your fast feedback. :)
>- The mimugmail-single repo is not yet up to the new ${ABI}, but the old binaries still work, no service outage whatsoever.
Michael was working on it this week. Hoping to see it up shortly.
>- Nut is finally working again with the default packages.
That's nice to hear!
>- To get a consistent view of the plugins I needed to completely disable the mimugmail-single repo, perform "pkg update", then they switched from "orphaned" to "installed".
Yep, this is expected. Faulty repositories should always be removed.
> - I don't like the look of the new services widget. Like at all, sticks out like a sore thumb. But I can live with it. At least please put a proper header on it as someone else already suggested.
The colours can be changed per theme. We wanted to wait a bit and see which other complains are coming up. I'm not a fan of the header for available space reasons so maybe we can find another way to make it more obvious.
Cheers,
Franco
I am with Patrick regarding the new services widget. It just doesnt' fit with the rest of the gui.
For the widget it would be better if only the borders were colored per each process per state.
Regards,
S.
Hum, the latest service widget appearance was far better as my "home" is on 4 columns, the last one dedicated for services list ... well, not a big deal, upgrade was smooth, thanks
Quote from: franco on Today at 01:11:22 PMI'm not a fan of the header for available space reasons so maybe we can find another way to make it more obvious.
I'd like it to look more consistent with the rest of the widgets.
I also never liked the not quite so new dashboard for the simple reason that the widgets do not snap to a fixed grid. Height should always be a multiple of X and vertical space between widgets should automatically create "lines" spanning multiple columns where appropriate. I hope you understand what I mean. I created an attachment. That's driving me up the walls. Honestly :-)
Kind regards,
Patrick
The design language of the widget is completely different from rest of the project.
That being said it's very space efficient and you can very easily identify what is enabled and what disabled.
I've updated successfully a few (ZFS) devices with various configurations, and also an APU4 running on UFS.
Big thanks to the team for the time and effort that went into this release.
Looking forward to seeing the OpenSSH 10.4 update in 26.7.x (was published too late to be included in 26.7)
Quote from: Patrick M. Hausen on Today at 01:18:18 PMThat's driving me up the walls. Honestly :-)
me too :)
Regards,
S.
Well I'm happy the biggest "issue" is just a widget so far, lol. :)
Carrot 🥕 and stick ? Rally the masses against a common enemy and get away with everything else.
For 27.1 we'll have IPv6 and IPv8 only networks.
FWIW... I upgraded a test instance this morning, and my first reaction to the widget was "WTF is that?? Is it a glitch? Hmm, actually, it looks kindof useful, but ugly!". Without a header, at least in dark mode, it looks like it's (erroneously) part of the widget above.
Maybe just add an option? Simple checkbox "show header". Even with the header added the new widget saves so much space, I'd say mission accomplished.
Another thing that has been bugging me for years, but I'll open a request on Github: the CPU graph should be fixed to 100%.
I need to quickly discern:
- squiggly line at the bottom - I don't care if it's 3% or 11%, mostly idle is all the info I need
- 50%-ish
- at the top - ok, the CPU is maxed out, let's check if that is a problem or not
Autoscaling for CPU (or for any other limited capacity) does not make sense, IMHO. Memory, bandwidth, ... all the same. It should scale to the maximum that I have (16 GB, 1 Gbit/s, ...) so I can check with one glimpse how much of what I have is used.
Kind regards,
Patrick
@Patrick, can you get into Services->NUT->Configuration? I am seeing a crash when I try. I can get into Diagnostics and it shows my UPS status, so it appears that NUT is running. I tried uninstalling and reinstalling the NUT plugin, but that did not fix it.
Same here. I submitted the crash report. But this does not look like the known Nut segmentation fault but rather like a UI/Frontend problem.
Thanks Patrick. I created an bug report: https://github.com/opnsense/core/issues/10534