It really works! Thanks, Phil!

Happens to me to. After upgrade freeradius doesn't start. Trying to kill radiusd process but nothing. After that i try remove package and stay stuck on execution (whatever command) search for freeradius process, not radiusd, trying to kill this stuff (removing the package) i ended with a successful installed, package previously shows as "configured but not (fully) installed" package by killing one of the processes (/usr/local/bin/php -f /etc/rc.packages pfSense-pkg-freeradius2 POST-INSTALL ). Is not a mistake i try remove and the package now appears as installed.

@Derelict: Put 8.8.8.8 on one WAN and 8.8.4.4 on the other. Has fixed it. Thanks.

@PJ2: I also encountered this issue. I was able to resolve this by changing the Search scope - Level: value (Under System => User Manager => Servers => LDAP Server Settings => Edit or Create LDAP server) from "One Level" to "Entire Subtree". Fantastic , thanks - you are my hero. For the record, I removed the Domain Admin group membership from the bind user account. It still works.

You can also do that on-the-fly from a loader prompt without editing: https://doc.pfsense.org/index.php/Boot_Troubleshooting#Booting_with_an_alternate_console

@Technigogo: @jimp: umount -f /cf; fsck -t ufs -y /cf; mount -f -o rw /cf Jimp, is this safe to do over SSH from a LAN computer that I am RDP'd into? (I am not onsite) We have done that exact thing remotely several times with no ill effects, but there is always a chance it could go sideways so I can't say it's completely safe.

Yeah I posted on that topic earlier so will see what they come back with.

Want to report that I too have the same lock up issue, I have 3 Netgate SG-2440.  Also seeing the same issue where interrupts goes really high.  Based on when the devices lock up, I think it's dependent on the total number of packets that has gone through ipsec.  Once it hits some limit, the system becomes unresponsive. All three systems uses ipsec.  Two of the systems uses ipsec a lot and locks up after about a week.  One rarely uses ipsec and has only locked up once.

@johnpoz: I have been running pfsense on esxi for long time..  Yes if your bridge mode depending on your isp you should get dhcp.  I get dhcp via my cable connection. Just validate per the mac of the vnic in esxi that your connected to the right ones in pfsense. Thank you so much. i'll test it and get back to you.

the patch from https://redmine.pfsense.org/issues/6149 worked for me, but only after changing the uppercase HTTP_PROXY to lowercase http_proxy

it provides you a way to setup the vlans before you get to the gui.. and during setup.  It provides no "extra" features if that is what your asking. Say the way your network is setup you would need vlan to be able to get to pfsense, would be bad if you could not set them up until you could get to the gui, since you need vlan info to get to the gui, etc.

A better forum would be "Traffic Shaping" than "Installation and Upgrades".

Hmm, that is strange indeed.  Well, that one is above my pay grade.  Up to the devs now…

Just upgraded from version 2.1 to 2.3, somehow if I enable proxy, all the traffic will be directed to https, all my users cannot access a lot of the websites, and my users also could access ftp site eventhough I have opened the port on firewall on LAN port, otherwise all works fine.

Good lord the time I've wasted on this. I rebooted the jail and it started responding so I rebooted the server and everything is working now. Sorry for the stupid post, it was PEBCAK.

Your destination would normally be your WAN IP..  Since to be honest that is the ONLY IP it could ever be dest for.

As said on the other thread, I'd like to know if you had the chance to solve.