<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Upgrading from 1.2.3 or reinstalling from scratch?]]></title><description><![CDATA[<p dir="auto">Yeah, I know, this is beta software <em>(albeit of a very good quality!)</em>, but I've tried upgrading two separate instances of pfSense 1.2.3 to 2.0b5, and both went badly (as in: can't recover, have to start over from scratch); now, I'm not complaining by any means, but my own impression is that there are enough differences between 1.2.3 and 2.0 - particularly on MultiWAN setups - that reinstalling and recreating your config from scratch is probably the better option.</p>
<p dir="auto">Also, in the last year or so of (mostly) lurking on this forum, there were quite a few threads that dealt with issues that turned out to be caused by faulty upgrades, so there seems to be some evidence to confirm the wisdom of doing fresh installs.</p>
<p dir="auto">I'm curious about it, though: what are your experiences upgrading from 1.2.3? I'm especially interested in MultiWAN setups, mostly because most of my installs are of this kind, but any "early adopter" tips &amp; tricks - or pitfalls to avoid - would be appreciated!</p>
<p dir="auto">Regards,</p>
<p dir="auto">Marcello Marques<br />
Sao Paulo - SP - Brazil</p>
]]></description><link>https://forum.netgate.com/topic/30427/upgrading-from-1-2-3-or-reinstalling-from-scratch</link><generator>RSS for Node</generator><lastBuildDate>Sun, 14 Jun 2026 09:38:37 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/30427.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 08 Feb 2011 19:28:17 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Upgrading from 1.2.3 or reinstalling from scratch? on Tue, 08 Feb 2011 21:07:30 GMT]]></title><description><![CDATA[<p dir="auto">I happen to be one of those guys who favors clean installs whenever possible (too many years using Windows, I guess…), so doing that on so important a piece of equipment as a router is no big deal - I was just curious about other user's upgrade stories.</p>
<p dir="auto">As to the config files, yeah, I should've saved those... I'll do that next time, and report back.</p>
<p dir="auto">I remember though that one of those upgrades (a MultiWAN setup on an old Intel 845 mobo, with 512MB RAM and Intel, SiS and Realtek NIC's - yes, I'm <strong>that</strong> brave! :D) ended in a loop assigning interfaces - meaning, the "assign interfaces" console routine kicked up after the upgrade, but no matter how many times I did the (re)assignment, it always cycled back to the same screen; unfortunately, I had some urgency in restoring Internet access, so I just reinstalled on top of the botched upgrade (using version 2.0b5, and manually recreating the configuration) - it's been working flawlessly ever since.</p>
<p dir="auto">Thanks - for the reply, and for giving us pfSense!</p>
<p dir="auto">Marcello</p>
]]></description><link>https://forum.netgate.com/post/264825</link><guid isPermaLink="true">https://forum.netgate.com/post/264825</guid><dc:creator><![CDATA[cellobita]]></dc:creator><pubDate>Tue, 08 Feb 2011 21:07:30 GMT</pubDate></item><item><title><![CDATA[Reply to Upgrading from 1.2.3 or reinstalling from scratch? on Tue, 08 Feb 2011 20:18:10 GMT]]></title><description><![CDATA[<p dir="auto">If you had an upgrade go badly, we need as much info about it as possible so the issues can be fixed. Including, if possible, a copy of your config.xml before and after the upgrade.</p>
<p dir="auto">It should be possible to simply upgrade in place and not worry about it. If something breaks, it should be fixed.</p>
]]></description><link>https://forum.netgate.com/post/264819</link><guid isPermaLink="true">https://forum.netgate.com/post/264819</guid><dc:creator><![CDATA[jimp]]></dc:creator><pubDate>Tue, 08 Feb 2011 20:18:10 GMT</pubDate></item></channel></rss>