Upgrade to 2.3
-
I wanted actually to upgrade to 2.2.6 and the auto update went to 2.3. I was trying to get pfsync to work between firewalls. Is there a way to go back to Version 2.2.6 from 2.3?
FW01 - 2.2.6
FW02 - Was on a earlier version of 2.2.6. I wanted to update FW02 to the same version as FW01 2.2.6 but accidentally went to 2.3. Is there a way to put this to version on FW02 to 2.2.6?
Thanks
-
wouldn't it better to just update the other one to 2.3 so your current?
-
Not that easy. I have multiple firewalls. Would like to go to this version.
-
Though I agree it would be easier! Any help is appreciated.
-
Well download 2.2.6 version do a clean install, and then restore your config.
-
I am remote. Will this change the ip access to it?
-
Also where can I download the older version?
-
just go to one of the mirrors and the old folder
-
Great can I do this remotely? Or will I not be able to get into the firewall after wiping it?
-
Also how do I know which release I have. ? I know 2.2.6 and I am 64 bit but thats it.
-
there is only 1 2.2.6 release.. not sure how you thought they were on different releases.. And yeah clean install is going to be clean, so yeah your most likely going to loose access to it.. You would need to make sure you have out of band access if your going to do it remotely.
-
Ok so I can just do the install. Actually going back to 2.2.4. Where do I flash it from from the GUI or install it?
-
Which one do I install?
pfSense-2.2.4-RELEASE-1g-amd64-nanobsd-vga.img.gz 26-Jul-2015 23:01 180172771
pfSense-2.2.4-RELEASE-1g-amd64-nanobsd-vga.img…> 26-Jul-2015 23:01 91
pfSense-2.2.4-RELEASE-1g-amd64-nanobsd-vga.img...> 26-Jul-2015 23:01 126
pfSense-2.2.4-RELEASE-1g-amd64-nanobsd.img.gz 26-Jul-2015 23:01 180017156
pfSense-2.2.4-RELEASE-1g-amd64-nanobsd.img.gz.md5 26-Jul-2015 23:01 87
pfSense-2.2.4-RELEASE-1g-amd64-nanobsd.img.gz.s..> 26-Jul-2015 23:01 122
pfSense-2.2.4-RELEASE-1g-i386-nanobsd-vga.img.gz 26-Jul-2015 23:01 169826170
pfSense-2.2.4-RELEASE-1g-i386-nanobsd-vga.img.g..> 26-Jul-2015 23:01 90
pfSense-2.2.4-RELEASE-1g-i386-nanobsd-vga.img.g..> 26-Jul-2015 23:01 125
pfSense-2.2.4-RELEASE-1g-i386-nanobsd.img.gz 26-Jul-2015 23:01 169645939
pfSense-2.2.4-RELEASE-1g-i386-nanobsd.img.gz.md5 26-Jul-2015 23:01 86
pfSense-2.2.4-RELEASE-1g-i386-nanobsd.img.gz.sh..> 26-Jul-2015 23:01 121
pfSense-2.2.4-RELEASE-2g-amd64-nanobsd-vga.img.gz 26-Jul-2015 23:01 181811034
pfSense-2.2.4-RELEASE-2g-amd64-nanobsd-vga.img...> 26-Jul-2015 23:01 91
pfSense-2.2.4-RELEASE-2g-amd64-nanobsd-vga.img...> 26-Jul-2015 23:01 126
pfSense-2.2.4-RELEASE-2g-amd64-nanobsd.img.gz 26-Jul-2015 23:01 181805650
pfSense-2.2.4-RELEASE-2g-amd64-nanobsd.img.gz.md5 26-Jul-2015 23:01 87
pfSense-2.2.4-RELEASE-2g-amd64-nanobsd.img.gz.s..> 26-Jul-2015 23:01 122
pfSense-2.2.4-RELEASE-2g-i386-nanobsd-vga.img.gz 26-Jul-2015 23:01 171511997
pfSense-2.2.4-RELEASE-2g-i386-nanobsd-vga.img.g..> 26-Jul-2015 23:01 90
pfSense-2.2.4-RELEASE-2g-i386-nanobsd-vga.img.g..> 26-Jul-2015 23:01 125
pfSense-2.2.4-RELEASE-2g-i386-nanobsd.img.gz 26-Jul-2015 23:01 171395141
pfSense-2.2.4-RELEASE-2g-i386-nanobsd.img.gz.md5 26-Jul-2015 23:01 86
pfSense-2.2.4-RELEASE-2g-i386-nanobsd.img.gz.sh..> 26-Jul-2015 23:01 121
pfSense-2.2.4-RELEASE-4g-amd64-nanobsd-vga.img.gz 26-Jul-2015 23:01 185333625
pfSense-2.2.4-RELEASE-4g-amd64-nanobsd-vga.img...> 26-Jul-2015 23:01 91
pfSense-2.2.4-RELEASE-4g-amd64-nanobsd-vga.img...> 26-Jul-2015 23:01 126
pfSense-2.2.4-RELEASE-4g-amd64-nanobsd.img.gz 26-Jul-2015 23:01 185326799
pfSense-2.2.4-RELEASE-4g-amd64-nanobsd.img.gz.md5 26-Jul-2015 23:01 87
pfSense-2.2.4-RELEASE-4g-amd64-nanobsd.img.gz.s..> 26-Jul-2015 23:01 122
pfSense-2.2.4-RELEASE-4g-i386-nanobsd-vga.img.gz 26-Jul-2015 23:01 175084817
pfSense-2.2.4-RELEASE-4g-i386-nanobsd-vga.img.g..> 26-Jul-2015 23:01 90
pfSense-2.2.4-RELEASE-4g-i386-nanobsd-vga.img.g..> 26-Jul-2015 23:01 125
pfSense-2.2.4-RELEASE-4g-i386-nanobsd.img.gz 26-Jul-2015 23:01 174949116
pfSense-2.2.4-RELEASE-4g-i386-nanobsd.img.gz.md5 26-Jul-2015 23:01 86
pfSense-2.2.4-RELEASE-4g-i386-nanobsd.img.gz.sh..> 26-Jul-2015 23:01 121 -
How do I do the install?
-
You cannot downgrade in place. You have to completely reinstall + restore a backup from before the upgrade.
That won't be possible remotely unless you have OOB access like DRAC or other IPMI type console that allows you to mount media and use the console remotely.
-
After one week of usage of version 2.3 , im not only disappointed but also irritated .
The new BUI has an hell of bugs(rules not showing up correctly , must scroll to se it , ) from floating rules that change order and everything gets ruined , QOS without layer 7 that is totally useless (oh yes probably not if you have time to waste on p2p rules and filter IP's…) . I'm using l7 from quite some time and did not have the issues reported ....
Packages like bind9 that are not existing in 2.3 and so on .
Next week shutdown and get back to 2.2.x ...
-
If you do decide to downgrade that member make sure you use a backup from the previous version and not 2.3. I am pretty sure you can't use a 2.3 config on previous 2.2 and 2.1 versions.
-
If you do decide to downgrade that member make sure you use a backup from the previous version and not 2.3. I am pretty sure you can't use a 2.3 config on previous 2.2 and 2.1 versions.
I have a full backup and an config backup from the previous version . I allways make backups before any update . The ideea behind 2.3 is ok but my opinion is that it was a to early relase and it's unstable and has a big lack of features and packages that existed before 2.3.
