Yes, sort of. They use a link local connection for WAN but will hand you a subnet via PD to use on an internal interface. That works fine. Or it did last time I checked. Steve

My upgrade was getting stuck the same way. The errors pointed to the custom options in unbound. I commented out the option - server:include: /var/unbound/pfb_dnsbl.conf  in DNS resolver. Simply put a # in front of the line and save. To double check I went to line #98 if I remember right at /var/unbound/unbound.conf. Upgrade worked fine with repository update and finished. After completion I removed the # sign in front of the option. Double check the unbound.conf file to make sure comment out is removed. Worked for me. Not sure if others may have similar problem. Mine was for 2.3.3 upgrade on spinning rust.

I thought I'd bring this back up to for the final resolution for this. I tried a 2.4 snapshot and it froze up same as before.  I was never able to find a legacy vs UEFI switch. I turned off a bunch of the hardware in the BIOS and was able to get to the installation process.  Most of what I turned off was serial port related.

I have the same problem with the Intel Centrino Wireless-N 1000 adapter.  Was this problem ever resolved?

Thank you.  I have determined that the YouTube video I was referencing was for an earlier version before what you have advised me was true.  I have now located a more up to date intstall video. Thanks again for the reply, I appreciate taking the time to help me out.  I am very new to pfSense, learning as much as possible in the last 48 hours.  My 2nd NIC card will be here tomorrow so I plan to go live shortly thereafter.

i think i finally found my answer in the etc/ec.initial file.

Should be fine, yes.

@doktornotor: And make sure you are NOT trying to boot from UEFI. Will not work at all with 2.3 Oh, yep just Checked It is UEFI Awesome, Thank you so much! I see the pfSense setup screen! Thank you everyone for looking out!  :D

@jimp: There is no NanoBSD for 2.4. Use a serial memstick and perform a full install. v2.4 will has no NanoBSD?  i have no used serial, it is need what

same problem here .. how can I be sure the proxyuser and proxypass are taken into account (they are store in the xml file), but impossible to check for update. I have no access to the log of the proxy so I cannot investigate on that side.

Thank you very much I will have to attempt that this weekend. Unfortunately I cannot disconnect any network related things during any hours other than typical maintenance window of 2am-6am.

Given those symptoms I'd be more concerned about the hardware than anything. Or the filesystem integrity at least. Unless the disk is full or something cut off the write (e.g. failing disk/media), it wouldn't just stop writing the config partway.

@jahonix: You should download a copy of pfSense here:  https://www.pfsense.org/download/ What you got is a fork which is obviously not supported in here. Oh, I see. I followed the link from the old monowall website, so I landed in the wrong place. Ok, I will reinstall the version you mentioned. Many thanks.

In the GUI, visit System > Update, Update Settings tab, make sure the Stable branch is selected then click Save even if you did not make any changes. Then try it again. If it still fails, make sure the firewall has working DNS and connectivity from the shell (try to ping some Internet sites by name from a shell prompt)

You need to get more public IPv4 from your isp to handle traffic that is not able to be proxied. Or use ipv6..  Or just use the ports with your fqdn.. So tell your users to connect to your gameserver use ftbminecraft.sarentech.com:25565 All of these different names all just point to the single public IP you have if you can not use a reverse proxy that understands the fqdn your sending in the headers then yeah your going to have to tell pfsense to forward traffic based upon the dest port.

Yes, pfSense is a separate machine on the way in to your network. But you can run it as a VM along with other VMs on the same physical hardware, and have pfSense be the real front-end WAN and then talk to the other VMs in the back end (or out another ethernet or VLAN to more backend systems.