You'd be much better off just putting everything on the HDD RAID. The USB flash is more likely to fail, much slower, has no redundancy, and there's no benefit to putting it on the flash rather than the RAID.

There's no mix to add anything to. Make a configuration backup, get a bigger HDD, reinstall and restore the backup. P.S. Anything USB-based is strongly discouraged.

If the pfsense box has a LAN IP address of 192.168.10.1 and has IPSec server running or a OpenVPN server running that does NOT mean the clients that connect to it via VPN should receive an ip address in the 192.168.10/24 space. In our case we give VPN clients an IP address in the 192.168.20.0/24 address space and have NAT rules that just divert traffic and allow communication between the two address spaces. That is why I said "provided you have appropriate NAT rules". Separating out our address spaces allows us to prioritize traffic and apply filtering rules slightly easier.

Yes, I used the 1G nano image. The size mismatch actully occured when i tried to write a 2G image to a 2G USB drive, and Win32diskimager complained so had to use the 1G image instead. No such error with the CF card though, but the size check seems to work so less probable it's a size mismatch. But of course, I can do a test next time I open the case. Other suggestions?

Well, at least it's solved quickly, lol. :D

hello ..im human on earth not betazoid mind-reader from betazed..please help me understand..thankz

Right in front of "CAM status" it logs something like "(ada1:ahcich1:0:0:0)". The CD drive being disconnected is the circumstance with ESX that can make weird things happen. Should connect it, or remove it entirely, to avoid problems.

THANKS !!! ;D

It's fine to leave it to that URL. I updated the release file prep scripts to make sure it gets copied into place correctly (I just manually copied that one before and obviously didn't pay close enough attention to what I was doing).

Try with the: "Memstick Serial" img ;) https://doc.pfsense.org/index.php/Installing_pfSense#LiveCD_vs_Memstick_vs_Memstick_Serial

yeah all the packages configs will stay the same..  No 2.2.2 to 2.2.5 is not a major release, 2.1.x to 2.2.x would be a major update.  Normally they mention if major changes in the release notes.  For example the upcoming 2.3 going to be major changes.  But even then prob no need to uninstall the packages unless its a problematic one..  Make sure you read the release notes on an update, wait a few days and read the forums on other peoples experiences with the update if your concerned and this is critical production system, etc. https://blog.pfsense.org/?cat=53 Upgrade Guidance As always, you can upgrade from any previous version straight to 2.2.5. For those already running any 2.2.x version, this is a low risk upgrade. For those on 2.1.x or earlier versions, there are a number of significant changes which may impact you. Pay close attention to the 2.2 Upgrade Notes for the details.

If it's Squid causing this then yes, it will flush the cache eventually when the daily cronjob hits; however – that's no solution! You need to configure things properly so that this doesn't happen again!

It looks like I spoke too soon - I'm seeing massive IPv6 brokenness to *.pfsense.org again :(

The earlier iteration of updation from the WebGUI failed when the main WAN was down even though the secondary WAN was up. This might be a pointer to modify the image check code on other available WANs if the main one is down. The firewall itself just uses the default gateway to get stuff like updates, so if the default gateway is down then that sort of stuff does not come. You can enable "default gateway switching" if you have a "standard" kind of installation where all the interfaces with gateways are good routes to the internet. Then the firewall itself should be able to failover its general internet access. But usually anyway I would only do an upgrade when I seem to have a good primary WAN. Introducing an upgrade when there is a primary WAN issue feels like an extra risk that is best avoided.