Most packages leave their settings in the config file. That way you can uninstall them and then reinstall to clean up an issue with the installation and not have to input the settings again. That can work both ways - sometimes you really want to clean out all settings and get a really fresh start at setting things up! So yes, it would be nice if package uninstall had an option to also remove all settings.

30GB will do the job, thanks all :)

I put my cable and dsl modems on blank, untagged vlans with my WAN ports.  That might enable you to go back to the realtek and hard-set the switchport to 100-Full to the cable modem. (Security issues aside (I'd rather have a dedicated outside switch), I do it so I can put a sniffer on the outside on a mirror port.)

Short answer: edit your /etc/inc/globals.inc, change the xmlrpcbaseurl from https to http. "xmlrpcbaseurl" => "http://packages.pfsense.org/", Long answer: In order to retrieve package updates for pfsense from behind an upstream web proxy, you may need to change the base URL used by the package manager.  The pfsense updater and the package manager work differently, so system updates may work fine. Your upstream proxy probably doesn't support the mechanism that the package manager's XML_RPC client is trying to use. The package manager connects to your upstream web proxy and says something like: POST https://packages.pfsense.org:443/xmlrpc.php HTTP/1.0 User-Agent: PEAR XML_RPC Host: packages.pfsense.org Content-Type: text/xml ... Most clients would usually start their request out like this: CONNECT https://packages.pfsense.org:443/xmlrpc.php HTTP/1.0 ... Many proxies choke on the type of request that the XML_RPC client uses, but disabling the HTTPS gets around it.  The xmlrpc_client checks the URL from globals.inc, and changes it from port 443/SSL to 80 in its xmlrpc_client.inc logic.

Enjoy (-;

Waiting for NTP to timeout used to be an issue if there was no WAN. I thought it had been resolved but perhaps you have a niche case. Steve

Hi. I have similar issue. Do you success to solve? Thanks

As Jon said above if you leave outbound NAT set to automatic the rules will be added automatically when you assign a new interface or change the assignments. Steve

@gonzopancho: I'm actually looking at using ZFS to do this, rather than the 2 slice nano setup. ZFS let's one keep multiple copies, and provides transparent compression on/off the SD card. First I have to prove (internally) that it is as reliable. @gonzopancho: As above, I'm investigating running ZFS as a first step to moving on from the nanobsd past and its restrictions. If it pans out, then likely that a "3.0" version of the pfSense software will run something a lot like 'freebsd-update', rather than the BWOS-like releases of today, and likely also something a bit more modern for a configuration system and GUI than the large mass of PHP that defines the product now.  This should help us address some of the security shortcomings in the current codebase. NO decision has been taken (yet), it's just time to re-think the direction. +1 for ZFS

It is the Delete key that is used to enter the BIOS. However, several of the F keys do work once in the BIOS, like F10 to save and exit. I didn't have any problems using Putty 0.63. One point that might be worth mentioning aout these boxes, is that the front panel lists the rightmost port as 0 Internal and the port to its left is labelled 1 External. However, when setting up Pfsense for the first time, the rightmost port ( 0 Internal ) is msk3 and the port to its left ( 1 external ) is msk 2. I found this out after setting up msk0 and msk1 and thinking they were the ports labelled 0 and 1 on the front panel. I couldn't understand why my pings were failing! All sorted after a cuppa  :)

Removed a couple links here, one that was not something to write out in the way instructed, one that won't exist much longer in that location. If you need to re-flash any hardware you purchase from us, please get in touch with us via your bundled support and we'll be able to point you to the correct image.

You have reinstalled the packages after the upgrade? Sometimes removing them and reinstalling them solves issues that merely reinstalling them (without removing them) does not.

You could disable one of those by editing the config file directly and then reloading it. Be aware that getting it wrong or typo'ing something can result in the box not booting or some other unwanted effect! Steve

@priller: What is your Internet?  Cable modem?  Is pfSense pulling a WAN IP address? If CM, you need to power cycle it if you change the attached device and the MAC address is different. Yeah I'm an idiot and didn't even think about the fact that the WAN needed to get a new public ip from my ISP. I gave it no time to do that and I'll try power cycling it when I get home. Thanks

I'll give it a try. Thanks!

There was a great post about that in 2008: https://forum.pfsense.org/index.php?topic=8273 It's a pity it haven't got enough attention.

Yes, modern SSDs shouldn't be a cause for concern. Though you can still use that /tmp and /var option if you want to be extra kind to the disk.

@stephenw10: This should work pretty much 'out of the box'. Try swapping the WAN and LAN NIC assignments or using the on-board Gigabit NIC for LAN. When you use DHCP is the client receiving an address? Steve The machine in question is now in service with IPFire, so I can't test at this time.  However, I tried pfSense on another PC, configured like the first one, and I had no problems accessing the web interface.  At least I'm able to evaluate pfSense now, but there seems to be some hardware compatibility issue with the first system.  If/when it gets pulled from service, I'll give it another try with your suggestion (using onboard Gb for LAN). Thanks!