Snapshot update for 23.xx?
-
The actual upgrade process works fine from 2.6 and always has. The outstanding issue is the repo branch setup after upgrade: https://redmine.pfsense.org/issues/14137
But it easy enough to run the workaround there to remove the old branch data.
Steve
-
Does 2.6 support Intel i-225’s and the Realtek 2.5gb NICs loading the Realtek 1.98 driver?
I do not mind going back to 2.6 Its not like a brain transplant. With the 2.5gb NIC’s I’m not sure how far back I can go however.
It’s not like my PFSense router is broken. Works just fine with the CE version. I can wait until even 23.05 is available.
The remove stuff step is after + installs. It won’t install so I can get to that point.
Which means it reads like a two step deal.
Go back to a CE version that’s not using PHP 8.2. Update to + version, 23.01. Then dive into the stored data that needs to be removed.
I’m guessing 23.05 is PHP 8.2 but only guessing.
-
2.6 supports most i225 NICs but it seems not all. We did see some that required 2.7.
The Realtek driver will support the rtl8125 there if you add the pkg.The CE 2.7 snapshot from Feb 15th has php 8.1 and can be upgraded directly to 23.01:
https://snapshots.netgate.com/amd64/pfSense_master/installer/Yes, 23.05 will use php 8.2.
-
@stephenw10 I tried a couple of times before and had to completely restore. I don’t recall if I used the Feb 15th as a try. I have a thumb drive with 2.6 and CONF folder ready to go. Could use 2.7 Feb just as easily.
-
Updated to 23.05.a.20230424.0600, branch 23.05 disappeared from the menu, Latest Stable version 23.01 and Previous Stable Version 22.05.01 are available.
And on that router where it has not yet been updated to "23.05" there is: Latest Development Snapshots 23.05
-
Checking....
-
Yup, OK I see that. Fixing....
-
Ok, that should be fixed now. Let me know if you're still seeing the wrong branches.
-
Yes, now everything is OK, I launched the update to 23.05.a.20230426.1230
-
23.05.a.20230427.0208 - The wireguard service stopped starting
usr/local/pkg/wireguard/includes/wg_service.inc: The command '/usr/local/sbin/filterdns -p /var/run/filterdns-route.pid -i 60 -c /var/etc/filterdns-route.hosts -d 1' returned exit code '1', the output was '/var/etc/filterdns-route.hosts:10: filterdns: duplicate configuration entry found filterdns: cannot open the configuration file.'
-
Yes, it's an issue with the module name. Should be fixed in the next snap.
-
It was not possible to update to 23.05.b.20230427.2246 via the web interface. Updated via console. Wireguard is working. But the branch 23.05 again disappeared from the settings. There are only 23.01 and 22.05.01
-
Hmm, so you didn't see 22.05 beta offered at all?
Do you see the correct branches after upgrading at the CLI?
-
@stephenw10 said in Snapshot update for 23.xx?:
Hmm, so you didn't see 22.05 beta offered at all?
Do you see the correct branches after upgrading at the CLI?
I have seen.. Somehow it was not updated the first time. I went through the update of the web interface, but the version did not change. After updating through the CLI, the version has changed (I now have 23.05.b.20230427.2246), but I stopped seeing the 23.05 branch.
I don’t update the second router yet and it sees the 23.05 branch
login-to-view -
Hmm, can you send me your NDI in chat?
It looks good on all the devices I have here.
-
Ok, that should be fixed (again!).
-
@stephenw10 said in Snapshot update for 23.xx?:
Ok, that should be fixed (again!).
all ok, i see 23.05 branch on 23.05.b.20230427.2246 device.
-
I can not understand. Installed to a friend pfSense 2.6. Registered Plus version. Updated to 23.01. Then I updated it to 23.05b. But it get the "Choose "pfSense Plus Upgrade" to upgrade to pfSense Plus
" message. Very strange. -
Oh, so you were able to upgrade OK to 23.01 _and _ then to 23.05 but are still seeing the update message?
Almost certainly this: https://redmine.pfsense.org/issues/14137So that message is harmless but can be removed by manually running:
rm /usr/local/share/pfSense/pkg/repos/pfSense-repo-custom.*Steve
-
@stephenw10
Thanks a lot. Helped! The most interesting thing is that I got this result twice. Installed 2.6, got a plus key and then updated to 23.01. Then a friend's ssd broke and we got the plus key again and updated everything again. And so in both cases there was such message. Right now everything is ok, thanks!