Here, on twitter, Reddit, etc. I'm sure. I've passed along the info internally, so hopefully we can head off some of the impending tsunami.

Anything in your System log?

General pfSense Questions.

thank you

@kiokoman said in How Can I Mount a Drive when Booting from the Install USB: mount -u / # re-mount root as read/write If it's a ZFS system you may need to run zfs mount -a Does the file system of the install disk permit this?

@johnpoz Thank you sir!

Indeed i've miss-understand vlsm. And it's wright what you ar saying because vlsm works ordering from bigger subnets to smallest subnets. That's why i got the error. Thanks, any way.. I have to check how to reordenate my subnets... thanks in advance...

pfsense Release Date News

@bmeeks Got one 500VA UPS coming tomorrow for the fiber modem, pfSense, switch, and the two UniFi AP's. This will be USB cabled to the pfSense and it's an APC so if nut doesn't work then I will use apcupsd. I have a second UPS also coming, in the range of 1800VA for my NAS, switch, and ESXi boxes. As far as the restore, since I have backups and copy them off the appliance, it was stupid simple. I created the USB key, added the FAT32 "Recover" partition and copied the backup xml file and named it config.xml. I had to hook the firewall up to my TV as I have no VGA monitors in my house surprisingly, but it booted, installed, and on reboot applied config.xml and was up and going. Stupid simple DR in my mind and a huge bonus for pfSense in my book! From now on, it's going to be a DR instead of hours of troubleshooting, its just too damned easy to recover. Going to use a SIIG USB over IP device and a FTDI cable to have remote access to the console for any future needs.

Usually that would indicate that you didn't provide the correct encryption password

@techgeek055 can you tell me how you did it? i face the same problem though i got live ips from the service provider, the ping is working fine. do i need to change the monitor DNS to the google?

Never mind, checking KB below and selecting "Disable hardware checksum offload" option did a trick: https://docs.netgate.com/pfsense/en/latest/interfaces/low-throughput-troubleshooting.html [image: 1571583965907-g.png]

Have not had time to script tests yet. One of the 2 brand new boxes with same hardware and "WOL" disabled froze a couple of days ago as well. The previous box's console was still interactive when issue happened. This one was a full freeze. Not reacting to any inputs.

Thank you!

@jimp Any update now ? I would like to us this feature as Official

Followed the full reset instructions on the linked page, reinstalled squid - back in business. Thanks for the help @stephenw10!