pfSense Community Edition (CE) 2.5.0 and pfSense Plus 21.02 now available!

defunct78

Just tried to upgrade a SG-1100. During the download/install process before the first reboot, I got a failure on certificate verification.

[87/200] Fetching libgpg-error-1.41.txz: .......... done
[88/200] Fetching libgcrypt-1.8.7.txz: .......... done
[89/200] Fetching libffi-3.3_1.txz: ..... done
[90/200] Fetching libevent-2.1.12.txz: .......... done
[91/200] Fetching libedit-3.1.20191231,1.txz: .......... done
[92/200] Fetching libdnet-1.13_3.txz: ......... done
[93/200] Fetching libdaemon-0.14_1.txz: .... done
1082884096:error:141F0006:SSL routines:tls_construct_cert_verify:EVP lib:/usr/local/poudriere/jails/pfSense_plus-v21_02_aarch64/usr/src/crypto/openssl/ssl/statem/statem_lib.c:283:
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/CN=repo00.netgate.com
1082884096:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/local/poudriere/jails/pfSense_plus-v21_02_aarch64/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915:
Child process pid=29228 terminated abnormally: Segmentation fault
Failed

brians

Forgot to mention that since upgrade my SG-2220 seems faster now and can get 900+Mbps on Speedtest.net where before was around 600-700Mbps. ipSEC still seems around 400Mbps, not as fast as 5100 but still good for an older box... just wish it had one more OPT port.

alain.leinbach

Please advise how I may return my SG-1100 to the previous version, prior to 21.02.

This new 21.02 is apparently dangerously unstable. My specific symptoms have been manageable so far as they are limited to incorrect and missing display information on the admin portal, but based on these forums, I fear that I may experience serious problems in the future if I stay on 21.02. Thank you in advance for your response.

SteveITS

@alain-leinbach said in pfSense Community Edition (CE) 2.5.0 and pfSense Plus 21.02 now available!:

advise how I may return my SG-1100 to the previous version, prior to 21.02

Open a ticket at https://go.netgate.com/ to request Netgate firmware.

defunct78

@defunct78 I attempted again, and was able to successfully upgrade. Though it looks like I am now having problems with the unbound service not starting. No logs either, which makes it hard to troubleshoot (resolver.log empty). I was able to switch over DNS Fowarder as suggested in here,

https://www.reddit.com/r/PFSENSE/comments/lo9ag5/since_upgrading_to_25_dns_resolver_unbound_keeps/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

add have restored services.

gpfsenser

@defunct78 I had the same error exactly.....

FileCity

Smooth upgrade as always. Running for more than 24 hours and very happy.
Thanks to the developers for this welcomed upgrade !!!
Keep the good work and take care.

defunct78

@defunct78 said in pfSense Community Edition (CE) 2.5.0 and pfSense Plus 21.02 now available!:

@defunct78 I attempted again, and was able to successfully upgrade. Though it looks like I am now having problems with the unbound service not starting. No logs either, which makes it hard to troubleshoot (resolver.log empty). I was able to switch over DNS Fowarder as suggested in here,

https://www.reddit.com/r/PFSENSE/comments/lo9ag5/since_upgrading_to_25_dns_resolver_unbound_keeps/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

add have restored services.

As a side note, with Unbound, I was doing this.
https://docs.netgate.com/pfsense/en/latest/recipes/dns-over-tls.html

Not sure if that broke with the upgrade.

rameshk

I have installed and configured OpenVPN on my pfSense 2.5 (spare) box yesterday. All working fine so far.

I need to do bit more experiment to understand the algorithms settings as it struggled to connect with AES-256-GCM. I have set the fall back algorithm to AES-128-CBC.

I appreciate any suggestions or guidance.

Thank you

weldong

When 21.02 was released 5 days ago, my SG-3100 showed the upgrade was available. However, by the end of the week (and as of today), it shows I am running the most current version (2.4.5-RELEASE-p1 (arm) ). Looks like the new revisions have been pulled?

Given this and this thread, i think I will wait for the next minor release before upgrading.

