Marked solved because problem is not related to the beta and it is working fine now.

Not yet, we are testing internally. There will be some announcement when we have an RC snap ready for testing.

Steve

Oddly enough I can't reproduce the PHP error but I can see where it would happen (and should happen). I've got a change that should fix it, though:

https://redmine.pfsense.org/issues/13876

index 18bb573b0c..21d1847e09 100644 --- a/src/usr/local/www/diag_backup.php +++ b/src/usr/local/www/diag_backup.php @@ -268,10 +268,12 @@ $section->add($group); $form->add($section); -if (($config['installedpackages']['package'] != "") || (is_subsystem_dirty("packagelock"))) { +$has_installed_packages = !empty(config_get_path('installedpackages/package', [])); + +if ($has_installed_packages || (is_subsystem_dirty("packagelock"))) { $section = new Form_Section('Package Functions'); - if ($config['installedpackages']['package'] != "") { + if ($has_installed_packages) { $group = new Form_Group(''); // Note: ID attribute of each element created is to be unique. Not being used, suppressing it. $group->add(new Form_Button(

@jimp said in DynDNS claims cannot determine WAN IP when WAN is RFC1918:

1e7eb5d1186dbc4c31f49af5e3ce72d9797b48ba

1e7eb5d1186dbc4c31f49af5e3ce72d9797b48ba

Indeed resolves it!

Thanks

We're aware of that, it's something we intend to correct before the release.

@jimp ok thanks for the explanation.
Understood and makes sense, but it is hard to see if there is ram left for eg plug-ins or not.

after doing some testing and switching of nics i no longer believe it is related to the 2.5gbe interface. i ripped a chelsio t520 from a server for a minute and threw it in and it gave me the exact same problem. peeks around 400-450Mbps in speed test running 23.01 and 950-1100Mbps with 22.05. i am sorry i led you down the wrong path. thank you for all your help!

In an ideal world, anything we mark RC could be the release, but as usual we inevitably find things here and there during our more intense RC testing and there that need fixed before the release.

So it's very, very close to release, but there are still a few changes we know are coming before release yet.

@stephenw10 Awesome, thank you. It works!

@gertjan

OK THX

@andrew_241 said in Hyper-V: Upgrade from 22.05 to 23.01.b.20221217.1429 fails to boot:

Is your configuration version at 10.0?

Yep.

Confirmed both the gui and command line updates are now loading the latest snapshot.

Thanks!

Yup, that's not an unreasonable argument IMO.

Thank you @jimp, much appreciated.

I noticed that you also updated Avahi--again thank you.

Based on your model, I've pushed an update to the outstanding PR for NUT to update it for PHP 8.1. Appreciated it if you could take a look to confirm that it is correct. Thanks.

That isn't what it's saying.

/usr/local/share/GeoIP on /var/unbound/usr/local/share/GeoIP (nullfs, local, noatime, read-only, nfsv4acls)

That means /usr/local/share/GeoIP is mounted using nullfs at /var/unbound/usr/local/share/GeoIP

Only the view through /var/unbound/usr/local/share/GeoIP is read only, going directly to /usr/local/share/GeoIP is not read only.

@j-koopmann
There's been some issues with the beta testing.
https://forum.netgate.com/topic/176064/attempting-to-update-to-23-01-devel-corrupts-my-pfsense-installation/84

@stephenw10 Yes, it works as expected.

Ted Quade

How are you trying to update?

You can't visit that page directly without the client side cert.

Steve

@michaellacroix that makes sense since the first error I received said something "like" unavailable, I should have grabbed a screen shot. once I got beyond that I thought continue but now seeing exactly what you reported.