(I had to open a support ticket to request images for both the SG-3100 and XG-7100 units we have).
The update kept failing with size mismatch.
So I had to re-flash my SG-3100 from a factory 2.4.4-p2 image again, and run the update again. The update worked - but then I seem to have hit some issue with Unable to load dynamic library - I've flashed back to 2.4.4-p2, but it was good to try it and I'm happy to try it again in a few days maybe, if that dynamic library error is fixed. (This is a lab environment).
Yes, the dev branch has moved to 2.5 which is built on FreeBSD 12. So to install packages you will need to either update to a 2.5 using the instructions for coming from 2.4.5 here:
https://www.netgate.com/blog/pfsense-2-5-0-development-snapshots-now-available.html
Or re-install 2.4.4. There is no way to downgrade easily to that from 2.4.5 in place.
@Sessa45 : a solution might be :
Re install the last released version - something like 2.4.4. p1 - and make WAN work.
Do nothing else.
Do not import your config.xml.
Now, upgrade to the bleeding edge : update to the 2.5.0 snapshot.
When all is ok, upgrade, reboot, etc, import your config.xml.
Btw : I wonder : pfSense "2.5.0" snap shotted should work. But you better be sure that all the packages you use are also "2.5.0" ready ...
I’ve got a SG-2220 and tried out the AWS Wizard. I stopped using the AWS wizard and uninstalled it in Package Manager.
When I needed a bit more CPU/Memory i backed up my SG-2220 and imported the config into a VM running pfSense CE. The AWS wizard is not available on CE.
I then wanted to test 2.5 in the pfSense VM but the upgrade failed due to the “aws-sdk” error ...
Unfortunately i cannot provide any logs as I have rolled back the VM to a snapshot taken prior to the upgrade attempt.
I assume that the config file still refers to AWS wizard components.
That wouldn't be related. Since the wizard package isn't available on CE it can't be doing that. It's not clear yet what is, however. We've had some odd quirks with the pkg solver on 12 so far.
If you read the thread linked from the issue above, the aws package didn't appear to be required by anything, which is part of the issue. It decided mid-upgrade that it was necessary for some as-yet-undiscovered reason and failed.
Without the console output or upgrade log from the first post-upgrade reboot it's difficult to say what might have happened in your case.
This thread got out of hand and has been locked. Please refrain from insults.
As far as I know altq is still disabled for ix in 2.5. I don't believe it has been tested though to see if the stability issues it introduced have been resolved in FreeBSD 12. It is something we could look into for 2.5. It's become more of a problem since the 1G interfaces used by C3K are now using the ix driver.
The thread I linked above has instructions on how to fix that. You can put hw.pci.enable_msix=0 into /boot/loader.conf.local before you upgrade, or set it at a loader prompt (set hw.pci.enable_msix=0 then boot) and then place it in /boot/loader.conf.local after it boots successfully.
There were two bugs at play here, both of which should be corrected on current snapshots:
filterlog needed adjusting for 64-bit platforms: https://redmine.pfsense.org/issues/9411
The firewall log parser needed adjusting for a slight change in the syslog format of the process name: https://redmine.pfsense.org/issues/9415
Even though that bug is marked "in progress" it's most likely fixed everywhere.
OK, so that's not too unusual. The transition for 2.4.4->2.5.0 users will be a lot smoother. We wanted to make 2.4.5 users manually opt in because we didn't want someone who was relatively stable on 2.4.5 to click the auto-update to 2.5.0 and break.
I split off individual threads from the 2.5.0 announcement thread, so others can see them easier, which is why this is its own topic now.
