Version 2.3.4 is available.
-
The OS updates are patch level updates so I wouldn't worry too much about that.
Doesn't look like many if any of the changes affect me and what I use so I may go for it.
-
Here is the log i am seeing right now:
>>> Updating repositories metadata... Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. >>> Unlocking package pfSense-kernel-pfSense... done. >>> Downloading upgrade packages... Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. Checking for upgrades (143 candidates): .......... done Processing candidates (143 candidates): pkg: unbound has a missing dependency: libevent2 Processing candidates (143 candidates)...... done Checking integrity... done (0 conflicting) The following 44 package(s) will be affected (of 0 checked): New packages to be INSTALLED: libevent: 2.1.8 [pfSense] Installed packages to be UPGRADED: webp: 0.5.2 -> 0.5.2_1 [pfSense] unbound: 1.6.0 -> 1.6.1 [pfSense] strongswan: 5.5.1 -> 5.5.1_1 [pfSense] sqlite3: 3.15.1_1 -> 3.17.0 [pfSense] smartmontools: 6.5_1 -> 6.5_2 [pfSense] png: 1.6.27 -> 1.6.29 [pfSense] php-xdebug: 2.4.1_1 -> 2.5.0 [pfSense] pftop: 0.7_7 -> 0.7_8 [pfSense] pfSense-default-config: 2.3.3_1 -> 2.3.4 [pfSense-core] pfSense-base: 2.3.3_1 -> 2.3.4 [pfSense-core] pfSense: 2.3.3_1 -> 2.3.4 [pfSense] perl5: 5.24.1.r4_1 -> 5.24.1 [pfSense] pcre: 8.39_1 -> 8.40 [pfSense] ntp: 4.2.8p9_1 -> 4.2.8p10_2 [pfSense] nginx: 1.10.2_3,2 -> 1.10.3_1,2 [pfSense] lzo2: 2.09 -> 2.10_1 [pfSense] libssh2: 1.8.0,2 -> 1.8.0,3 [pfSense] libsodium: 1.0.11_1 -> 1.0.12 [pfSense] libnghttp2: 1.18.0 -> 1.21.0 [pfSense] ldns: 1.6.17_5 -> 1.7.0 [pfSense] ipmitool: 1.8.17_1 -> 1.8.18 [pfSense] gmp: 5.1.3_3 -> 6.1.2 [pfSense] glib: 2.46.2_4 -> 2.46.2_5 [pfSense] freetype2: 2.6.3 -> 2.7.1 [pfSense] dhcp6: 20080615.1 -> 20080615.2 [pfSense] curl: 7.53.0 -> 7.54.0 [pfSense] ca_root_nss: 3.28.1 -> 3.30.2 [pfSense] bind-tools: 9.11.0P3 -> 9.11.1 [pfSense] apcupsd: 3.14.14 -> 3.14.14_1 [pfSense] Installed packages to be REINSTALLED: vstr-1.0.15_1 [pfSense] tiff-4.0.7_1 [pfSense] nettle-3.3 [pfSense] libxml2-2.9.4 [pfSense] libidn-1.33_1 [pfSense] libiconv-1.14_10 [pfSense] libedit-3.1.20150325_2,1 [pfSense] json-c-0.12.1 [pfSense] jpeg-turbo-1.5.1 [pfSense] idnkit-1.0_6 [pfSense] giflib-5.1.4 [pfSense] expat-2.2.0_1 [pfSense] dnsmasq-2.76,1 [pfSense] (options changed) check_reload_status-0.0.7 [pfSense] (direct dependency changed: libevent) Number of packages to be installed: 1 Number of packages to be upgraded: 29 Number of packages to be reinstalled: 14 The process will require 3 MiB more space. Upgrade is complete. Rebooting in 10 seconds. >>> Locking package pfSense-kernel-pfSense... done. SuccessEven after restart, it still shows upgrade available, i do it again, same output as above etc.
Did not make a backup of config :/
:'( -
Well that was painless aside from having to reinstall the temp sensor patch for my APU2C4.
-
@NEK4TE:
Hello,
After download / upgrade completed message / reboot, it still shows 2.3.3-RELEASE-p1 (amd64) under version, and telling me that new update is available:
2.3.3-RELEASE-p1 (amd64)
built on Thu Mar 09 07:17:41 CST 2017
FreeBSD 10.3-RELEASE-p19Version 2.3.4 is available.
Any1 having this issue?
Tnx
Had the same issue. Now my DNS is not working. Did a complete fresh install and restored config and things are not right.
-
The OS updates are patch level updates so I wouldn't worry too much about that.
Doesn't look like many if any of the changes affect me and what I use so I may go for it.
Well that was painless aside from having to reinstall the temp sensor patch for my APU2C4.
Cool 8)@NEK4TE:
Here is the log i am seeing right now:
>>> Updating repositories metadata... Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. >>> Unlocking package pfSense-kernel-pfSense... done. >>> Downloading upgrade packages... Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. Checking for upgrades (143 candidates): .......... done Processing candidates (143 candidates): pkg: unbound has a missing dependency: libevent2 Processing candidates (143 candidates)...... done Checking integrity... done (0 conflicting) The following 44 package(s) will be affected (of 0 checked): New packages to be INSTALLED: libevent: 2.1.8 [pfSense] Installed packages to be UPGRADED: webp: 0.5.2 -> 0.5.2_1 [pfSense] unbound: 1.6.0 -> 1.6.1 [pfSense] strongswan: 5.5.1 -> 5.5.1_1 [pfSense] sqlite3: 3.15.1_1 -> 3.17.0 [pfSense] smartmontools: 6.5_1 -> 6.5_2 [pfSense] png: 1.6.27 -> 1.6.29 [pfSense] php-xdebug: 2.4.1_1 -> 2.5.0 [pfSense] pftop: 0.7_7 -> 0.7_8 [pfSense] pfSense-default-config: 2.3.3_1 -> 2.3.4 [pfSense-core] pfSense-base: 2.3.3_1 -> 2.3.4 [pfSense-core] pfSense: 2.3.3_1 -> 2.3.4 [pfSense] perl5: 5.24.1.r4_1 -> 5.24.1 [pfSense] pcre: 8.39_1 -> 8.40 [pfSense] ntp: 4.2.8p9_1 -> 4.2.8p10_2 [pfSense] nginx: 1.10.2_3,2 -> 1.10.3_1,2 [pfSense] lzo2: 2.09 -> 2.10_1 [pfSense] libssh2: 1.8.0,2 -> 1.8.0,3 [pfSense] libsodium: 1.0.11_1 -> 1.0.12 [pfSense] libnghttp2: 1.18.0 -> 1.21.0 [pfSense] ldns: 1.6.17_5 -> 1.7.0 [pfSense] ipmitool: 1.8.17_1 -> 1.8.18 [pfSense] gmp: 5.1.3_3 -> 6.1.2 [pfSense] glib: 2.46.2_4 -> 2.46.2_5 [pfSense] freetype2: 2.6.3 -> 2.7.1 [pfSense] dhcp6: 20080615.1 -> 20080615.2 [pfSense] curl: 7.53.0 -> 7.54.0 [pfSense] ca_root_nss: 3.28.1 -> 3.30.2 [pfSense] bind-tools: 9.11.0P3 -> 9.11.1 [pfSense] apcupsd: 3.14.14 -> 3.14.14_1 [pfSense] Installed packages to be REINSTALLED: vstr-1.0.15_1 [pfSense] tiff-4.0.7_1 [pfSense] nettle-3.3 [pfSense] libxml2-2.9.4 [pfSense] libidn-1.33_1 [pfSense] libiconv-1.14_10 [pfSense] libedit-3.1.20150325_2,1 [pfSense] json-c-0.12.1 [pfSense] jpeg-turbo-1.5.1 [pfSense] idnkit-1.0_6 [pfSense] giflib-5.1.4 [pfSense] expat-2.2.0_1 [pfSense] dnsmasq-2.76,1 [pfSense] (options changed) check_reload_status-0.0.7 [pfSense] (direct dependency changed: libevent) Number of packages to be installed: 1 Number of packages to be upgraded: 29 Number of packages to be reinstalled: 14 The process will require 3 MiB more space. Upgrade is complete. Rebooting in 10 seconds. >>> Locking package pfSense-kernel-pfSense... done. SuccessEven after restart, it still shows upgrade available, i do it again, same output as above etc.
Did not make a backup of config :/
:'(Always make backups. Then make backups of the backups. Then store the backups in multiple places, in theft proof, fire proof, disaster proof, child proof boxes….....
It seems that this issue with upgrade reporting the wrong version is a known issue. I found this ( https://forum.pfsense.org/index.php?topic=129310.0 ) and it appears to be related to some kind of packaging issue with the system packages. Try running the pkg-static command stated in the link I posted and let us know how you get on.
EDIT
I also just had a thought. Did the guys having issues try to upgrade from the nano version? Also where you using the 32bit version? Both are now depreciated and I'm not sure if the devs have figured out a clear upgrade path to the x86_64 full version. This could cause issues if you have a system that does not support 64bit or if you have a nano 2.3.3-p1 install. -
Why do I now have a Netgate Unique ID?
-
Why do I now have a Netgate Unique ID?
Dunno but netgate have been moving stuff off of the pfsense side to theirs. The blog is an example.
-
The OS updates are patch level updates so I wouldn't worry too much about that.
Doesn't look like many if any of the changes affect me and what I use so I may go for it.
Well that was painless aside from having to reinstall the temp sensor patch for my APU2C4.
Cool 8)@NEK4TE:
Here is the log i am seeing right now:
>>> Updating repositories metadata... Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. >>> Unlocking package pfSense-kernel-pfSense... done. >>> Downloading upgrade packages... Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. Checking for upgrades (143 candidates): .......... done Processing candidates (143 candidates): pkg: unbound has a missing dependency: libevent2 Processing candidates (143 candidates)...... done Checking integrity... done (0 conflicting) The following 44 package(s) will be affected (of 0 checked): New packages to be INSTALLED: libevent: 2.1.8 [pfSense] Installed packages to be UPGRADED: webp: 0.5.2 -> 0.5.2_1 [pfSense] unbound: 1.6.0 -> 1.6.1 [pfSense] strongswan: 5.5.1 -> 5.5.1_1 [pfSense] sqlite3: 3.15.1_1 -> 3.17.0 [pfSense] smartmontools: 6.5_1 -> 6.5_2 [pfSense] png: 1.6.27 -> 1.6.29 [pfSense] php-xdebug: 2.4.1_1 -> 2.5.0 [pfSense] pftop: 0.7_7 -> 0.7_8 [pfSense] pfSense-default-config: 2.3.3_1 -> 2.3.4 [pfSense-core] pfSense-base: 2.3.3_1 -> 2.3.4 [pfSense-core] pfSense: 2.3.3_1 -> 2.3.4 [pfSense] perl5: 5.24.1.r4_1 -> 5.24.1 [pfSense] pcre: 8.39_1 -> 8.40 [pfSense] ntp: 4.2.8p9_1 -> 4.2.8p10_2 [pfSense] nginx: 1.10.2_3,2 -> 1.10.3_1,2 [pfSense] lzo2: 2.09 -> 2.10_1 [pfSense] libssh2: 1.8.0,2 -> 1.8.0,3 [pfSense] libsodium: 1.0.11_1 -> 1.0.12 [pfSense] libnghttp2: 1.18.0 -> 1.21.0 [pfSense] ldns: 1.6.17_5 -> 1.7.0 [pfSense] ipmitool: 1.8.17_1 -> 1.8.18 [pfSense] gmp: 5.1.3_3 -> 6.1.2 [pfSense] glib: 2.46.2_4 -> 2.46.2_5 [pfSense] freetype2: 2.6.3 -> 2.7.1 [pfSense] dhcp6: 20080615.1 -> 20080615.2 [pfSense] curl: 7.53.0 -> 7.54.0 [pfSense] ca_root_nss: 3.28.1 -> 3.30.2 [pfSense] bind-tools: 9.11.0P3 -> 9.11.1 [pfSense] apcupsd: 3.14.14 -> 3.14.14_1 [pfSense] Installed packages to be REINSTALLED: vstr-1.0.15_1 [pfSense] tiff-4.0.7_1 [pfSense] nettle-3.3 [pfSense] libxml2-2.9.4 [pfSense] libidn-1.33_1 [pfSense] libiconv-1.14_10 [pfSense] libedit-3.1.20150325_2,1 [pfSense] json-c-0.12.1 [pfSense] jpeg-turbo-1.5.1 [pfSense] idnkit-1.0_6 [pfSense] giflib-5.1.4 [pfSense] expat-2.2.0_1 [pfSense] dnsmasq-2.76,1 [pfSense] (options changed) check_reload_status-0.0.7 [pfSense] (direct dependency changed: libevent) Number of packages to be installed: 1 Number of packages to be upgraded: 29 Number of packages to be reinstalled: 14 The process will require 3 MiB more space. Upgrade is complete. Rebooting in 10 seconds. >>> Locking package pfSense-kernel-pfSense... done. SuccessEven after restart, it still shows upgrade available, i do it again, same output as above etc.
Did not make a backup of config :/
:'(Always make backups. Then make backups of the backups. Then store the backups in multiple places, in theft proof, fire proof, disaster proof, child proof boxes….....
It seems that this issue with upgrade reporting the wrong version is a known issue. I found this ( https://forum.pfsense.org/index.php?topic=129310.0 ) and it appears to be related to some kind of packaging issue with the system packages. Try running the pkg-static command stated in the link I posted and let us know how you get on.
EDIT
I also just had a thought. Did the guys having issues try to upgrade from the nano version? Also where you using the 32bit version? Both are now depreciated and I'm not sure if the devs have figured out a clear upgrade path to the x86_64 full version. This could cause issues if you have a system that does not support 64bit or if you have a nano 2.3.3-p1 install.Something is definitely messed up badly, not even SSH is working for me.
-
Sounds like a fresh install is in order for you.
You don't have any config backups?
-
yep, definitely, fresh install :/
I do have, some 'older' backups, better then nothing :)
This is actually the last time i am 'rushing' upgrades.
Lesson learned, hard way :-X
-
No worries as a fresh install is trivial…..as long as you have a current config..... :o
-
-
I've decided to try update to 2.3.5-DEVELOPMENT (amd64) , which worked just fine.
I did this to 'save' the config file before i do clean install.
A question ( if this can be answered ) , is it okay to save this config now, and restore it on 2.3.4 ?
I would say, at least for now, everything works just fine on 2.3.5 , i am not seeing any errors / problems.
(Should i even stay on development ?)Thanks again
-
DNS issues here as well.
Cannot log in to GUI via FQDN
Let's Encrypt cert claiming to be a mismatch
Bit of a mess, I'd hold off on upgrading just yet.
-
Can't ping 8.8.8.8
Can't browse the web
One ios client has twitter working. That's about it.
-
Upgraded from 2.3.3-1 on a "Dell-PC" (2005 - my pfSense gateway/firewall since 2007) to 2.3.4.
Took 2 minutes : ;D
I'm posting here 'through' it right now.2.3.4-RELEASE (amd64) built on Wed May 03 15:13:29 CDT 2017 FreeBSD 10.3-RELEASE-p19 The system is on the latest version.Used packages : avahi - openvpn-client-export - acme** - nut.
** : Let's Encrypts certificates were already ok, no need to redo anything (see Changelog)
-
Went very smoothly. Following advice from here I always do a full backup of my config.
-
I upgraded three units this morning (Lanner FW-7525, pfSense SG-2440, Qotom Q355G4) from version 2.3.3-P1 to 2.3.4 without any problems. Everything is running fine, thanks to the pfSense developers!
-
The Netgate Unique ID and other details are explained on the blog ( https://www.netgate.com/blog/pfsense-2-3-4-release-now-available.html ) and the release notes ( https://doc.pfsense.org/index.php/2.3.4_New_Features_and_Changes )
-
Update when fine, but now cannot login to the GUI I get "504 Gateway Time-out" after I put in my credential in the login page. Ran the script to update the web gui certificate from the console and still cannot login.
Is there a fix to this issue?
Thanks
