Version 2.3.4 is available.



  • 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-p19

    Version 2.3.4 is available.

    Any1 having this issue?

    Tnx



  • Wow, releasing before a weekend. That's brave.

    I'll wait a bit…...    ;)



  • :D

    Probably i will have to wait as well due to issue i am seeing :P



  • @Jailer:

    Wow, releasing before a weekend. That's brave.

    I'll wait a bit…...    ;)

    Yeah, I just logged in to my firewall to check on some things I changed today and saw that the update was out. After reading the changelog I have some concerns about how well my config is going to translate over. Especially with all the changes to the base OS, the WiFi stack move, oVPN version upgrade etc. I think I'm gonna leave it a little while just to see how things pan out.

    @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-p19

    Version 2.3.4 is available.

    Any1 having this issue?

    Tnx

    Did you take a config backup before you did the upgrade? If so is it possible to do a clean install and then restore the config on to it? Was there anything unusual posted in the log output for the upgrade?



  • 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.
    Success
    

    Even 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-p19

    Version 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.



  • @Jailer:

    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.

    @Jailer:

    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.
    Success
    

    Even 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?



  • @Jailer:

    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.



  • @M3PH:

    @Jailer:

    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.

    @Jailer:

    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.
    Success
    

    Even 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



  • @Jailer:

    Why do I now have a Netgate Unique ID?

    Yeah, same question here.



  • 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!


  • Rebel Alliance Developer Netgate

    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


  • Rebel Alliance Developer Netgate

    That is not a known issue or one anyone has encountered during release testing. Please start a new thread for assistance.



  • Well I've tried to upgrade a couple of test boxes here and they are all getting time outs. Must be to many people hitting that upgrade button :P

    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 (161 candidates): .......... done
    Processing candidates (161 candidates): ... done
    The following 75 package(s) will be affected (of 0 checked):

    New packages to be INSTALLED:
    libevent: 2.1.8 [pfSense]
    libgpg-error: 1.27 [pfSense]
    libgcrypt: 1.7.6 [pfSense]
    gnutls: 3.5.9 [pfSense]
    trousers: 0.3.14_1 [pfSense]
    tpm-emulator: 0.7.4_1 [pfSense]
    p11-kit: 0.23.5 [pfSense]
    libtasn1: 4.10 [pfSense]
    libunistring: 0.9.7 [pfSense]
    hyperscan: 4.4.1_1 [pfSense]

    Installed packages to be UPGRADED:
    unbound: 1.6.0 -> 1.6.1 [pfSense]
    suricata: 3.1.2 -> 3.2.1_1 [pfSense]
    strongswan: 5.5.1 -> 5.5.1_1 [pfSense]
    squidclamav: 6.14 -> 6.16 [pfSense]
    squid: 3.5.23 -> 3.5.24_2 [pfSense]
    sqlite3: 3.15.1_1 -> 3.17.0 [pfSense]
    smartmontools: 6.5_1 -> 6.5_2 [pfSense]
    python27: 2.7.13_1 -> 2.7.13_3 [pfSense]
    pkgconf: 1.1.0 -> 1.3.0,1 [pfSense]
    php-xdebug: 2.4.1_1 -> 2.5.0 [pfSense]
    pftop: 0.7_7 -> 0.7_8 [pfSense]
    pfSense-rc: 2.3.3_1 -> 2.3.4 [pfSense-core]
    pfSense-pkg-suricata: 3.1.2_2 -> 3.2.1_1 [pfSense]
    pfSense-kernel-pfSense: 2.3.3_1 -> 2.3.4 [pfSense-core]
    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]
    nss: 3.28.1_1 -> 3.30.2 [pfSense]
    nspr: 4.13.1 -> 4.14_1 [pfSense]
    nginx: 1.10.2_3,2 -> 1.10.3_1,2 [pfSense]
    mysql56-client: 5.6.35_1 -> 5.6.35_3 [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]
    libnet: 1.1.6_4,1 -> 1.1.6_5,1 [pfSense]
    liblz4: 131 -> 1.7.5,1 [pfSense]
    libhtp: 0.5.22 -> 0.5.23 [pfSense]
    lha: 1.14i_6 -> 1.14i_7 [pfSense]
    ldns: 1.6.17_5 -> 1.7.0 [pfSense]
    krb5: 1.14.4 -> 1.15.1_4 [pfSense]
    jansson: 2.9 -> 2.10 [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]
    dhcp6: 20080615.1 -> 20080615.2 [pfSense]
    curl: 7.53.0 -> 7.54.0 [pfSense]
    clamav: 0.99.2_2 -> 0.99.2_3 [pfSense]
    ca_root_nss: 3.28.1 -> 3.30.2 [pfSense]
    c-icap-modules: 0.4.3 -> 0.4.5 [pfSense]
    c-icap: 0.4.3,2 -> 0.4.4,2 [pfSense]
    bind-tools: 9.11.0P3 -> 9.11.1 [pfSense]
    GeoIP: 1.6.9 -> 1.6.10 [pfSense]

    Installed packages to be REINSTALLED:
    vstr-1.0.15_1 [pfSense]
    openldap-client-2.4.44 [pfSense]
    nettle-3.3 [pfSense]
    luajit-2.0.4_1 [pfSense]
    libyaml-0.1.6_2 [pfSense]
    libxml2-2.9.4 [pfSense]
    libpcap-1.8.1 [pfSense]
    libltdl-2.4.6 [pfSense]
    libidn-1.33_1 [pfSense]
    libiconv-1.14_10 [pfSense]
    libffi-3.2.1 [pfSense]
    libedit-3.1.20150325_2,1 [pfSense]
    json-c-0.12.1 [pfSense]
    idnkit-1.0_6 [pfSense]
    gettext-runtime-0.19.8.1_1 [pfSense]
    expat-2.2.0_1 [pfSense]
    dnsmasq-2.76,1 [pfSense] (options changed)
    cyrus-sasl-2.1.26_12 [pfSense]
    check_reload_status-0.0.7 [pfSense] (direct dependency changed: libevent)

    Number of packages to be installed: 10
    Number of packages to be upgraded: 46
    Number of packages to be reinstalled: 19

    The process will require 43 MiB more space.
    92 MiB to be downloaded.
    [1/75] Fetching python27-2.7.13_3.txz: …....... done
    [2/75] Fetching pkgconf-1.3.0,1.txz: ….... done
    [3/75] Fetching php-xdebug-2.5.0.txz: …....... done
    [4/75] Fetching pftop-0.7_8.txz: …..... done
    [5/75] Fetching pfSense-rc-2.3.4.txz: . done
    [6/75] Fetching pfSense-pkg-suricata-3.2.1_1.txz: …....... done
    [7/75] Fetching pfSense-kernel-pfSense-2.3.4.txz: ….. done
    pkg: https://pkg.pfsense.org/pfSense_v2_3_4_amd64-core/All/pfSense-kernel-pfSense-2.3.4.txz: Operation timed out

    Locking package pfSense-kernel-pfSense... done.
    Failed


  • Rebel Alliance Developer Netgate

    That's entirely possible. Give it a bit and try again. :-)



  • For me the new update does not appear. I also tried via shell.




  • My update to 2.3.4 went smoothly.  Everything seems to be working. Thanks for the good work.



  • I used the console update (option 13) this time and everything went fine.



  • @kpa:

    I used the console update (option 13) this time and everything went fine.

    I always use console and a reboot beforehand to be sure there is not some issue lurking to manifest itself at the most inopportune time and to create a demarcation point before the upgrade.  i.e. it booted fine before the upgrade, so any issue is likely to be upgrade related as apposed to something else going wrong.  That's nice to know when troubleshooting.



  • The biggest issue I seem to have with upgrades is the extractions are taking forever.  We'll maybe not quite forever but a really long time.  Like about an hour.  A few individual ones take probably 10 to 15 minutes.

    Pretty sure that's not normal.

    Intel(R) Pentium(R) 4 CPU 2.66GHz
    2 GB RAM
    Full install on USB 2 flash drive (idle, so don't think that is the cause)



  • For me it took couple of minutes. I have a rather old but still quite fast 30GB SSD on my system. I would guess your issue is the USB drive.



  • @kpa:

    For me it took couple of minutes. I have a rather old but still quite fast 30GB SSD on my system. I would guess your issue is the USB drive.

    But it is idle when this is going on.  Just occasional activity.



  • @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-p19

    Version 2.3.4 is available.

    Any1 having this issue?

    Tnx

    I'm having the same issue.  Still showing 2.3.3-p1 after upgrade from WebGUI.  I rebooted and then did Console Option 13, which said it would download 2 MiB.  Even after reboot, still showing 2.3.3-p1.

    I'm gonna do a clean install of 2.3.4 and restore from config backup.  Never done that before.  Hope the config restore works or I'm extra screwed.

    Edit:  Success.  :D  I downloaded the 2.3.4 Release amd64 memstick image, used Win32DiskImager (on Windows) to create a USB install drive.  Also followed the Automatically Restore During Install instructions and created an additional USB drive with \conf\config.xml with an unencrypted backup file.  Did the Quick & Easy install and crossed my fingers.  After reboot, it came back 2.3.4 with my config automatically restored.

    The only hiccup was it didn't re-install packages.  I use FreeRADIUS so I'm glad I created a temporary Wi-Fi network that was WPA2-Personal so I could log back into the WebGUI.  Manually reinstalled all packages (and the package configuration settings magically restored, thank goodness).  After another reboot, everything is back to normal on 2.3.4-RELEASE and all packages running.

    I immediately made another backup.

    Edit 2:  In other words, this part in the documentation is incorrect:

    pfSense has, as part of the installation routine, a "Pre-Flight Install" or PFI. PFI will check for an existing configuration on a USB drive, and use it instead. When installing to the target disk, it will copy this configuration, and then the first time the WebGUI is visited afterward, all packages will be reinstalled.

    Packages have to be reinstalled manually after the Pre-Flight Install process is performed.



  • @NOYB:

    The biggest issue I seem to have with upgrades is the extractions are taking forever.  We'll maybe not quite forever but a really long time.  Like about an hour.  A few individual ones take probably 10 to 15 minutes.

    Pretty sure that's not normal.

    Intel(R) Pentium(R) 4 CPU 2.66GHz
    2 GB RAM
    Full install on USB 2 flash drive (idle, so don't think that is the cause)

    This exact same behavior is reported by FreeNAS users that install to USB drives. Do yourself a favor and put a cheap SSD in there.



  • Well, what i did … as i wrote in this thread ... as 2.3.4 did not work, and i did not have a backup of config from 2.3.3, i upgraded to experimental which worked just fine, made a backup of config and then installed fresh install of 2.3.4 and restored the same backup.

    Everything is working fine, and running latest stable version.



  • Upgraded fine on my PC Engines APU2 I like the WAN Up time display as I have my ADSL setup to recycle every night



  • For who was able to update, what is the content of the file /usr/local/etc/pkg/repos/pfSense.conf after the upgrade?



  • Just performed the upgrade via the web interface and no issues here.

    Contents of  /usr/local/etc/pkg/repos/pfSense.conf

    
    FreeBSD: { enabled: no }
    
    pfSense-core: {
      url: "pkg+https://pkg.pfsense.org/pfSense_v2_3_4_amd64-core",
      mirror_type: "srv",
      signature_type: "fingerprints",
      fingerprints: "/usr/local/share/pfSense/keys/pkg",
      enabled: yes
    }
    
    pfSense: {
      url: "pkg+https://pkg.pfsense.org/pfSense_v2_3_4_amd64-pfSense_v2_3_4",
      mirror_type: "srv",
      signature_type: "fingerprints",
      fingerprints: "/usr/local/share/pfSense/keys/pkg",
      enabled: yes
    }
    
    

Log in to reply