bmeeks

@weldong said in pfSense Community Edition (CE) 2.5.0 and pfSense Plus 21.02 now available!:

When 21.02 was released 5 days ago, my SG-3100 showed the upgrade was available. However, by the end of the week (and as of today), it shows I am running the most current version (2.4.5-RELEASE-p1 (arm) ). Looks like the new revisions have been pulled?

Given this and this thread, i think I will wait for the next minor release before upgrading.

Yes, the Netgate team has temporarily pulled the update for SG-3100 boxes as they work on fixing a bug and testing the fix. Posts over the past weekend suggest the bug has been identified and hopefully fixed. They are testing to be sure before releasing a patched upgrade.

mkryger

@bmeeks
Thank you for the info, as i was also a bit confused why it disappeared from my SG-3100.
Can you possibly provide a link for the source of this information, so we will be able to follow the progress and get to know about what the bug was about?
I find it weird the team didn't inform about this in the original post or made it clear elsewhere in this thread.

SteveITS

@mkryger said in pfSense Community Edition (CE) 2.5.0 and pfSense Plus 21.02 now available!:

disappeared from my SG-3100.
Can you possibly provide a link

https://forum.netgate.com/topic/160959/21-02-sudden-lockup/

bmeeks

@mkryger said in pfSense Community Edition (CE) 2.5.0 and pfSense Plus 21.02 now available!:

@bmeeks
Thank you for the info, as i was also a bit confused why it disappeared from my SG-3100.
Can you possibly provide a link for the source of this information, so we will be able to follow the progress and get to know about what the bug was about?
I find it weird the team didn't inform about this in the original post or made it clear elsewhere in this thread.

@teamits beat me to it, but here is a copy of his link as a clickable one: https://forum.netgate.com/topic/160959/21-02-sudden-lockup/.

chudak

@teamits

https://twitter.com/NetgateUSA/status/1362791245546946561

edmund

@weldong - I wish that I had been as smart as you and not "upgraded" as soon as I saw the alert. My system is a SG-4860 and after a couple of days working on it I think I've got it working reliably again.
The main problem that I see with the update process is that you are just told that an update is read to be installed but without any information of details.

bmeeks

@mkryger said in pfSense Community Edition (CE) 2.5.0 and pfSense Plus 21.02 now available!:

@bmeeks
Thank you for the info, as i was also a bit confused why it disappeared from my SG-3100.
Can you possibly provide a link for the source of this information, so we will be able to follow the progress and get to know about what the bug was about?
I find it weird the team didn't inform about this in the original post or made it clear elsewhere in this thread.

I'm not a Reddit user, but I understand something was also posted there by the team (and perhaps on Twitter, but not sure about that one). I'm just not an active social media guys, so I don't follow all those sites.

The main bug causing the lockups appears to have been a sort of estoteric thing where the llvm compiler for ARM hardware was reordering some memory reads and writes for optimization, but that reordering, in one particular case, resulted in a thread locking deadlock situation. If this link opens for you, here is the bug fix: https://github.com/pfsense/FreeBSD-src/commit/4b914061a48bb289ede4d3a7362ed6adf9378c0f. This is also being backported into FreeBSD-12, I believe.

yepitro1986

Still no GUI for ZFS?

yepitro1986

and how about ZFS email notification, is it available on Pfsense 2.5.0

brians

Upgraded SG-5100 to 21.02.
IPsec seems to have issue. Tunnels connect but some are duplicated and shown as disconnected at bottom of Status->IPsec page but instead create a different IPsec ID with a larger con# eg. con400000 vs typical lower number like con1000. These large connections have same information and show connection except there is blank where name should be. If I identify one what it should be and disconnect, reconnecting the "correct" one, or sending IP traffic across a tunnel still creates these incorrect IDs. This also slows down the interface when loading status. Some tunnels are fine and do not have this behaviour. I deleted the tunnels and recreated and same problem.
Anyone else ever see this?
Here is example (which IP address blocked out) that shows disconnected an a con400000 that actually connects...