Four days ago it was looking on track: https://forum.opnsense.org/index.php?topic=35041.0 [https://forum.opnsense.org/index.php?topic=35041.0] As per the roadmap, https://opnsense.org/about/road-map/ [https://opnsense.org/about/road-map/] it will come soon. The main points to note about this release (See https://forum.opnsense.org/index.php?topic=34948.0 [https://forum.opnsense.org/index.php?topic=34948.0] for everything): o php8.2 updates o allow “.” in DNS search override o extend/modify IPv6 primary address behaviour o rewrote OpenVPN configuration as “Instances” using MVC/API available as a separate configuration o move unbound-blocklists.conf to configuration location Updates to these plugins: o plugins: os-acme-client 3.18[3] o plugins: os-dnscrypt-proxy 1.14[4] o plugins: os-dyndns removed due to unmaintained code base o plugins: os-frr 1.34[5] o plugins: os-telegraf 1.12.8[6] However, there are a lot of known issues and migration considerations: o The Unbound ACL now defaults to accept all traffic and no longer generates automatic entries. This was done to avoid connectivity issues on dynamic address setups – especially with VPN interfaces. If this is undesirable you can set it to default to block instead and add your manual entries to pass. o Dpinger no longer triggers alarms on its own as its mechanism is too simplistic for loss and delay detection as provided by apinger a long time ago. Delay and loss triggers have been fixed and logging was improved. The rc.syshook facility “monitor” still exists but is only provided for compatibility reasons with existing user scripts. o IPsec “tunnel settings” GUI is now deprecated and manual migration to the “connections” GUI is recommended. An appropriate EoL annoucement will be made next year. o The new OpenVPN instances pages and API create an independent set of instances more closely following the upstream documentation of OpenVPN. Legacy client/server settings cannot be managed from the API and are not migrated, but will continue to work independently. o The old DynDNS plugin was removed in favor of the newer MVC/API plugin for ddclient. We are aware of the EoL state of ddclient which was unfortunately announced only one year after we started working on the new plugin. We will try to add upstream fixes that have not been released yet and already offer our own ddclient-less Python backend in the same plugin as an alternative.