Hello: @ffuentes, You stated "My squid issue comes from before and I think is a config issue in my case...", a squid config issue or a pfSense config issue? Fist and foremost any kind of config issue would drive me insane! I would hunt it down and fix whatever was wrong. If that meant starting fresh until it worked (correctly) then that's what I would do (and have done in the past). Total PITA, but, I then know I don't have to play that "well maybe because I did/didn't do something and now that might be what's causing this new problem." SO FRUSTRATING!!!! Problem with this approach is obviously time (and money). Either way, you might want to consider fixing the issue so as to avoid a future headache. I'm guessing this unit is a unit in production so fixing may require doing it when the impact is at a minimal. Always hated that, but no greater joy than knowing the config is perfect and possible future headaches will be avoided (well at least that's how I felt). As stated previously, I don't use squid (not that I haven't experimented with it in the past and decided it wasn't necessary for my needs). My setup is very vanilla with a dash of a few VLANs thrown in. My conversion to 2.4.5 was easy peasy! No problems, less than 5 minutes total. But then again, I'm not utilizing pfSense to it's full potential. I just hope whatever issue(s) it is, it's found quickly and COMPLETELY resolves the problem for everyone. Feel so sorry for anyone going through this as pfSense is an awesome product!

The easy and fastest way is to clean reinstall 2.4.5 and then restore your Backup. https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.html -Rico

Which version of pfSense are you running? Did you try another Browser/Incognito window? -Rico

What hardware you use and do you have something unusual in system log? Status/System Logs/System/General ?

Thank you Johnpoz, I double check the server mode, and it was peer to peer. I changed it to Remote Access and the Advance Client Settings is back. !!!! You're the best. Cheer !!!

I'm sorry you had a bad experience with that upgrade. I'm glad you were able to resolve it though. Rebooting before upgrading is in our upgrade guide. We do try to link to that as much as possible. https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide.html#pre-upgrade-reboot Steve

I updated from the console just to be safe and I too got a PHP crash report. It cannot find files needed in /usr/local/lib/php/20170718/ PHP_errors.log.txt

@provels Thanks for that. This happens even if I uninstall pfblocker, just to a lessor degree. I would expect that, less rules and no enormous aliases. Still see latency and packet loss when the firewall rules are reloaded. I did make that code change, btw.

You can't edit an ISO image but you can edit the memstick image once it's written to the drive if you need to. It's UFS so you need something that can read/write that, like FreeBSD. So it's one of these?: https://www.pcmag.com/reviews/infocus-kangaroo-mobile-desktop Steve

@chudak This thread solves pfB-devel issues with 2.4.5. https://forum.netgate.com/post/900063

That's completely separate the the dhcp client that runs on WAN. There should be no interaction between them. Unless your network wiring is badly wrong! Steve

Thank you

Restored from config.xml off the /cf/conf box, restored and up and running in a few minutes. Notwto put the filebeat back on :) Thank you again!

@stephenw10 Thanks for pointing that one out to me , I flushed the error, system is up and running.

The downloaded lists may not be. Those options are to retain the package config in the main config file. If you restored the config those lists would be re-downloaded anyway. Steve

Like it says on the ACB configuration page, it is derived from the generated ssh key. The ssh key is generated uniquely for every installation. Probably uncheck ssh, rm /etc/ssh/*.key /etc/ssh/*.pub then re-enable ssh. A new key should be generated. Or just disable ssh and remove those files and use that as your snapshot. Then a new key will be generated when/if ssh is enabled. I didn't test any of this but that is the kind of thing I would expect to work for you.

What have you tried? What happened? What did you expect to happen? Anything logged etc? More info needed! Steve