pfSense 2.4.5 Now Available
-
While keeping your IT infrastructure up to date is a clear best practice, if your device is remote we recommend delaying any upgrades while the travel restrictions around COVID-19 are active.
We are pleased to announce the release of pfSense 2.4.5. This release brings several new features as well as security and bug fixes. To learn more see our release blog.
A huge thank you to the community for all your testing and feedback you have provided!
-
Updated without issue. I had/have NUT and pfblockerng_devel packages installed.
-
Just want to post a link to this- https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide.html
Please read it before updating your firewall(s).
You have been warned!
-
Upgraded from 2.4.4p3 without issue.
Packages:
cron
NUT
pfBLocknerNG
Suricata -
Upgraded two pfSense boxes this afternoon from 2.4.4 P3 with no issues - one was a Supermicro 5018D-F8NT, the other a custom build based on an Intel i3-8100. The latter box actually had an uptime of 243 days - I was halfway tempted to wait until 245 days uptime and upgrade then...
Thanks everyone for all your hard work on this latest release and for making such a fantastically stable product.
-
2.4.4p3 squid com autenticaĆ§Ć£o LDAP estava funcionando corretamente, apĆ³s atualizaĆ§Ć£o para 2.4.5 fica solicitando usuĆ”rio e senha, mesmo utilizando usuĆ”rio e senha corretos. Servidor estava operando normalmente antes da atualizaĆ§Ć£o, configuraĆ§Ć£o estĆ” correta, proxy em uso a muitos anos, sem erros em atualizaƧƵes anteriores. Reinstalado pacote squid mas erro persiste. Tentei usar os mesmos parĆ¢metros de integraĆ§Ć£o ldap do squid em outro proxy, e apresenta o mesmo erro.
-
@IsmaelPA said in pfSense 2.4.5 Now Available:
anteriores
2.4.4p3 squid with LDAP authentication was working properly, after upgrading to 2.4.5 gets requesting user and password, even using correct user and password. Server was operating normally before the update, configuration is correct, proxy in use for many years, no errors in previous updates. Reinstalled squid package but error persists. I tried to use the same ldap integration parameters of squid in another proxy, and it presents the same error.
-
I upgrade six (6) pfsense production server at the same time from 2.4.4_p3, and I had problem with the conectivity. The ping time is very high until 5.000ms.
I tried upgrade with my pfsense server at home from 2.4.4_p3, but in this case I did a snapshot on vmware, and the problem is same. The ping time is very high and the navigation have a lot of problems.
I restored the snapshot, and all return to normally
-
@IsmaelPA this is MS latest update, you can talk to AD only with secure communication protocol like LDAPS
-
Upgraded yesterday. Exactly 37 minutes ago, at start of this hour, both of my VM upgraded to latest version started to consume CPU 35%-40%, connection started to swop from up to down, console not responding, web-console not loading.
Reverted to snapshot before upgrade, both VMs started to work normally. -
@hmh No, this is not the problem... today before the update everyone was browsing normally, the problem occurred after the update. I'm doing exhaustive testing, squid+radius also does not navigate, only worked with local authentication.
-
Hi to all,
i've upgraded my pfsene to 2.4.5 and I running on FTTH connection.
Before upgrade when I try to testing my speed connection the resulst are over 600; now i'm not up to 300.How can I solve this issue?
Thanks
-
We some problems reported by early adapters of 2.4.5 release, do you plan to release hot-fixes soon to people who is still waiting and not updating?
Thx
-
@chudak move to TNSR :-)
-
UEFI does not work
-
-
Version check says 'Unable to check for updates' - message now, maybe new version is coming up?
-
I updated 4 Days 05 Hours 47 Minutes 35 Seconds ago, with the following packages installed with the only issue that I have discovered is I had to click the update graphs in the traffic totals package.
-
Again update is not available ATM
https://imgur.com/a/gw9hQOW
-
Yes it is
You have a dns or connectivity issue most likely
https://docs.netgate.com/pfsense/en/latest/install/upgrade-troubleshooting.html
do a
pkg-static update -fwhat does it say?
