Is there an easy way to downgrade from 22.05 to 22.01?
-
My setup was working fine with my Netgate 1100 running 22.01, all my VOIP clients operated fine, just updated to 22.05 and some clients can't make outbound calls anymore while some can, and they are in the same location (I use pfblockerng 3.1.0_4 to white list countries).
Is there a safe way to downgrade the unit to 22.01 considering I don't have physical access to it right now and if some goes wrong with the downgrade it will brick the unit until someone can get to the location?
-
There is no way to downgrade in place. You'd have to reinstall the software and restore a configuration from before the upgrade.
-
@jimp I haven't reinstalled yet, I did make a backup, do you have guide on how to reinstall, the safest one if possible.
-
-
@paul2019 Did you see the suggestion in your other thread https://forum.netgate.com/topic/174451/just-updated-to-pfsense-22-05-is-it-fully-compatible-with-3-1-0_4 ? Just need to change a ) character to a space.
-
@steveits said in Is there an easy way to downgrade from 22.05 to 22.01?:
@paul2019 Did you see the suggestion in your other thread https://forum.netgate.com/topic/174451/just-updated-to-pfsense-22-05-is-it-fully-compatible-with-3-1-0_4 ? Just need to change a ) character to a space.
Yes, I just applied that patch manually and restarted the unit, still some users can't make outbound calls, I can still call them fine but when they call me it's connecting forever.
-
@paul2019 Tried a couple usb cables and none of them worked, two different computers and nothing gets detected under the device manager -> ports, the driver was installed but if it doesn't detect the cable connected then the usb port must be bad. would be nice to ssh via lan to do that update.
-
I can confirm that we are having the same issue. We don't use pfblockerng though. This seems to be something else related to 22.05.
-
@adamjonfuller said in Is there an easy way to downgrade from 22.05 to 22.01?:
I can confirm that we are having the same issue. We don't use pfblockerng though. This seems to be something else related to 22.05.
This is what fixed it for me: https://docs.netgate.com/pfsense/en/latest/recipes/nat-voip-pbx.html