Ideally, if something can't get working within some reasonable timeout, it should fail with a clear message.

Removed the patch, upgraded to 2.2.6, did the patch again (with the updated url for 2.2.6) and everything still works.

@bluepr0: Interesting! It will be helpful for a newbie like me. Thanks a lot for sharing! I hope that helps beginners friends :)

Hi, I created the wan on pfsense, thanks to the guide linked by roby. It works fine, but unfortunately I can't go beyond 20 mbps (i have 100 mbps connection) the CPU load does not exceed 25% while with the "bastion host" configuration I could use it all  :( PS:  PC Engines ALIX 2D3

Oh well… I did not find the root cause of it, but I backed up my settings, factory defaults, restore settings, and now its read-only after boot. Go figure... :o

Ok apparently my USB stick had an issue. I tried with a different one and now it's booting. Will try to restore now…

Usual cause of that is not having enough available disk space to complete the upgrade successfully.

Hi, pfSense-memstick-serial-2.2.6-RELEASE-amd64.img.gz.md5 appears to be fixed… However, pfSense-memstick-serial-2.2.6-RELEASE-amd64.img.gz.sha256 appears to be still incorrect. The "-RELEASE-amd64" appears to be missing from the filename inside the SHA256 file... -Simon

@ryanjaeb: I'm also seeing this error.  I'm using: http://files.nyi.pfsense.org/mirror/downloads/pfSense-memstick-serial-2.2.6-RELEASE-amd64.img.gz The size of the download doesn't look right to me.  It's ~2MB smaller than the 2.2.5 release.  All the other downloads are slightly bigger than the 2.2.5 releases. The 2.2.5 image worked for me without doing anything different.  Could the 2.2.6 image be broken? This one was a legitimate problem. We regenerated that image and uploaded a fresh copy after re-testing it.

@ctirado: Same here on a home built Atom based system with 4 Gigs of RAM and 128 Gig SSD (the (in)famous? http://www.newegg.com/Product/Product.aspx?Item=N82E16856205007.) Worked like a charm. Carlos Sweet and very sweet price this is. yap.

…I have a remote nano i386 box that did not come back after updating to 2.2.6, apparently the PPPoE did not succeed after reboot. Only the nighly dis-/reconnect of the PPPoE brought the box back. Much relief, as the box is 1000 km away at the moment....

I contacted support and they sent me a very general e-mail, and it was enough to walk me through the process. In case anyone else experiences this issue and needs some additional details, here are the instructions: Since you had packages, after you did factory reset packages settings remained, so that might be the reason you had issues. Let's just do a clean installation. Here's how to connect via console https://portal.pfsense.org/docs/manuals/reference/sg-series-serial-console.html Since you're using OS X, all you need is the command like this: screen /dev/cu.SLAB_USBtoUART 115200 (try it first, before installing drivers, if it doesn't work then install drivers from the link above). To reinstall pfSense, simply login to portal.pfsense.org and under USB Memstick Installer download the latest 2.2.5 ADI Netgate image. After you download the image, flash it to USB. Here's the guide on how to flash image to USB from OS X. https://doc.pfsense.org/index.php/Writing_Disk_Images#Writing_Images_in_Mac_OS_X (click expand). After that plug in the USB to your 2220, connect console cable and power cycle the unit. USB will boot first into setup wizard. From there, select Quick / Easy setup and follow the wizard. After that installation will be complete.

Also it's a good idea to fill in the empty "MAC Address" field of each interface while still running on the old hardware, with the MAC addresses of the original interfaces. When restoring config on the new hardware, the old MAC addresses will be kept and devices on your network will not realize that the gateway has been changed (Windows particularly, if detects MAC address change on the default gateway, prompts the users with a selection dialog, and defaults to "Public network" which can break certain functionality in some cases).

That should all be preserved across an upgrade, specially the simplest upgrade from 2.2.5 to 2.2.6. Did you backup the whole config? (I guess yes, if you just backed up 1 section then a lot more would be missing) Don't know - it should "just work". Really need to know exactly the config and sequence of the upgrade. Then maybe it could be reproduced and then the bug found. The settings are all in the config.xml - you should be able to search in there and find your username and password…

Bah, it was removed in 2.2.3: https://redmine.pfsense.org/projects/pfsense/repository/revisions/4d474c094f7e3efb76d7d0ef02031d8c34433756

FYI, still not working on (fresh upgrade) to 2.2.6. Thoughts? Thanks!

Thanks orsomannaro I was able to execute those commands via Diagnostics -> Command Prompt  and got it working again.

I downloaded the upgrade images and did manual upgrade. That is because I have crap internet and it is quite likely that the auto-upgrade will drop out while downloading due to that. For me a download manager can work away at getting the image, then I can use it to do manual upgrade knowing that I have it all locally. It does take time to write the image to the other slice - it seems to depend on the state (age) of the CF card.

Thanks. That did it. Everything working.