I figured it hadn't a clue but couldn't work out why it was all going to hell. What I've done now is to move the 2nd one (here, it was high up and while you couldn't see it it was in the open - not IN the cupboard ;) ) to a different room, where there is another switch so I could plug it in. SAme details as the other one so I am presuming my devices will swap from one to another depending on signal. The coverage is really just needed to get to the garage which is away from the house. The original point is as far away from that as is physically possible! Just thinking there that the usual 10/100 card that was teir originally would have been fine for the 72Mbps connection. I did replace the PCs in the house onbaord cards (and the pfsense cards) with 1GB just for internal traffic - a lot of file shifting going on. Thanks for the help.

@renegade: Same here. After upgrading there was no connection to the internet although ppp had a public ip address. I have to disconnect and reconnect manually. This problem exists since 2.3.1 and is in most times reproducible after reboot. Already made a clean install and restored config. Using a vigor 130 for German adsl telekom. I confirm the same problem with 2.3.1 and Telecom Italia as provider. My warkround was to disable the 'fake interface' that i created to access the modem. Since than the connection is stable as never before!

Hi Tnx for your Answer  ,  my problem resolved  So Tnx

@EricE: @2chemlud: This whole TRIM thing is a pile of sh*t on i386 BSD… TRIM is an ugly hack, period.  Mainly a symptom of trying to graft old storage technology that works one way on top of flash memory that works an entirely different way.  Hopefully someone will come up with a replacement for SATA and develop a native flash memory stack end to end. Until then I just buy SSDs that are over-provisioned and do their own garbage collection irrespective of TRIM.  Most Sandforce based SSDs work this way - it just takes a bit more digging to find 'em. With regard to  over-provisioned SSD a good article (at least from Kingston) is https://www.kingston.com/en/ssd/overprovisioning Seagate: http://www.seagate.com/gb/en/tech-insights/ssd-over-provisioning-benefits-master-ti/

Gents, Ultimately I reloaded 2.3.3 and once that came up was immediately presented with the opportunity to update to 2.3.3_1 - which I am pleased to say went off without a hitch. I may have a motherboard issue in that I saw numerous indications on the console during the re-installation that most of my USB ports were having issues remaining "attached" to the several thumbdrives I tested. This complication may account for my failed effort to "automatically restore during the installation" but ultimately I was able restore the config file via the GUI. And then there is the suggestion of an I/O issue in the log noted by doktornotor…  :-\ Although underlying hardware issues may remain, I'm pleased that for now at least my system seems to be operating normally.  ;) Thanks for your assistance.  :)

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.