Messages

I 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!

I prioritize core function over looks, so I'm not going to die on this hill, lol. It's a widget people, let's settle down....  But my last point will be that in vicuna, the old widget was beautiful and blended right in.  Simple, clean, clear, not overbearing in-your-face colors, and the small green buttons elegantly indicated running vs the small red buttons indicating stopped were nothing short of UX genius....

With that said, (and only because of this change), that I noticed in my screenshot there does look to be some opportunity to optimize the space it took up without impacting the UI visuals.  So if anyone ever takes a vote, I'm voting for the old clean and clear look, but then just optimize the space if we want to change something. As you can see in my screenshot, there's a country mile between the text and the green buttons.  Win win! Innovation is great and I am truly glad the devs are thinking about how to optimize space.

Or, even just leave it like it was... It was the last thing I expected to change in this update, and honestly didn't even know there was a need before this update. Let's be honest, you only open the page to check the services if something isn't working, then you close the page and move on with life....  It's NOT like you really need to push those buttons all day long and need an OMG Optimized interface to operate them.  :)

1. Login SSH
2. Press 8 for Shell
3. sudo nano /usr/local/opnsense/www/js/widgets/Services.js
4. Copy Contents in Services.js
https://github.com/opnsense/core/blob/stable/26.1/src/opnsense/www/js/widgets/Services.js
5. Reboot

Thank you very much for this tip!

Thanks to one of the users above I found the rebellion theme and on 26.7 it looks much better than vicuna regarding Services Widget. Still, it's not as blended into the panel as before, but livable. It's not like I have to look at it all day every day.  :)  I do certainly prefer the old seamless look of vicuna shown in my earlier screenshots, but I'm just super happy that 26.7 is working well and all things stable.

You cannot view this attachment.

Upgraded to 26.7 without any issues, thanks for the clear release notes (Removed os-cpu-microcode-intel). Congratulations on the new version and thank you for all your hard work!!

I came here because the services widget looked be broken with the way it was rendering after the upgrade.  It turned all black and white vs the nice colored status we had before that blended into the theme. Running vicuna theme here.

(link due to hard limit on attachments)

https://www.pasteboard.co/8JSLaKo_fJJ7.png

I tried the patch from this thread, but it made it worse.

(link due to hard limit on attachments)

https://www.pasteboard.co/4O3RNGbMbuOl.png

Is there any way to get the pre-upgrade colors back that seamlessly blended in using the super modern looking theme vicuna?

For reference, here is the pre-upgrade that blended well.

You cannot view this attachment.

Thanks.

> Please remember, I'm not trying to be unfriendly. I merely want to share our side of the picture, because I feel it gets lost in the excitement and disappointment over trying something new.

Understand, and get it.  No unfriendlies taken at any time.  I also want to clarify that I didn't say "I moved and NEED this one thing", I simply said I really miss it.  ;)  Hearing the Dev side of it I can see why time hasn't been burnt on it, so thanks for sharing that.  But I still miss it.  :)

Regards and best

Completely agree with "Anything that improves the readability and maintainability of firewall rules is not in fact 'non-functional' ".  It's the same reason the "automatically generated" rules are collapsed and out of view.  You just don't want to see those most of the time, but still need them.  I moved from pfsense in the last year, and love OPNsense, but honestly, I miss this ONE feature a lot.  It's just the pure organization visually, and ability to quickly find sections to make adjustments.

In the meantime I just create a disabled "fake rule" with a recognizable comment separator such as:

****************************** Rules for routing clients to VPN ********************************

and put those rules below it.  The only downside is that it's not collapsible.  I hope this can be available some day in the future, but completely understand that resources are limited.

Thanks for all the hard work on OPNsense.

Hi Franco,

I just saw this a few minutes ago which is a duplicate that I didn't initially find in my search. 

https://forum.opnsense.org/index.php?topic=41870.0

