Is there any way to downgrade from 2.1 back to 2.0.3
-
Hi all,
I upgraded my firewall to 2.1 a couple of days ago and since then the firewall goes ofline every night. I'm sure there are a lot of nice features in 2.1 but i need my internet and 2.0.3 has been rock solid for me :-)
So, is there any way to revert the upgrade?
-
I had to reinstall 2.0.3 (everynight, pfsense sent dozens of emails showing gateway monitoring had failed although internet kept going) and fortunately, a 2.1 backup worked when restored in 2.0.3, at least for us…
-
Yes - There is a way, I'm pretty sure.
If you download the 2.02 > 2.03 upgrade file and save it on a desktop somewhere and then open your 2.1 web gui and the system > firmware > manual update and point it to the file you saved on your desktop it should downgrade to 2.03.
(This assumes they didn't change from the way its been done in the past. I've downgraded this way a few times in the past)
Update files
http://files.nyi.pfsense.org/mirror/updates/old/Full installs
http://files.nyi.pfsense.org/mirror/downloads/old/ -
Thanks for both suggestions! I'm still trying to decide which of them that seems most likely to give me a working setup in reasonable time.
The firewall just went of line again, this time i managed to get the system log out.
The log is empty for a couple of hours and everything is working just fine then suddenly this in the log and no WAN connection. Not sure if the log entries are a result of WAN dropping or the other way around though.
2013-09-27 14:39 –> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> php: rc.dyndns.update: DynDNS (<public_dns_name_1>) There was an error trying to determine the public IP for interface - wan(ue0). Probably interface is not a WAN interface.
2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt1).
2013-09-27 14:39 --> php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt1).
2013-09-27 14:39 --> php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
2013-09-27 14:39 --> php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
2013-09-27 14:39 --> php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
2013-09-27 14:39 --> php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
2013-09-27 14:39 --> php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
2013-09-27 14:39 --> php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
2013-09-27 14:39 --> php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
2013-09-27 14:39 --> php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan).
2013-09-27 14:39 --> php: rc.filter_configure_sync: ERROR! PPTP enabled but could not resolve the $pptpdtarget
2013-09-27 14:39 --> php: rc.dyndns.update: DynDNS (<public_dns_name_1>) There was an error trying to determine the public IP for interface - wan(ue0). Probably interface is not a WAN interface.
2013-09-27 14:39 --> php: rc.dyndns.update: DynDNS (<public_dns_name_2>) There was an error trying to determine the public IP for interface - wan(ue0). Probably interface is not a WAN interface.
2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> php: rc.dyndns.update: DynDNS (<public_dns_name_2>) There was an error trying to determine the public IP for interface - wan(ue0). Probably interface is not a WAN interface.
2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> check_reload_status: Restarting OpenVPN tunnels/interfaces
2013-09-27 14:39 --> check_reload_status: updating dyndns WWW_Check
2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> check_reload_status: Reloading filter
2013-09-27 14:39 --> check_reload_status: Restarting OpenVPN tunnels/interfaces
2013-09-27 14:39 --> check_reload_status: Restarting ipsec tunnels
2013-09-27 14:39 --> check_reload_status: updating dyndns WAN
2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> php: rc.dyndns.update: DynDNS (<public_dns_name_1>) There was an error trying to determine the public IP for interface - wan(ue0). Probably interface is not a WAN interface.
2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> php: rc.dyndns.update: DynDNS (<public_dns_name_2>) There was an error trying to determine the public IP for interface - wan(ue0). Probably interface is not a WAN interface.
2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> php: rc.interfaces_wan_configure: The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf ue0 > /tmp/ue0_output 2> /tmp/ue0_error_output' returned exit code '1', the output was ''
2013-09-27 14:39 --> php: rc.interfaces_wan_configure: The command '/sbin/ifconfig 'ue0' inet delete' returned exit code '1', the output was 'ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address'
2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> check_reload_status: updating dyndns wan
2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> check_reload_status: Configuring interface wan
2013-09-27 14:39 --> php: rc.newwanip: rc.newwanip: Failed to update wan IP, restarting...
2013-09-27 14:39 --> php: rc.newwanip: rc.newwanip: on (IP address: ) (interface: wan) (real interface: ue0).
2013-09-27 14:39 --> php: rc.newwanip: rc.newwanip: Informational is starting ue0.
2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> php: rc.linkup: Clearing states to old gateway <isp_gateway_ip>.
2013-09-27 14:39 --> php: rc.linkup: ROUTING: setting default route to <isp_gateway_ip>2013-09-27 14:39 --> check_reload_status: rc.newwanip starting ue0
2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> kernel: arpresolve: can't allocate llinfo for <isp_gateway_ip>2013-09-27 14:39 --> php: rc.linkup: The command '/sbin/ifconfig 'ue0' inet delete' returned exit code '1', the output was 'ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address'
2013-09-27 14:39 --> php: rc.linkup: HOTPLUG: Configuring interface wan
2013-09-27 14:39 --> php: rc.linkup: DEVD Ethernet attached event for wan
2013-09-27 14:39 --> php: rc.linkup: DEVD Ethernet detached event for wan
2013-09-27 14:39 --> check_reload_status: Linkup starting ue0
2013-09-27 14:39 --> kernel: ue0: link state changed to UP
2013-09-27 14:39 --> kernel: ue0: link state changed to DOWN
2013-09-27 14:39 --> check_reload_status: Linkup starting ue0</isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></public_dns_name_2></isp_gateway_ip></public_dns_name_1></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></isp_gateway_ip></public_dns_name_2></isp_gateway_ip></public_dns_name_2></public_dns_name_1></isp_gateway_ip></public_dns_name_1></isp_gateway_ip> -
IF you saved your configuration before upgrading, a fresh 2.0.3 install and reload the saved config does not take long at all (when I was first trying pfSense, I ended up doing a LOT of reinstalls until I settled on my disk configuration and which version I was using.)
If you have a spare machine, you can reinstall onto that and then swap machines. But even without that it should be a matter of ~15 minutes at the most.
-
Yes - There is a way, I'm pretty sure.
If you download the 2.02 > 2.03 upgrade file and save it on a desktop somewhere and then open your 2.1 web gui and the system > firmware > manual update and point it to the file you saved on your desktop it should downgrade to 2.03.
I dont think that this will be a good idea ;)
http://forum.pfsense.org/index.php/topic,61159.msg329697.html#msg329697
-
haha - Maybe. You won't know until you have tried. If it doesn't work with 2.1, it will be the first time it hasn't worked. I've done it a number of times before.
I'd say back up the settings and try it. If it fails, THEN do the clean install and restore.
If you want to go straight to clean install and restore, thats always good.
