Here is the "gateways" section: <gateways><gateway_item><interface>opt1</interface> <gateway>192.168.65.254</gateway> <name>AspinwallGW</name> <weight><interval><ipprotocol>inet</ipprotocol></interval></weight></gateway_item> <gateway_item><interface>wan</interface> <gateway>X.159.198.129</gateway> <name>CharterBusiness</name> <weight><interval><descr><ipprotocol>inet</ipprotocol></descr></interval></weight></gateway_item> <gateway_item><interface>wan</interface> <gateway>X.181.155.193</gateway> <name>CharterBusiness_LJG2</name> <weight><interval><descr><ipprotocol>inet</ipprotocol></descr></interval></weight></gateway_item> <gateway_item><interface>lan</interface> <gateway>192.168.50.2</gateway> <name>Untangle_GW</name> <weight>1</weight> <ipprotocol>inet</ipprotocol> <interval></interval></gateway_item> <gateway_item><interface>opt2</interface> <gateway>172.20.1.1</gateway> <name>OPT2GW</name> <weight><ipprotocol>inet</ipprotocol> <interval><defaultgw></defaultgw></interval></weight></gateway_item></gateways> A couple things: My WAN default gateway is X.181.155.193 and named "CharterBusiness_LJG2" That "opt2" interface was just entered as a test and was deleted months ago. I used to see that opt2 interface IP (172.20.1.1) in my logs, but couldn't for the life of me figure out where it was coming from since it wasn't configured in my system anywhere….  now I know.... it's there behind the scenes.

@robi: But the download could go to ramdisk instead… Sure, except that machines running from a 512MB card (Alix boxes) are likely to have 256MB of RAM which is barely enough to keep things running. This will get you going for now.  Long term though you should upgrade to a larger card. https://forum.pfsense.org/index.php?topic=74140.0

I entered again packages tab I saw the package in the list of installed packages I clicked on reinstall It came back

You should probably check your default gateway and dns servers. Those shouldn't be blank!? You should point default gateway to pfSense LAN ip and DNS to the Windows 2008 Server. Also make sure to configure DNS on the Windows 2008 Server so that it knows one or more relays where it can check for addresses it doesn't know itself. This can be either pfSense's DNS forwarder or your ISP's DNS or Google DNS (8.8.8.8). By asking if you can get to internet from pfSense, I meant that can you ping google.com or other address from pfSense GUI or console? I ask this to make sure that it's not pfSense's fault that your client machine can't connect to internet.

ok i think i found the cause of this problem i reinstalled 2.1.2 RELEASE and  configured everything as usual Then i added the NIC tweak - (https://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards) /boot/loader.conf.local kern.ipc.nmbclusters="655356" hw.em.num_queues="4" as we always did- but after adding this line, and rebooting, ill get the exact same error message. any idea why?

thanks you problem solve!. dont know what cause the problem but fresh install fix the problem.

@cmb Thanks, I would like to try that but don't know how. Can you explain ?

The only way that happens is if you have NICs assigned in your config that aren't actually present anymore. Then things can't function until the system knows what NICs it should be using, since what's in your config isn't actually valid (NIC removed from the system generally, on occasion a hardware failure will make a NIC disappear entirely). If you go to Interfaces>assign before the upgrade and verify all your assigned interfaces actually exist, remove or fix any that don't, that won't happen.

doktor's right on there. You're very obviously doing it wrong. I've NEVER had to reinstall a production system short of hardware failure or someone getting in and modifying the source on their own, and I have upwards of 20,000 hours of my life into this over the past decade. Supporting over 1000 companies via portal.pfsense.org.

Thanks Steve…worked.

I've run into a strange issue where my pfSense nanoBSD 2.1 will not upgrade to 2.1.1 or 2.1.2. I have tried using the webGUI and the manual update but each fails at the 48% download/upload. Since I'm running off a 4GB USB drive, I'm simply building another USB using Physdiskwrite with the 2.12 image and will restore my configuration from backup. Will report back with results.

Yes, 9600bps does seem a little outdated these days. I would fully expect that running /var on a flash drive will kill it eventually but I would also expect it to take while on a, say, 2GB stick and they are now very cheap. I guess the issue would be what happens if the drive fails? The script would take care of it on reboot but what would happen before that? A by product of this would also be that logs would be readable after a crash and also easily removed from the box for reading. Personally I don't have an Alix box so it's not an issue for me. There have been a number of upgrade failure reports since 2.1 though where memory exhaustion seemed to be the culprit, this mod could help that. I wouldn't expect it to ever be official though.  ;) Steve

I was a bit disappointed that this 2950 ended up being so loud and hot, but honestly now that I'm running this x750e I staged months ago but never used…I'm starting to realize that it's probably better this way.  Keep pfSense on its own dedicated box rather than in a VM on one of my ESXi hosts alongside other VMs.  Whenever my 860 crashed it took my network and internet connectivity with it. I'll keep the pfSense VM on the 860 as a backup in case the firebox fails.

Thanks Jimp  :) !

This bricked one of my boxes. Insert rude ramblings about previous comments from pfSense team about packages bricking boxes, and finding out this time it's a 'paid for' and marked stable package. Thank you jimp (and pfSense team), for the quick repair instructions, for the one time I didn't download an iso simultaneously, and thank you Google, may you always 'steal' my information, so you may provide me the fastest search result in my time of dis pare. (and yes, I realize this was pushed out 'quickly' because of HeartBleed.., and yes, I apologize for not adding any real value to this conversation) I hope in time this mystical new framework/system the other Jim is talking about resolves issues like this before someone gets bit..

Ok, The newest patch, 2.1.2, seems to fix it.  Same system is now reporting status of captive portal users.  Thanks!

False alarm, it seems my dyndns was acting up and giving out the wrong IP.