It is quite strange that with OPEN auth it seems to function fine.  But the second I enable WPA it fails and gets hung until I completely remove the wifi device and interface. It looks like it's well noted and hopefully these tips can help solving it at some point.

Take care.

What I have figured out is there is something really broken with WPA.  This has always worked beautifully until I got to 24.7.

What I have found so far:
1) Remove the wireless device all together, and remove the interface (setup over from scratch)
2) Reboot and then add it back in under INTERFACE > WIRELESS > DEVICES (listed as run0)
3) When I look under WIRELESS STATUS and it's working!  It can scan and see other access points!
4) Then I set the wireless device to ACCESS POINT and leave as authentication OPEN.  It works!  I can connect to the AP.
5) Now here is where it breaks!  When I enable WPA by clicking the box, the access point disappears and ceases to work going forward

6) Kernel panic!  If I try to go back to open authentication by unchecking WPA, it kernel craps and hard reboots the device.  It shouldn't kernel panic regardless, but something with WPA in 24.7 is really amiss. Picture attached.

I have submitted crash logs through the GUI.  Please let me know how I can troubleshoot this to help get a fix.

Thank you.

Hardware: Qotom-Q355G4

After updating to 24.7, Ralink wifi gets broken and I cannot get it working again.  I use the built in basic wifi just as an isolated IoT for a few basic risky devices, so it's important.  Also I don't even see the SSID being broadcast anymore, so it has me wondering if it's loading properly.  It's there an look correct in Interfaces > Wiresless > Devices.

In the wireless logs I can see that right after upgrade it changes to "WPA rekeying GTK" repeating instead of doing proper handshakes.

Code Select Expand


# cat /var/log/wireless/latest.log

<31>1 2024-07-31T16:43:15-05:00 home.arpa hostapd 7345 - [meta sequenceId="23"] run0_wlan1: STA 22:6a:10:ba:15:73 WPA: received EAPOL-Key frame (2/2 Group)
<30>1 2024-07-31T16:43:15-05:00 home.arpa hostapd 7345 - [meta sequenceId="24"] run0_wlan1: STA 22:6a:10:ba:15:73 WPA: group key handshake completed (RSN)
<31>1 2024-07-31T16:43:15-05:00 home.arpa hostapd 7345 - [meta sequenceId="25"] run0_wlan1: STA 4c:a1:61:04:d8:27 WPA: received EAPOL-Key frame (2/2 Group)
<30>1 2024-07-31T16:43:15-05:00 home.arpa hostapd 7345 - [meta sequenceId="26"] run0_wlan1: STA 4c:a1:61:04:d8:27 WPA: group key handshake completed (RSN)
<31>1 2024-07-31T16:43:15-05:00 home.arpa hostapd 7345 - [meta sequenceId="27"] run0_wlan1: STA 22:6a:10:ba:14:e4 WPA: received EAPOL-Key frame (2/2 Group)
<30>1 2024-07-31T16:43:15-05:00 home.arpa hostapd 7345 - [meta sequenceId="28"] run0_wlan1: STA 22:6a:10:ba:14:e4 WPA: group key handshake completed (RSN)
<31>1 2024-07-31T16:43:15-05:00 home.arpa hostapd 7345 - [meta sequenceId="29"] run0_wlan1: STA 22:6a:10:ba:15:67 WPA: received EAPOL-Key frame (2/2 Group)
<30>1 2024-07-31T16:43:15-05:00 home.arpa hostapd 7345 - [meta sequenceId="30"] run0_wlan1: STA 22:6a:10:ba:15:67 WPA: group key handshake completed (RSN)
<31>1 2024-07-31T16:43:16-05:00 home.arpa hostapd 7345 - [meta sequenceId="31"] run0_wlan1: STA 33:61:32:3a:52:1c WPA: EAPOL-Key timeout
<31>1 2024-07-31T16:43:16-05:00 home.arpa hostapd 7345 - [meta sequenceId="32"] run0_wlan1: STA 33:61:32:3a:52:1c WPA: sending 1/2 msg of Group Key Handshake
<31>1 2024-07-31T16:43:16-05:00 home.arpa hostapd 7345 - [meta sequenceId="33"] run0_wlan1: STA 33:61:32:3a:52:1c WPA: received EAPOL-Key frame (2/2 Group)
<30>1 2024-07-31T16:43:16-05:00 home.arpa hostapd 7345 - [meta sequenceId="34"] run0_wlan1: STA 33:61:32:3a:52:1c WPA: group key handshake completed (RSN)
<31>1 2024-07-31T16:50:10-05:00 home.arpa hostapd 48511 - [meta sequenceId="1"] run0_wlan1: WPA rekeying GTK
<31>1 2024-07-31T16:51:11-05:00 home.arpa hostapd 48511 - [meta sequenceId="1"] run0_wlan1: WPA rekeying GTK
<31>1 2024-07-31T16:52:11-05:00 home.arpa hostapd 48511 - [meta sequenceId="2"] run0_wlan1: WPA rekeying GTK
<31>1 2024-07-31T16:53:10-05:00 home.arpa hostapd 48511 - [meta sequenceId="1"] run0_wlan1: WPA rekeying GTK
<31>1 2024-07-31T16:55:34-05:00 home.arpa hostapd 46747 - [meta sequenceId="1"] run0_wlan1: WPA rekeying GTK


