pfSense WAN needs to have some IP that is in the "fios router lan" subnet and have the upstream gateway set to the "fios router lan" IP address. Assuming the FIOS router has a DHCP server working, then it will be easy to set the pfSense WAN to DHCP, so it will just ask upstream and the FIOS router will give it an IP address. The DHCP pool on pfSense LAN side must not include the pfSense LAN IP. Make the pool have less range, at the moment you have put the whole subnet. Actually I am surprised that the pfSense DHCP page let you do that. (You don't actually say what you set the pfSense LAN IP to - hopefully you used something different from the Cisco switch)

@jimp: We haven't rolled a formal patch release for those since that would involve a lot more work, but we wanted to get the fixes out there for people to use if they were worried. Thank you for your explanation. For me personally, it’s ok to get smaller updates and minor security fixes just by running pkg from command line. Thanks a lot for the patches. Good to know how this is going on. For those concerned, please just check (my guess this is the issue here): FreeBSD-SA-17:03.ntp https://www.freebsd.org/security/advisories/FreeBSD-SA-17:03.ntp.asc I really appreciate the availability of the patches anyway and the hard work you are doing for pfSense. :)

Confirming this has been a problem for a while. You cannot set a partition size smaller than the disk size. I got around this by installing on an old 64GB SSD, imaging that with clonezilla, and then restoring the 64GB image to a new 128GB SSD, which left 1/2 unallocated. Not the best method for everyone, but it was quick and dirty and workable for me.

Mmm, I'm not sure just how much money can be saved by turning off the VM host. If that's the budget you have to work with though your options are clearly very limited. We might be able to suggest something if we had all the details. Steve

oh ok cool. I do want to setup a vpn server, but I also want to keep any NAT routing off the firewall, so I guess I will port forward through from my public router. Thank you so much for your time and attention, really appreciate the input!!

I don't know.  It's the first time I've used this particular flash drive. I brought it in to work and just let it sit there for about 10 minutes after I pressed Enter to select option 1.  I installed pfSense with no problems.  It boots fine from the SSD now.  I'll play with it at home when I have time. Thanks for your help.

I just updated to 2.3.3 and I'm having an issue with my dashboard in the GUI.  When I have Snort installed, the dashboard yields this message instead of a page: Fatal error: Cannot redeclare widget_snort_uninstall() (previously declared in /usr/local/www/widgets/include/widget-snort.inc:29) in /usr/local/www/widgets/include/.widget-snort.inc.uIzi3Hvkv9Po on line 29 Call Stack: 0.0004 228368 1\. {main}() /usr/local/www/index.php:0 PHP ERROR: Type: 1, File: /usr/local/www/widgets/include/.widget-snort.inc.uIzi3Hvkv9Po, Line: 29, Message: Cannot redeclare widget_snort_uninstall() (previously declared in /usr/local/www/widgets/include/widget-snort.inc:29) I had Snort installed before I applied the update and it's always been fine.  As soon as I applied the update from 2.3.1 to 2.3.3, the dashboard stopped working.  The other GUI pages are ok.  If I remove/uninstall Snort I have no issues.  Based on the message, I'm guessing it's an issue with the configuration of my dashboard widgets.  I'm fairly new to pfSense.  Is there a way to reset my dashboard config and possibly blow away the bits that are causing the issue?  Is there something I can delete in a widgets folder that will blow away the config for the Snort widget so I can (hopefully) clear all related settings?  I'm fine with re-doing my dashboard layout from scratch.  Any clues would be greatly appreciated.

No worries Stephen, thanks for the tip. You should be thankful that you're not on our useless NBN! Matt.

still confused… ;D TRIM yes or no ?!

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.