@robi:

???

http://www.youtube.com/watch?v=ZWP8OUytprE

I think restarting the bowser, emptying cache and pressing Ctrl+F5 were all the options I had, and exhausted them all…

And guess what, after swapping the virtual machines in VMware (the old broken one with the freshly installed one), pressing a simple F5 in the browser, without any forced refresh or cache emptying, brought me to the correct interface. Thus I'm 100% sure it's not the browser's cache mixing it up.

The other oddity with 6to4 is that the apinger gateway monitor thinks it's down:

| Name | Gateway | Monitor | RTT | Loss | Status | Description |
| WAN_6TO4 | 2002:c058:6301:: | 2002:c058:6301:: | 0ms | 100% | Offline
Last check:
Sun, 15 Sep 2013 15:06:14 -0700 | Interface WAN_6TO4 Gateway |

Thanks… that really solved the issue...  ;D 8)

PS - Forgot to say... KEEP ON THE GOOD WORK, pfSense ROCKS!!!  ;D

Just upgraded.
Final reboot and thats it, let the dust begin doing its job on sitting on perfect firewall :)

Thanks to all involved!

It's been fixed and is back up if you haven't noticed already.

Release 2.1 upgrade (i386) was successful. I'm having some minor issues, will post them in an appropriate thread.

Might want to try to limit the HD to less than  1TB and also try to disable multicore and any CPU power saving features in BIOS.  Once installed, just re-enable multicore and C1E.

http://forum.pfsense.org/index.php?topic=61799.0

This is a good start: http://forum.pfsense.org/index.php/topic,64315.0.html
It could be worth making that post a sticky in General Questions or Installations and Upgrades.

You shouldn't have any problems upgrading from 1.2.3 to 2.0.3 but bringing a spare cf card can't hurt.
The config file was updated between those releases. When you update it will be updated accordingly but that means it will no longer be compatible with 1.2.3. So you should make sure you've backed it up in case you have to switch back to the old slice.

Steve

Guys, this weird method worked!

Before touching the live system I made a quick test on the backup hardware by replacing the config file in the /conf directory and rebooted. As expected, interface mismatch happened, but during boot I fixed that with dummy values of that different hardware to let me in.
I noticed that there were package problems, the config file brought the already broken package list from the live system. I compared the initial dummy config file with the one coming from the live system and copied the XML part referring to the packages from there. Brushed it up a little to keep packages's configs - except NTP which was completely changed during the update.
Afterwards, a new reboot, new interface mismatch - but everything else seemed to work fine.

Today I took the live system down, plugged in the newly created card with the patched config file, booted - et voila! It worked! Apart from having to click Save once in the NTP service settings page, everything worked fine! No interface mismatch or any other errors.

Now I have a fully functional, fresh and up-to-date system, and during the process I had virtually no downtime on any of the services offered by the system.

Yes - And thank you for typing thanks  ;D
(If only there were a more simple way right?)

I'm glad its working for you.  The 2.1 official release will be out soon.  Update when its out.

In VirtualBox under the System section for your install, look at the boot order for the storage devices. Try moving Hard Disk to the top.

How did you disable the firewall? It probably stopped NAT working at the same time.
Interesting the lease time helped. Do your clients generally keep the same address across a lease renewal?

Steve

Packages are not and can't be compatible with the LiveCD in a clean/integrated way. You'd be better off with a NanoBSD install with a small SSD/USB. There is little benefit to continued long-term use of the LiveCD these days, even if it is the Memstick version.

I wish I knew enough to install this stuff for a living…    Sounds like fun.  :D
I hope you got paid by the hour?

I don't believe there were any changes to the config file format between 2.0.1 and 2.0.3. Those were only bug fix updates. But backing up the config file takes seconds so do it anyway.

Steve