# dmesg | grep run0

Code Select Expand


run0 on uhub1
run0: <Ralink 802.11 n WLAN, class 0/0, rev 2.00/1.01, addr 1> on usbus0
run0: MAC/BBP RT5390 (rev 0x0503), RF RT5370 (MIMO 1T1R), address 24:0a:64:a0:fc:34
run0: [HT] Enabling 802.11n
wlan0: changing name to 'run0_wlan1'
run0: firmware RT3071 ver. 0.33 loaded
run0: firmware RT3071 ver. 0.33 loaded
run0: firmware RT3071 ver. 0.33 loaded


Code Select Expand

#  sysctl -n net.wlan.devices
run0


Anyone know how to troubleshoot this issue with 24.7?

To disable in logs, go to logging, Facilities, and turn off user-level messages, or just disable configd.py all together.

Everything worked flawlessly today with the download and no issues with the update to 27.1.1.  Great work everyone!

Regards

After 3.5 hours it finally gave ".................. failed, signature invalid".

Can anyone suggest a way to manually do the upgrade?

Thanks.

At nearly 2 hours and I think it's stuck.  :-\

Can anyone provide any guidance to anything I can do in terminal to get it moving?

Thanks

I have been stuck on this screen for 60 minutes now and it's making me a bit nervous.  Should I expect this to finish?  The dots are still printing across the screen, but it seems too long.

Looks like fetch is still running:

Code Select Expand

root@opnsense:~ # ps ax | grep fetch
78483  -  S      0:00.28 /bin/sh /usr/local/sbin/opnsense-fetch -a -w 1 -T 30 -q -o /var/cache/opnsense-update/65511/packages-24.1-amd64.tar https://pkg.opnsense.org/FreeBSD:13:amd64/23.7/sets/packages-24.1-amd64.tar
79651  -  Is     0:00.00 daemon: fetch[80174] (daemon)
80174  -  I      0:01.27 fetch -a -w 1 -T 30 -q -o /var/cache/opnsense-update/65511/packages-24.1-amd64.tar https://pkg.opnsense.org/FreeBSD:13:amd64/23.7/sets/packages-24.1-amd64.tar


Package doesn't seem to be increasing in size:

Code Select Expand

root@opnsense:~ # ll /var/cache/opnsense-update/65511/
total 283981
-rw-r-----  1 root  wheel  290586624 Feb 14 20:48 packages-24.1-amd64.tar
-rw-r-----  1 root  wheel       1332 Jan 31 05:46 packages-24.1-amd64.tar.sig
root@opnsense:~ #


Anything else I should check?