OPNsense Forum
Archive => 22.1 Legacy Series => Topic started by: franco on May 25, 2022, 08:53:28 pm
-
Hi all,
Quick kudos to FreeBSD people for smooth managing of 13.1 this time around that also fits our release window nicely. The release notes can be found here:
https://www.freebsd.org/releases/13.1R/relnotes/
Since 22.1 is based on 13-STABLE some changes may already be included as documented therein. Yet the plan for 22.1 was to stay as close to 13.1 as possible so the next phase of the plan goes forward as we adopt the actual 13.1 code base for the upcoming 22.7 release series. We also managed to upstream a few small things so we can get rid of a bit of custom patching in our source code.
As such, the operating system between 22.1 and 22.7 is interchangeable so for anyone wondering about new features or driver changes there now is a public beta test to preview. The command to install is as follows:
# opnsense-update -bkzr 22.7.b
# opnsense-shell reboot
(reboot now or later, but must reboot to load the new OS)
For anyone looking to switch back the firmware upgrade will try to move you back to 22.1.x base/kernel sets unless you lock both packages from the firmware GUI page.
Note of care for kmod users (specifically Realtek and WireGuard within our immediate reach):
Your kernel module was built for an older FreeBSD version and may not work correctly or outright refuse to load upon reboot. Your only choice is to rebuild it from the correct source version or revert back to 22.1.x.
Feedback? Questions? Happy testing!
Cheers,
Franco
-
Thank you for the fixes in 22.1.8 as well as providing an onramp to beta test 13.1-RELEASE.
What does the upgrade cycle look like if we go to 22.7.b for when 22.7 proper is released? Is that just an opnsense-update jump away to get on the 22.7 series proper once released?
-
# opnsense-update -bkzr 22.7.b
If i run `opnsense-update -bkzr 22.7b` on my OPNsense 22.1.8 VM, I get the following error:
Fetching base-22.7b-amd64.txz: ..[fetch: https://pkg.opnsense.org/FreeBSD:13:amd64/snapshots/sets/base-22.7b-amd64.txz.sig: Not Found] failed, no signature found
--- Edit ---
I missed one dot ... I typed opnsense-update -bkzr 22.7b instead of opnsense-update -bkzr 22.7.b
I updated my two OPNsense VMs (HA Cluster) and they seem to work fine, no errors yet :)
-
Updated and everything ok so far.
But then it started to be a little confusing.
Dashboard/System information shows:
OPNsense 22.1.8-amd64
FreeBSD 13.1-RELEASE
OpenSSL 1.1.1o 3 May 2022
and
¨Click to view pending updates.¨
Clicking shows:
Package name Current version New version Required action Repository
base 22.7.b 22.1.8 upgrade OPNsense
kernel 22.7.b 22.1.8 upgrade OPNsense
Not paying attention and assuming there was an update I updated and... was back on 13.0/22.1.8.
Luckily I made snapshots (running on Proxmox) and switched back and ( I think :-) ) I am running 13.1/22.7.b now although System Information shows:
OPNsense 22.1.8-amd64
FreeBSD 13.1-RELEASE
OpenSSL 1.1.1o 3 May 2022
-
Same for me, my OPNsense VMs also report being still on 22.1.8, but "freebsd-version -kru" reports 13.1-RELEASE - so I guess the Updates still works
-
Thank you for the fixes in 22.1.8 as well as providing an onramp to beta test 13.1-RELEASE.
What does the upgrade cycle look like if we go to 22.7.b for when 22.7 proper is released? Is that just an opnsense-update jump away to get on the 22.7 series proper once released?
Correct me if I'm wrong but it shouldn't matter as this is just the underlying FreeBSD OS and kernel. Not the Opnsense extensions. For the others that are confused, as Franco said previously, you're going to see an update if you check for updates. If you want to prevent the downgrade to 13.0, you need to lock the base and kernel packages. Worked great for me.
Thank you Franco and team. No issues so far. I was using the pre3 version as well and had zero issues.
-
madj42 is correct. :)
> What does the upgrade cycle look like if we go to 22.7.b for when 22.7 proper is released? Is that just an opnsense-update jump away to get on the 22.7 series proper once released?
22.7 upgrade will force a new kernel install to ensure integrity. You can either keep using 22.7 kernel/base in 22.1 or revert back to 22.1.x versions. Either way in the actual 22.7 upgrade the kernel will be matching the major release version again.
Cheers,
Franco
-
22.1.8_1 + 22.7b kernel+base
All is good so far after a day, and the update was uneventful.
Simplistic setup:
- VLANs on WAN + MAC spoofing with dhcp
- VLANs on LAN + DHCP server
- plugins: IGMP-proxy, uPNP, Sensei
- 4xi225 NICs
- Suricata on WAN
- Zenarmor on LAN
-
Same here, 22.1.8_1 + 22.7b kernel+base and all is OK.
I am also stable since the panics I had earlier, though removing the Atheros wifi card seemed to help with that.
https://forum.opnsense.org/index.php?topic=28422
-
OPNsense 22.1.8_1-amd64
FreeBSD 13.1-RELEASE
OpenSSL 1.1.1o 3 May 2022
Now we wait...
Running on a HP T620 Plus with a dual SFP port Intel i350 card.
AMD GX-420CA SOC with Radeon(tm) HD Graphics (4 cores, 4 threads)
-
OPNsense 22.1.8_1-amd64
FreeBSD 13.1-RELEASE
All good so far
Multi WAN (PPPoE and Starlink)
HE tunnel for IPv6 testing
Both old and new ddclient (still need the old for GoDaddy)
X520-DA2 card and 4x1G intel card
Multiple VLANs
Acme, netflow, mdns, IPsec, OpenVPN
-
All OK here.
native dhcp/6 on WAN, 3 tracking interfaces, no issues.
UDP Broadcast Relay - no issues.
Wireguard - no issues.
ddclient - Google Domains, IPv4 only - No issues.
Green across the board.
Qotom core I5-5250U
4 * Intel NICs
8Gb Mem
-
Everything seems to be good with:
# opnsense-update -bkzr 22.7.b
# opnsense-shell reboot
##Proxmox 7.2
# Intel Corporation I350 Gigabit Network Connection two port passthrough
Port One = WAN
Port Two = Vlan parent (4 vlan in total)
# Intel Corporation 82574L Gigabit Network Connection passthrough
LAN
No parent interface enabled
openVPN to Surfshark
Used this Guide:
https://schnerring.net/blog/opnsense-baseline-guide-with-vpn-guest-and-vlan-support/
Substituted OpenVPN for Wineguard
OPNsense 22.1.8_1-amd64
FreeBSD 13.1-RELEASE
OpenSSL 1.1.1o 3 May 2022
os-api-backup (installed) 1.0_1 2.35KiB OPNsense
os-chrony (installed) 1.5 20.6KiB OPNsense
os-firewall (installed) 1.1 56.4KiB OPNsense
os-qemu-guest-agent (installed) 1.1 19.2KiB OPNsense
os-theme-rebellion (installed) 1.8.8 5.20MiB OPNsense
os-udpbroadcastrelay (installed) 1.0_2 44.8KiB OPNsense
os-wol (installed)
I've been using OPNsense on a Bare Metal box, so will post any problems I encounter with this VM.
-
Works fine on Beelink GK55 mini PC, Intel J4125, 8GB RAM (also works fine replacing with 16GB sodimm), 128GB SSD, built-in dual Realtek NICs, purchased brand new on sale for CAD $215 Amazon.ca :
OPNsense 22.1.8_1-amd64
FreeBSD 13.1-RELEASE
OpenSSL 1.1.1o 3 May 2022
- unbound : all blocklists enabled except WindowsSpyBlocker(Update & Extra)
- Suricata IDS/IPS
- Zenarmour/Sensei : Free Edition
Great many thanks to the Developers ensuring latest most secure OS version !
-
Lynxcat, how did you get Zenarmor running?
-
What do you mean by running, did you perform any usual installation steps ?
-
I get a Phalcon error after initial install, so I was curious how you managed to get it to work?
-
Disregard all previous comments I made here please. Some how got it working...
-
Huh, but it's my thread :D
-
About one time per week I had connectivity loss on the LAN. With the test kernel it seems that is no longer happening. Although it might be a bit early to say that.
-
Yup, spoke too early. Between 7th and 8th day I lose connectivity on LAN.
-
Rather pleased to have found this thread. I needed support for a "Quectel EM12-G" LTE modem that was installed yesterday at the datacenter, but which is only available in FBSD 13.1. Initiated the 22.7.b update, rebooted, and now the PPP interface section of the UI recognizes the modem and lists the usual expected options.
I'll let this bake in for a few more hours and if there are no issues then I'll upgrade the active node (running a 2-node H/A pair, with the passive one on 22.7.b).
Here's the HW Probe link to the machine specs if it's useful for the dev team: https://bsd-hardware.info/?probe=cd8960f886 ; it's a decent enterprise-spec Dell R630 with 4x 1G and 4x 10G Intel based interfaces, though they're being upgraded soon to run 8x 10G (X710 quad-SFP+ rNDC and X710 quad 10G-BASET).
-
I've been getting errors on my i225v ports that have VLANed traffic. I tried updating to see if driver changes fixed it. No change.
-
I've been getting errors on my i225v ports that have VLANed traffic. I tried updating to see if driver changes fixed it. No change.
Did you assign the parent interface?
-
Yes, and I also tried giving it an IP for untagged traffic.
And because of a new issue (WAN interface refused to pull IP from DHCP because it thought the interface was down) I reverted back to the current stable.
Both versions however have the same symptoms; tagged vlans generate errors.
-
Are these errors measurable beyond merely looking at a counter increasing in a monitoring tool?
Cheers,
Franco
-
I tried getting details of errors but all I could find was interface errors in netstat.
Speed test also were unable to reach full WAN speeds. After switching to untagged vlans full speeds were reached.
-
Thanks for clarifying. So situation is the same for 22.1 and 22.7? There isn't a lot of movement in igc driver between 22.1 and 22.7 if that would be any indication of the problem at hand.
Cheers,
Franco
-
Correct. It seems this issue is common.
https://forum.opnsense.org/index.php?topic=28809.msg140202#msg140202
-
Is there anything to be aware of if someone applied this test base/kernel, with 22.1.9 being released? i.e. should you avoid 22.1.9 altogether? Should you upgrade to 22.1.9, then reapply this preview? Should you do something else?
-
If you don't have issues with 22.7.b keep it. If there are issues 22.1.9 is recommended.
I've also updated the 22.7.b to a newer version which matches the fixes included in 22.1.9. In that care a reinstall of the beta is recommened.
# opnsense-update -bkfzr 22.7.b
(note the additional -f to force a reinstall)
Cheers,
Franco
-
I didn't have any issues with 22.1.8_1 but upgraded regardless:
22.1.9 + 22.7b(new) kernel+base
All is good so far after 2 days, and the update was uneventful.
Simplistic setup:
- VLANs on WAN + MAC spoofing with dhcp
- VLANs on LAN + DHCP server
- plugins: IGMP-proxy, uPNP, Sensei
- 4xi225 NICs
- Suricata on WAN
- Zenarmor on LAN
-
If you don't have issues with 22.7.b keep it. If there are issues 22.1.9 is recommended.
I've also updated the 22.7.b to a newer version which matches the fixes included in 22.1.9. In that care a reinstall of the beta is recommened.
# opnsense-update -bkfzr 22.7.b
I did the above and then rebooted. Still running 22.1.8.
After reboot, I have
root 46672 38.7 0.4 48904 35184 - Ss 23:09 12:25.19 /usr/local/bin/python3 /usr/local/opnsense/scripts/netflow/flowd_aggregate.py (python3.8)
Which uses a full CPU at 100%. Even after 12 minutes uptime, it's still up there. Looking at health history, I did not have this issue before reboot.
ast pid: 57394; load averages: 1.20, 1.11, 0.70 up 0+00:12:58 23:21:34
73 processes: 2 running, 70 sleeping, 1 zombie
CPU: 24.9% user, 0.0% nice, 0.0% system, 0.5% interrupt, 74.6% idle
Mem: 272M Active, 699M Inact, 759M Wired, 298M Buf, 6250M Free
Swap: 8192M Total, 8192M Free
PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
46672 root 1 103 0 48M 34M CPU3 3 12:10 99.78% python3.8
84338 root 4 20 0 39M 11M kqread 0 0:00 0.03% syslog-ng
57394 root 1 20 0 14M 3584K CPU2 2 0:00 0.03% top
After 15 mins it calmed down. The process is still there but not using the CPU anymore, only a little peak every now and then. Maybe it's something it does on startup (reloading cache or data, unsure) and I never noticed it ?
In other words, this could totally be normal and unrelated to the upgrade. I suppose it does that after every reboot and I never noticed it but I prefer to report it anyways, just in case.
As for 13.1 (22.7b), it's been rock solid for me since end of May when I installed it.
-
*mark for deletion* excuse me
-
OPNsense 22.7.a_417-amd64
FreeBSD 13.0-STABLE
LibreSSL 3.3.6
- For 12h in production i only miss in OutboundDNS--->Custom Options field.
Other than that , i see only one issue Firewall: Log Files: Plain View -- that the line option breaks the page somehow ( image bellow ).
* Maybe it's suppose to be that way idk, i'am kinda new at firewalling , excuse me and be well.
Hello,
This thread is about the testing of the operating system/base distribution/kernel of FreeBSD 13.1 (with OPNSense 22.7/22.1.x).
Since you are using FreeBSD 13.0 and your issues are not kernel or base system related but UI and OPNSense configuration related, you should post your issue in the general forums or development forums or, and I believe this would be the right place, report a bug or ask for a feature request.
If it's a bug, check this first to see if it has already been reported: https://github.com/opnsense/core/issues
Else, you can open up a new issue.
As for the custom options of unbound, it's been removed some time ago (version 21.7, more than a year ago if I remember well). You can, however, read this which could help you out as it "replaces" the "Custom Options" way of doing it: https://docs.opnsense.org/manual/unbound.html#advanced-configurations
Welcome to the forums !
-
What is the recommended way to upgrade from 22.1.8_1 (on which we installed FreeBSD 13.1) to 22.7-rc1 @franco ? Should we upgrade/downgrade (Upgrade to 22.1.10 and thus downgrading FreeBSD at the same time) and then upgrade to 22.7-rc1 ?
-
installed OPNsense 22.7.r1-amd64 on Proxmox 7.2 latest with q35 and uefi.
Imported my 22.1.10 config
reinstalled Chrony, os-qemu-guest-agent, os-WireGuard, os-theme-cicada and the mimugmail repository then os-adguardhome-maxit.
used scp to copy 22.1.10 /usr/local/AdGuardHome/AdGuardHome.yaml to my mac
used scp to copy AdGuardHome.yaml from my mac to 22.7rc1 /usr/local/AdGuardHome/AdGuardHome.yaml
started adguard from the dashboard
Modifed 22.7rc1 `/etc/rc.conf` by adding
qemu_guest_agent_enable="YES"
qemu_guest_agent_flags="-d -v -l /var/log/qemu-ga.log"
then ran
# service qemu-guest-agent start
So far 22.7rc1 is running well as my primary firewall including wireguard-go (no kmod available that I can tell yet), edit to add: WG-kmod, unbound/adguard and a functioning qemu-guest-agent. I'll report back if I find anything amiss.
EDIT: installed the WG-Kmod so long ago I forgot that it was CLI pkg install with a new OPNsense install. pkg install wireguard-kmod at the CLI followed by a reboot and WG-kmod is working on 22.7rc1
-
An odd thing with 22.7-rc1: in the dashboard, it always says 'Click to view pending updates.' However, if I click on it, it checks the repositories but finds nothing.
-
@RedVortex the quickest way is to update to 22.1.10, REDACTED--SEE BELOW
@dinguz let me try to take a look at that tomorrow
Cheers,
Franco
-
An odd thing with 22.7-rc1: in the dashboard, it always says 'Click to view pending updates.' However, if I click on it, it checks the repositories but finds nothing.
As another data point, that is not the case on my new install. has the expected "Click to check for updates."
-
@RedVortex the quickest way is to update to 22.1.10, REDACTED--SEE BELOW
I did the upgrade to 22.1.10 and then applied the patch. That went well.
However, checking update from the GUI shows this
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 22.1.10 (amd64/OpenSSL) at Wed Jul 13 18:19:47 EDT 2022
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 799 packages processed.
All repositories are up to date.
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking for upgrades (0 candidates): . done
Processing candidates (0 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***
While command line shows an upgrade available
5) Power off system 12) Update from console
6) Reboot system 13) Restore a backup
Enter an option: 12
Fetching change log information, please wait... done
This will automatically fetch all available updates and apply them.
A major firmware upgrade is available for this installation: 22.7.r1
Make sure you have read the release notes and migration guide before
attempting this upgrade. Around 500MB will need to be downloaded and
require 1000MB of free space. Continue with this major upgrade by
typing the major upgrade version number displayed above.
Minor updates may be available, answer 'y' to run them instead.
Proceed with this action? [22.7.r1/y/N]:
I'll do the upgrade through command line and see what happens.
-
Updated both kernel and opnsense, not seeing any issues; smooth upgrade. Will report any issues. Cheers. :)
-
trying to update to 22.7.r1, and get the attached.
Ideas?
-
@lrosenman Meh I forgot about that. My bad.
Edit /usr/local/etc/opnsense-update.conf and replace "%%CORE_ARCH%%" with "amd64". I'll update the patch.
Cheers,
Franco
-
Patch is https://github.com/opnsense/core/commit/83414431d
# opnsense-patch 83414431d
@RedVortex likely same issue, sorry
Cheers,
Franco
-
@dinguz cannot reproduce, can you post output of the following?
# cat /tmp/pkg_upgrade.json
Cheers,
Franco
-
This is it:
root@haanjdj:~ # cat /tmp/pkg_upgrade.json
{
"api_version":"2",
"connection":"ok",
"downgrade_packages":[],
"download_size":"",
"last_check":"Wed Jul 13 21:43:38 CEST 2022",
"needs_reboot":"0",
"new_packages":[],
"os_version":"FreeBSD 13.1-RELEASE",
"product_id":"opnsense-devel",
"product_target":"opnsense-devel",
"product_version":"22.7.r_22",
"reinstall_packages":[],
"remove_packages":[],
"repository":"ok",
"upgrade_major_message":"<p>OPNsense 22.7 \"<em>Not Yet</em>\" has reached i ts end of life. As such it will not receive any more updates, but the upgrade to the new 23.1 series is seamless and can be performed right here from the web GU I.</p> <p> Another method is to import and reinstall using a new installation im age, which will retain your settings using \"Import Configuration\", then reform at the disk and apply a clean system using either \"Install (UFS)\" or \"Install (ZFS)\".</p> <p>You can also upgrade via console / SSH by using option 12 from the menu by typing \"22.7.r1\" when prompted.</p> <p>Make sure to read the migra tion notes and adjust for possible minor breaking changes.</p> <p>Please backup your configuration, preview the new version via live image or in a virtual machi ne. Create snapshots. If all else fails, report back <a href=\"https://forum.opn sense.org/\" target=\"_blank\">in the forums</a> for assistance.</p> ",
"upgrade_major_version":"22.7.r1",
"upgrade_needs_reboot":"0",
"upgrade_packages":[],
"upgrade_sets":[]
}
The only issue I had while upgrading is that the upgrade couldn't find the ZenArmor repository, I have posted some error messages in the appropriate subforum.
-
I have patched it with this patch and via GUI I did upgrade. It gave me warning for multi times rebooting the system but it did smooth upgrade without any problem till now.
-
@dinguz https://github.com/opnsense/core/commit/aaaf842462fa35a
looks like we need to disable the changelog check on the devel version since it only works for real releases (it thinks 22.7.r != 22.7.r1 which is true but not really).
Cheers,
Franco
-
I applied the patch, and after a reboot it works now as expected, thanks!
-
I also saw the errors on a CLI update -- but it seems(!) to be running?
-
Patch is https://github.com/opnsense/core/commit/83414431d
# opnsense-patch 83414431d
@RedVortex likely same issue, sorry
Yeah it was it. But even after patching I couldn't update. I had to completely empty the /usr/local/etc/opnsense-update.conf file first, then patch and then update.
The file was a mess before I cleaned it and only kept the first comment line.
root@DigitalParadise:~ # cat /usr/local/etc/opnsense-update.conf
# configuration for opnsense-update(8), do not edit
UPGRADE_RELEASE="22.7.r1"
UPGRADE_RELEASE="22.7.r1"
UPGRADE_HINT="FreeBSD:13:%%CORE_ARCH%%/22.7"
UPGRADE_RELEASE="22.7.r1"
UPGRADE_HINT="FreeBSD:13:%%CORE_ARCH%%/22.7"
UPGRADE_RELEASE="22.7.r1"
UPGRADE_RELEASE="22.7.r1"
UPGRADE_RELEASE="22.7.r1"
UPGRADE_RELEASE="22.7.r1"
UPGRADE_RELEASE="22.7.r1"
UPGRADE_RELEASE="22.7.r1"
UPGRADE_RELEASE="22.7.r1"
UPGRADE_RELEASE="22.7.r1"
UPGRADE_RELEASE="22.7.r1"
UPGRADE_RELEASE="22.7.r1"
UPGRADE_RELEASE="22.7.r1"
UPGRADE_HINT="FreeBSD:13:%%CORE_ARCH%%/22.7"
UPGRADE_RELEASE="22.7.r1"
UPGRADE_HINT="FreeBSD:13:%%CORE_ARCH%%/22.7"
Thanks for the quick fix.
Now running
OPNsense 22.7.r1_8-amd64
FreeBSD 13.1-RELEASE
OpenSSL 1.1.1q 5 Jul 2022
-
I did want to start fresh so did a complete reinstall from scratch (coming from 21.1.4, no config import), so far everything works flawless, also the upgrade from 22.7.r1 to 22.7.r1_8 from the GUI. I'm using an Atom C3858 with 4x 10Gb (ix) and 8x 1Gb (igb).
I like the (interface) flexibilty of the new VLAN config, but the VLAN device naming is a little weird IMHO. Instead of starting at vlan0X (to vlan 0XX) it would make more sense to match the VLAN device name with the VLAN ID (or do I miss something ?). Looking up the VLAN overview to find my VLAN device with TAG 4 is vlan021 isn't really clear.
edit: Sorry ;-), just read the thread elsewhere about this decision...
I guess the Interface List in Interfaces->Point-to-Point->Devices->Link Interface could use some pimping with some VLAN metadata (ie TAG).
Need to fine tune several bits, but PPPoE (IPv4 & IPv6), DHCP, Unbound, NTP, Suricata, LLDPd, SMART are up and running. I've selected the Intel QAT crypto accelerator in Settings->Misc, but haven't found out if (and where) it's used.
Is it automagicly enabled in services like HAProxy when using crypto ? Need to dive into that but I know from the past (other OS) I had to configure the QAT device directly from the HAProxy config itself. Is this still the case with OPNSense or is the QAT device only used for (IPSec) VPN by default.
Again a great release from the OPNSense team, tnx !!!
-
@RedVortex uh, that was opnsense-patch messing up the config file ;)
@netnut QAT is mostly fire and forget, although it's somewhat hard to verify it's working as it pertains to certain algorithms and eventual service requirements / support
Cheers,
Franco
-
Since the RC2 patch, the Services: FreeRADIUS: Log File is blank/empty. Prior i was getting logs there.
-
I'm not aware of any changes regarding FreeRADIUS. Make sure to check severity filter when you don't get any results the log file might still be logging debug info.
Cheers,
Franco
-
Franco,
I have tried with selecting all logs in freeradius or none or just one at a time.
Maybe related to system: remove support for displaying legacy logs in the GUI in the rel notes from RC2? or this one o system: fix RADIUS config validation for port requirement (contributed by Josh Soref).
Most likely the 1st one in my eyes. The service does work and respond to requests correctly, i dont have any issues. Just no logs.
-
Might be the first then, indicating that Freeradius is not logging syslog but rather handrolling its on text file...
https://github.com/opnsense/core/commit/569afb5af3
# opnsense-patch 569afb5af3
Cheers,
Franco
-
Franco,
Your patch resolved the issue. Prior to patch, I changed the settings from Log to File to Syslog. The syslog only showed warnings in the attached screenshot, no informational or info or anything else.
-
Thanks, we might revert for now to give time to FreeRADIUS plugin to resolve this graecefully.
https://github.com/opnsense/core/issues/5892
Cheers,
Franco
-
Small update: reverted commit in question for final 22.7. Thanks again for the report.
Cheers,
Franco