CARP Config <version>#s are different</version>
-
Greetings,
I have two Netgate XG-2758 firewalls that I have updated to 2.4.1.
Just backed up the config for both of them and compared them side by side and noticed that the <version># is different between the two of them.
My primary is 15.8 and the Secondary is 17.0. For the heck of it, and honestly I don't know why, I checked my pfsense firewall (VPN) and it is also 2.4.1 and its version is 17.3.
Any thoughts as to why they are different.
Thanks
Dino</version>
-
It changed.
Apparently after an upgrade the config <version>does not or didn't change. Honestly, I remember that changing each time after an upgrade/update.
After I changed something under System and then backed up the config did the <version>change.
Any thoughts?
Thanks.
Dino</version></version>
-
Your config version should match what is here:
https://doc.pfsense.org/index.php/Versions_of_pfSense_and_FreeBSD
-
Thanks for replying!
Ok, yeah, this has got to be a bug or something (open to suggestions). The config version did not update after the 2.4.0 upgrade from 2.3.4_1. When my Netgate XG-2758 were updated to 2.4.0 they were at 15.8. My third box is an old Dell server running pfSense community edition and the same situation happened to it.
And
My config version after making system changes is now at 17.3. Per your link, that shouldn't be possible.
-
No. It shouldn't be. Have you been dabbling with -DEVELOPMENT trains or anything on these?
-
Nope. These are production boxes. No WAY I would put DEV on them. They were updated through the GUI and no I didn't go into Update Settings.
Like I said, after upgrading to 2.4.0 then to 2.4.1 the config <version># remained the same (15.8). Only after I made a change in the system settings did the config <version>number change to 17.3.
Something is goofy. I imagine if I DID install the -DEVELOPEMENT version I imagine the config version would have changed to 17.3 right away.</version></version>
-
Something else that I noticed and this might explain why the version didn't change (not why the 2.4.1-RELEASE is showing 17.3).
After the upgrade to 2.4.0 then the update to 2.4.1, I mentioned that the version showed 15.8. I failed to realize that the <password>and <md5-hash>also still existed. After a 'System' settings change (changed the skin to pfsense-dark) the version number changed to 17.3 and <password>and <md5-hash>were replaced in each user to <bcrypt-hash>. <dashboardcolumns>2</dashboardcolumns> and <webguicss>pfSense.css</webguicss> were also added for some reason (they aren't correct).</bcrypt-hash></md5-hash></password></md5-hash></password>
-
There has been a correction to the wiki page.
The correct config file version number for 2.4.1-RELEASE is 17.3.
2.4.0-RELEASE is 17.0.
