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

johnpoz

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

Where did you get the 21.02 image?

If you want an actual image to do a clean install with - open a ticket with netgate, they will send you a link to image very quickly.. Took a whole 28 minutes the other day during the drop of new, while I am sure they are quite busy with legit tickets and not just requests for images.

If you updated to 2.5 vs 21.02 - you were prob running the CE version on your netgate appliance vs the FE (factory edition)..

matthijs

One big mess after upgrading to 2.5 with named/Bind, this is it, I am done with PFsense Netgate. I have those Issues with conflicting rndc ports between named and unbound for years forcing me to run the named/bind rndc port on a virtual IP instead of localhost/172.0.0.1 I am migrating to OPNSense now, bye bye PFSense

matthijs

Update !

The issue is de Bind package,

[1/5] Installing protobuf-3.13.0,1...
[1/5] Extracting protobuf-3.13.0,1: .......... done
[2/5] Installing protobuf-c-1.3.2_6...
[2/5] Extracting protobuf-c-1.3.2_6: .......... done
[3/5] Installing fstrm-0.6.0...
[3/5] Extracting fstrm-0.6.0: .......... done
[4/5] Installing bind916-9.16.11...
[4/5] Extracting bind916-9.16.11: .......... done
[5/5] Installing pfSense-pkg-bind-9.16_9...
[5/5] Extracting pfSense-pkg-bind-9.16_9: .......... done
Saving updated package information...
overwrite!
Loading package configuration... done.
Configuring package components...
Loading package instructions...
Custom commands...
Executing custom_php_install_command()...done.
Executing custom_php_resync_config_command()...rndc: connect failed: 10.17.19.1#8953: timed out

The install procedure (resync config command) is trying to find de rncd port on the interface Bind/Named is bind to in my configuration (a virtual IP address) but I guess it is bind to 127.0.0.1 instead failing the installation/upgrade

Sucks Big Time because I have a very big and complex bind configuration with Acme integration, and have have this rndc issues for years now.

So this sucks big time for me !!

edmund

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

Always take a backup of the firewall configuration prior to any major change to the firewall, such as an upgrade.

Everything would go much better if the upgrade process made a backup automatically and offered users the ability to quickly return to the previous release when they run into problems. I would see this as a major feature.

mmichael

Hello,

thanks for the new Release. Update on two VM's was easy! But I have a issue with my IPSEC-Tunnels. The tunnels to Machines with 2.4.1 didn't come online.
A IPSEC-Tunnel between two 2.5 Machines is up - but on one Machine "marked as down" (but working).
For business use - I'll wait a bit bevor upgrading
Regards
Martin

plfinch

Upgrade of my primary firewall, an SG-5100, was successful via GUI update. I did experience the following:

Could not connect OpenVPN. Looks like pfSense Dynamic DNS did not actually update Google DNS after boot. I forced the update (“Save & Force Update”) and all good once propogated.
Arpwatch continually reported 2 devices flip-flopping on one IP. Rebooted both devices to resolve.

chudak

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

Upgrade of my primary firewall, an SG-5100, was successful via GUI update. I did experience the following:

Could not connect OpenVPN. Looks like pfSense Dynamic DNS did not actually update Google DNS after boot. I forced the update (“Save & Force Update”) and all good once propogated.

Arpwatch continually reported 2 devices flip-flopping on one IP. Rebooted both devices to resolve.

Did you have to redo OpenVPN ovpn config files for clients ?

gpfsenser

The update bricked my SG-1100. Had to access via serial (which took a bit because my OSX tool was not compatible with recent OS). After this serial connect issue was solved - lots of errors on the menu on pretty much every option. Opened a support ticket, downloaded recovery image, and reinstalled. Would recommend anyone with a netgate device to actually do this first just to have as a standby. Things running well now. Having your configuration backed up is a must. Thanks for the update! I hope the reliability of updates improves - I'm like 0/3 now. ;-) New version UI runs faster, package manager runs better - no downsides discovered yet.

