[CALL FOR TESTING] FreeBSD 13.1 / 22.7 operating system preview

[franco]

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

[bugvito]

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

[RedVortex]

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

Code Select Expand

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.

Code Select Expand

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.

[xkpx]

*mark for deletion* excuse me

[RedVortex]

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 !

[RedVortex]

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 ?

[Vesalius]

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.

Code Select Expand

pkg install wireguard-kmod at the CLI followed by a reboot and WG-kmod is working on 22.7rc1

[dinguz]

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.

[franco]

@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

[Vesalius]

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]

@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

Code Select Expand

***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

Code Select Expand

  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.

[gpb]

Updated both kernel and opnsense, not seeing any issues; smooth upgrade.  Will report any issues.  Cheers.  :)

[lrosenman]

trying to update to 22.7.r1, and get the attached.

Ideas?

[franco]

@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

[franco]

Patch is https://github.com/opnsense/core/commit/83414431d

# opnsense-patch 83414431d

@RedVortex likely same issue, sorry


Cheers,
Franco