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

[franco]

@dinguz cannot reproduce, can you post output of the following?

# cat /tmp/pkg_upgrade.json


Cheers,
Franco

[dinguz]

This is it:

Code: [Select]

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.

[hamadabsi]

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.

[franco]

@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

[dinguz]

I applied the patch, and after a reboot it works now as expected, thanks!

[lrosenman]

I also saw the errors on a CLI update -- but it seems(!) to be running?

[RedVortex]

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.

Code: [Select]

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

Code: [Select]

OPNsense 22.7.r1_8-amd64
FreeBSD 13.1-RELEASE
OpenSSL 1.1.1q 5 Jul 2022

[netnut]

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

[franco]

@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

[danderson]

Since the RC2 patch, the Services: FreeRADIUS: Log File is blank/empty. Prior i was getting logs there.

[franco]

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

[danderson]

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.

[franco]

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

[danderson]

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.

[franco]

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