Hi, What hardware are you using? Which install type are you running? (32/64bit, nano/full/embedded, etc) Are you using the default IP address for LAN? Have you tried http and https? Have you made any other changes? Can you still ping the LAN IP address? Steve

You can't transparently redirect HTTPS. You have to explicitly set the proxy in the browser settings or use an auto config URL.

I am stuck in the same spot, but investigating this- I see my available free space as only 907MB, the decompressed image is actually 986M. This is likely where I am getting hung up. I'll either have to find a way to clear some space or do a clean install and restore my config and rebuild packages  :-\

Not running Nano? Looks like a custom install. Steve

Booted from a USB CD drive. Wouldn't boot completely; not sure why, last time I CD booted this system it had a SATA CD drive in it - perhaps some oddball interaction of it being a USB CD. Had tried booting from USB stick, but that wasn't working. Finally got it to boot by letting the CD boot to the point where it gives the various boot options (had been letting it go from there to option 1, and that was not working), and then choosing (3) boot from USB with the USB stick in. That finally let me install, and the system is now booting from hard disk to 2.1.2, just needs reconfiguring and cutting back from the temporary lash-up that's been replacing it.

@razzfazz: You're not trying to boot from one of the USB 3.0 ports, are you? Turns out I was. This did the trick. Thank you!

Check this page for instructions. https://doc.pfsense.org/index.php/System_Patches

@cmb: @oggsct: Update: I was able to get this to install on 2 netgate devices but a third tried to go to the normal 2.1.2 and didn't change, shows that it is 2.1p1 and says there is an update available but the update never applies. Let me know if there is any information or logs I can provide to help, or if I need to break this into its own thread. If you're still having issues, yes, please start your own thread with the info so it's easier to follow up. Upon further digging the 2 that don't work are showing signs of a corrupted partition table. I will be replacing the compact flash cards in them. I don't see a need for a new thread currently. Thank you for your assistance and continued hard work.

Forgot to copy one of the stock files back into place after our debugging last week, sorry about that. All good now.

Reboot the box, stop at the loader prompt, type "show" and look for any em tunables you may have had set, for each of those, run "unset xxxxxx" where xxxxxx is the variable name of the tunable, when they're all unset, boot and see if it works. Odds are that you either had an em tunable in /boot/loader.conf or /boot/loader.conf.local that either had no effect before and is honored now, or that is no longer necessary. If it boots OK, edit those files and remove any em tunables and see if it reboots OK on its own the next time.

@doktornotor: You have yet again rewritten "oh noes it does not work". I did not ask for definition of NAT reflection, but for details about what's exactly set up how and does not work. Also you have any good reason to use NAT + Proxy instead of Pure NAT? I thought my last post was detailed enough. pfsense makes many things easy. I realize there is a lot going on behind the scenes, but it is just a simple drop down menu to enable it. Below is pfsense hint information for NAT Reflection and Pure NAT. **"When enabled, this automatically creates additional NAT redirect rules for access to port forwards on your external IP addresses from within your internal networks. The NAT + proxy mode uses a helper program to send packets to the target of the port forward. It is useful in setups where the interface and/or gateway IP used for communication with the target cannot be accurately determined at the time the rules are loaded. Reflection rules are not created for ranges larger than 500 ports and will not be used for more than 1000 ports total between all port forwards. Only TCP and UDP protocols are supported. The pure NAT mode uses a set of NAT rules to direct packets to the target of the port forward. It has better scalability, but it must be possible to accurately determine the interface and gateway IP used for communication with the target at the time the rules are loaded. There are no inherent limits to the number of ports other than the limits of the protocols. All protocols available for port forwards are supported. Individual rules may be configured to override this system setting on a per-rule basis."**

Reply to myself… just had another failure, this time I checked the log's: On Resolver Log i found: failed to load names from /etc/hosts: Too many open files in system And on System Log lot's of: kernel: pid 65477 (dhcpd), uid 1002 inumber 5975 on /var: filesystem full Googling the first entry i found that thread: https://forum.pfsense.org/index.php?topic=63357.0 So I'll continue over there… ;-)

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