SebM

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

Opened a support ticket, downloaded recovery image, and reinstalled. Would recommend anyone with a netgate device to actually do this first just to have as a standby.

Underrated comment right there!

plfinch

Did you have to redo OpenVPN ovpn config files for clients ?

No. No changes at all are required on the pfSense appliance or the openvpn client devices after upgrading. The openvpn config information is fully contained in the pfSense backup file. Even swapping to my standby/backup firewall loaded from the same config file, my client devices can connect without issue.

plfinch

Opened a support ticket, downloaded recovery image, and reinstalled. Would recommend anyone with a netgate device to actually do this first just to have as a standby.

Even after successfully upgrading my SG-5100 via the GUi, I went back and did a clean install from the memdisk image and reloaded the post-upgrade config backup. I always do this on updates to ensure I have a fresh clean build.

SebM

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

Opened a support ticket, downloaded recovery image, and reinstalled. Would recommend anyone with a netgate device to actually do this first just to have as a standby.

Even after successfully upgrading my SG-5100 via the GUi, I went back and did a clean install from the memdisk image and reloaded the post-upgrade config backup. I always do this on updates to ensure I have a fresh clean build.

Sounds pretty good actually, I like it the idea of a fresh install and also installing the default file system and other options (I think it’s ZFS now, right?)

So restoring the backup of 2.4.5-p1 onto 21.02 shouldn’t be a problem, right?

gpfsenser

@sebm For me - no issues faced, configuration restore worked on the first attempt.

tele_01

I've updated an APU2C4 from 2.4.5p1 to 2.5. After adjusting "Fallback Data Encryption Algorithm" to "None (No Encryption)" the setup was working fine with my uploaded backup data from 2.4.5p1. Also Squid and pfBlockerNG Devil are working well. A real impact is the VPN speed even if I've used nearly the same settings as my VPN provider taught and were existent under 2.4.5p1. I use OpenVPN with NordVPN and after updating the d/l speed is the half. Under 2.4.5p1 I've had about 96mbit now at about 50mbit. I've tried different options also under "Allow Compression" in the VPN Client settings but no change achieved so far. If this will is not getting better I'll go back to 2.4.5p1.

tele_01

@tele_01 I've forgot to mention that the processor load was not above 90% via SSH. My feeling is that OpenVPN was different migrated into FreeBSD 11.x than under 12.x within pfSense because on 2.4.5p1 and having sometimes more than 100mbit in d/l (provider hosts max 120mbit) the processor load was at about 94%.

elvisimprsntr

Performed an in place upgrade on my backup Protectli FW1 to see how the upgrade went, followed by a memstick clean install.
Then performed an in place upgrade on my primary Protectli FW4A without any issues.

Taz79

Upgraded my SG-1100 from 2.4.5p1 to 21.02.. Upgrade went fine. The network was down for 14 minutes, so dont worry if it takes a long time. Everything came up and my 2 VPN tunnels came up again without any issues.

Good Job Netgate! :)

brians

Upgraded my home custom PC system based on an old HP proudest desktop to 2.5.0 with no major issues. I had to manually start DNS resolver as DNS was not working right after but maybe was just my impatience. OpenVPN server for client works, all IPsec tunnels up.

The only production system I did was an SG-2220 so far at one of our locations over weekend I did remotely. It seemed to go smooth but when I was in there onsite yesterday no Internet but the IPsec tunnels were up. After troubleshooting it was a bad GW which I had left in there from an old static WAN configuration, but it is currently using GW via DHCP. I removed this static GW and made sure the DHCP GW is default which solved the issue and works fine now.

Hesitant to do my SG-5100s maybe will wait a bit and do first while onsite.

I have customer with SG-4860 that has lots of VPN tunnels, VLANs etc. it has been up for 230 days... probably will wait on that one for a while.

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.