Feedback on new Widgets since 26.7

[JohnSchnee]

Hi there,

today I was updating from 26.1.11 to 26.7.

As always the update went smooth, thanks for the great work guys. (Even on Hyper-V, I don't had kernel Panics)

However, the new Service Widget looks not great and does not blend in well with the other GUI Elements. (Black writing on green background)

Thats of course only my personal opinion. Maybe others find the new design more helpful, the advantage might be that a failed service is more visible.

Is there any possiblity to let users choose from the two designs. I was just super satisfied with the old one.

I've added you a screenshot of an old test-build with my typical Web-Interface-Design and a small Picture how it looks with the new design.

Keep the good work up and best regards!

[franco]

Which theme is that? The colors correspond to the bootstrap alert "danger" and "success", which can be adjusted by the theme author. I agree the green doesn't look good here, but that's not the fault of the widget.


Cheers,
Franco

[Monviech (Cedrik)]

Out of curiosity,
- whats the hardware you use for Hyper-V (CPU architecture etc...)
- whats the OS? (Windows 11, Windows Server version...) Is it up to date, all latest patches?
- how is the VM configured? -
    - gen1 or gen2...?
    - configuration version (11.0, 12.0...)
    - how many virtual processors (1,2...?)

Thank you.

[AhnHEL]

I think the grey text in the green box just doesnt have enough contrast.

You can easily change the text color for yourself in the shell with vi

usr/local/opnsense/www/js/widgets/Services.js


Change both instances of the following text:

color: rgb(55, 55, 54);

to

color: rgb(230, 230, 230);

Save the file and reload your dashboard webpage.

This will give you white text instead of that dark grey for both the Service name and the Status icons.

I think it cleans it up a bit while we wait for all the themes to be updated.

Screenshot attached is with the Flexcolor Theme which is my personal Theme choice.

**Edited to add following to post:
Although I did some more editing to the Theme itself to get that green color for running Services..

/usr/local/opnsense/www/themes/flexcolor/build/color_schemes/black/default_scheme.css

Change colors in lines 109 and 209 from 000000 to 388E3C

/* alert success */
    --alertsuccessfore: #E6E6E6;
    --alertsuccessback: #388E3C;
    --alertsuccessborder: #36D93E;

and

/* success button */
    /* unselected */
    --sbtnfore: #388E3C; /* textcolor */
    --sbtnback: #388E3C; /* background */
    --sbtnborder: #388E3C; /* border */

In Shell, issue command

#  service flexcolor restart

Refresh Dashboard in browser

[JohnSchnee]

Hi there,

thank you so much for the quick answers and the feedback.

My Hyper-V Config is:

- Based on Windows 11 25H2, latest Jul Update installed
- VM-Config Version is 12.0
- Gen-2 VM with TPM, Secure-Boot & Shielded VM enabled
- 12 vCPUs and 16 GB RAM configured

Physical Hardware: Ryzen 5 5600G, A520 Chipset, 64 GB RAM, BCM5720-2P Ethernet + Onboard RTL 8116 Ethernet

No Hyper-V based Snapshots, only PCIe based NICs (if that can make a difference).

I've also added a Screenshot of the "Integration Services TAB".

The theme I'm using is Rebellion, and I'm afraid to say, it's more about the layout of the new Widget and how it blends in with the other UI Elements.

Maybe it would be a compromise, if both (old and new) have their existence and the new one is the "Compact" Version.

But yeah, life and maybe a firewall isn't a "Wish-Concert", so I could survive with the new one.

Just my honest feedback.

Regards

[Monviech (Cedrik)]

Hello John,

thank you. We have almost the same hardware, but I am affected by this in every VM:
https://github.com/opnsense/src/issues/297

My Hyper-V Config:
- Windows 11 25H2 Build 26200.8875
- VM Config Version 12.0
- Gen2-VM, but TPM, secure boot and shielded VM are disabled
- 4vCPU and 8GB RAM

Physical Hardware: AMD Ryzen 9 3900X, AMD X570 chipset, 64GB RAM, Intel(R) I211 Gigabit Network Connection

Integration tab has "Shutdown" and "Guest Services" checked.

It's really strange.

-> On the working VM, do you have Unbound enabled?
-> On the working VM, can you give the output of "sysctl hw.vmbus.tlb_hcall" - The command is for the OPNsense shell (log in as root, option 8)
    (My VM reports hw.vmbus.tlb_hcall: 1)
-> Can you maybe boot the latest 26.7 image in a new VM (2 vCPUs or more) and tell me if the installer kernel crashes?

[dseven]

Regarding the Services widget (original topic), there was some discussion about it already in https://forum.opnsense.org/index.php?topic=52380.0

I'm thinking that an "LED" (instead of the background) to show the status of each service would be more in-keeping with the "look and feel" of the UI... but, of course, at the expense of some "compactness"...

[JohnSchnee]

Hi Cedrik,

I've tested it with both mine and your settings and the VM didn't crash.

I booted and logged in with "Installer" - so I expect the crash should have occured before this point?

Curiously I wasn't able to enable Secure-Boot for this VM, but I know I had a long fight to get this working, so I better don't touch my current config. :D

I'm using Unbound cascaded with the AdGuard-Plugin as DNS, where AD-Guard is my Upstream and Unbound the "internal" DNS.

I've added a Screenshot where you can see the Kernel Version as evidence of a successfull boot with 12 vCores

Best regards

[Monviech (Cedrik)]

Hello John,

thank you thats really valuable. That means your Hyper-V VMs are not affected.

One last thing, can you tell me about this:

-> On the working VM, can you give the output of:

sysctl hw.vmbus.tlb_hcall

command is for the OPNsense shell (log in as root, option 8)

[JohnSchnee]

Hi,

Input:
sysctl hw.vmbus.tlb_hcall

Output:
hw.vmbus.tlb_hcall: 1

If you need anything more, let me know.

Regards

[Monviech (Cedrik)]

Hello John, thank you. That's all for now.

I cannot explain the difference here, but knowing that the blast radius of the issue is very reduced (I just know of myself, and one other upstream report in Freebsd) that's already quite valuable. Though its annoying its not a generic issue, since now it's less important to fix it.

[nero355]

I cannot explain the difference here

I think it could be simply this :

Ryzen 5 5600G, A520 Chipset

vs.

AMD Ryzen 9 3900X, AMD X570 chipset

AMD fixing stuff 2 generations later and not telling anyone about it sounds very typical for them ;)