Just means you don't have any IPsec config when it's doing the config upgrade. I added a check to skip that part where you don't have IPsec configured, to prevent the noise in that case in future releases. Doesn't hurt anything.

There's a good chance the HAVP package could have filled /tmp there. That's normally only applied in embedded (Nano) installs where running HAVP is not recomended.
Increase the size of /tmp if that's the case.

Steve

It's your code "hardcoding" it when you select something from dropdown. How's that user-induced?! Users assume the GUI exists for a reason, and have a need to check the settings!

Stupidity illustrated:

Step 0:

$ grep firmwareurl /cf/conf/config.xml                                 <firmwareurl>https://updates.pfsense.org/_updaters/amd64</firmwareurl>

Step 1:

Uncheck, Save, as advised above:

$ grep firmwareurl /cf/conf/config.xml $

Good that we spared one line in config.xml! To make it more helpful, there's nothing useful visible in the GUI either. ::)

Step 2:
Select the (recommended) "Current architecture", watch the "Use an unofficial server for firmware upgrades" getting automagically ticked. Click Save.

$ grep firmwareurl /cf/conf/config.xml                                 <firmwareurl>https://updates.pfsense.org/_updaters/amd64</firmwareurl>

Result:
We are back to Step 0. Wash, rinse, repeat.  >:( >:( >:(

Bonus:
I also see this note there:

NOTE: When a custom URL is configured, the system will not verify the image has an official digital signature

but cannot see that coded anywhere. Sigh.

Tell people what they have set (even by default) in the GUI. Instead of leaving it blank – and leaving the config.xml blank as well.

New option "any" added for peer ID, and config upgrade code added so EAP types have their peer ID changed so it continues to match previous behavior. Rebuilding 2.2.4-RELEASE with that change. You can gitsync RELENG_2_2 now to fix that on your system.

Can you browse this? http://www.msftncsi.com/ncsi.txt What's the output of this? drill dns.msftncsi.com

Otherwise, kindly describe "limited connection".

LAN GW: 10.0.0.254

Should not exist.

Waste of time. Use the latest 2.2.4 snapshots; sync mounts with slow drives -> disaster.

Hey thanks for that, i think i will do a re-image of the card when i get chance, as a temp solution i created the dir and scp'd the font over from another pfsense box. Seems to be working at the moment. But as the directory structure wasnt created initially it looks like i may have a semi broken box so i think i definitely need to rebuild.

64 Bit LiveCD Installer ran fine (2.2.3)

I'll quantify that better, in previous versions of 2.2.x, cant say about earlier versions beyond that.

It was on a 64bit capable device, but one thing from memory that stuck was it was only found less than 512Mb when its 2x4GB, 4GB being the theoretical max for 32bit systems unless something like whats hilighted in the link was occurring, ie falling back to an earlier instruction set on the intel cpu forced by either the cpu or freebsd handling of instructions sets at the OS, which could have explained the memory warning about having less than 512MB.

https://en.wikipedia.org/wiki/RAM_limit#32_bit_addresses.2C_24_address_pins

That is it. Thanks!

Summary: When configuring multi-wan PFSense 2.0 has a hidden rule to route local network connections that overrides the explicit default rule I configured. This hidden rule no longer exists in 2.1 and newer. A lan firewall rule needs to be configured for the local connection to use the default gateways instead of the gateway group.

Yeah - Often using DHCP and just telling pfsense to allocate a certain IP to a certain MAC is easiest.

Its pretty easy to screw up static IP with centos.

The error was clear but  I was pretty sure that the upgrade was from x64 version. 
The reset did the job !

Many thanks,
Adrian