Version 2.3.4 is available.
-
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
-
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: 19The 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 outLocking package pfSense-kernel-pfSense... done.
Failed -
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-p19Version 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.
-
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 }
-
@tortue:
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 }
Thanks tortue!! My pfsense still does not want to show the update. I tried edit directly to the file and upgrade via shell with option 13, but without success. My dns is ok and I can install packages.
I do not know why it does not work !!!
-
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 I doubt an SSD for the interface of that era is cheep. Even HDD for that era are getting pretty spendy. Haven't looked, but pretty sure SSD is not on the table for 2002 era Dell Inspiron 5100 notebook. I'm okay with it as is with the exception of the upgrades extraction taking so long. Other than that it serves me well for home use.
I could throw the other notebook a colleague donated to me at it to see if it makes any difference. It at least isn't ancient.
Since there is very little activity being indicated, I wonder if maybe the USB driver, or something, is somehow blocking? An hour? The entire USB device could be written/copied in less time. I used to make dup copies of 4 GB USB flash drives on this machine in about 7 minutes or so. That was with earlier versions of FreeBSD. The USB driver has probably changed since then.
-
Check what the mount options are used for the root filesystem on your installation. If it's not using soft-updates the write performance will be absolutely terrible on USB memory.
-
@kpa:
I used the console update (option 13) this time and everything went fine.
I just used the web gui to update my apu2c4 from 2.3.3_1 and everything went fine. I just need to copy the custom amd cpu temperature kernel modul (amdtemp.ko) to /boot/kernel. After reloading the module (or rebooting the system) the temperatures are reported again.
-
Just updated 2.3.2_1 through the GUI and it said it was going to update to 2.3.3_1 but updated to 2.3.4 instead.
Once it finished, OpenBGP kept restarting every 90 seconds or so.
While looking at the logs I noticed that there were also entries saying that vmWare tools was not running.
Had to reinstall both packages.
-
Hello,
After upgrade to 2.3.4 it shows
Version 2.3.4-RELEASE (i386)
built on Wed May 03 15:22:11 CDT 2017
FreeBSD 10.3-RELEASE-p16The system is on the latest version.
Platform nanobsd (2g)
Everything is working fine, but why is -p16 and not -p19?
How to update the version of FreeBSD?Tnx
-
Already discussed here: https://forum.pfsense.org/index.php?topic=129998.0
-
I did everything as well in https://forum.pfsense.org/index.php?topic=129998.0 with the same result that is unsuccessfully.
Thx
-
Yeah, I'm pointing out that there's an already existing thread about the issue, no need to duplicate it.
-
I just did the update and it went fine. Only took a couple of minutes but I do have an old Dell desktop with a 50GB HDD and an AMD Athlon 2 x2 B22 with 8GB of ram which is super overkill for what I need it for. It did scare me by retrying to load the interface 4 times at the end of the update but it worked out. I did notice that the processor was running hotter than normal by about 10C but it seems to have calmed down now.
I'm more annoyed that my 35 day uptime streak got broken ;D >:( ::)
-
Just upgraded. No problem! :D :D
Thnx for your excellent work!
Running : c-icap, clamd, dhcpd, dpinger, ntopng, ntpd, snort, squid, squidGuard, sshd and unbound. -
Hi,
Upgaded yesterday. pfSense SG-4860, pfBlockerNG and Snort. Mostly just simple setup.
I had no problems, thanks for developers!
-
Success! SG-4860 upgraded just fine. Reboot took several minutes longer than usual, which of course is normal for an upgrade, but always a bit of a sweat.
Also ran
pfSsh.php playback generateguicert
from the shell to generate a new certificate for that Chrome issue, thanks for putting that in the release notes. -
For some reason the update still isn't showing for me?
I tried rebooting too, no change. Going to the update page too, also doesn't see anything new. ideas?
-
@kpa:
Check what the mount options are used for the root filesystem on your installation. If it's not using soft-updates the write performance will be absolutely terrible on USB memory.
cat /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/ufsid/570dcd05b61eb735 / ufs rw 1 1 /dev/label/swap0 none swap sw 0 0
mount /dev/ufsid/570dcd05b61eb735 on / (ufs, local, journaled soft-updates) devfs on /dev (devfs, local) /dev/md0 on /tmp (ufs, local) /dev/md1 on /var (ufs, local) devfs on /var/dhcpd/dev (devfs, local)
tunefs -p /dev/ufsid/570dcd05b61eb735 tunefs: POSIX.1e ACLs: (-a) disabled tunefs: NFSv4 ACLs: (-N) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) enabled tunefs: soft update journaling: (-j) enabled tunefs: gjournal: (-J) disabled tunefs: trim: (-t) disabled tunefs: maximum blocks per file in a cylinder group: (-e) 4096 tunefs: average file size: (-f) 16384 tunefs: average number of files in a directory: (-s) 64 tunefs: minimum percentage of free space: (-m) 8% tunefs: space to hold for metadata blocks: (-k) 6408 tunefs: optimization preference: (-o) time tunefs: volume label: (-L)
A little surprised by the device "/dev/ufsid/570dcd05b61eb735". Was expecting something like "/dev/da0s1a".
Looks like it is mounted with journaled soft-updates.
"FreeBSD 9.0 introduced a journaling supplement to soft updates…"
https://en.wikipedia.org/wiki/Soft_updates
https://www.freebsd.org/releases/9.0R/relnotes-detailed.html#FSDon't recall the version at which updates started taking a long time but it very well may have been around the time of leaving FreeBSD 8.x.
Could the journaling supplement to soft updates cause write performance issues for USB flash drives? It's unclear to me.https://www.freebsd.org/doc/handbook/configtuning-disk.html
-
Could a moderator please split this vein out to be it's own thread. Thanks.
Update Extraction Extremely Slow (USB Flash Full Install)
https://forum.pfsense.org/index.php?topic=129994.msg716477#msg716477
https://forum.pfsense.org/index.php?topic=129994.msg716482#msg716482
https://forum.pfsense.org/index.php?topic=129994.msg716483#msg716483
https://forum.pfsense.org/index.php?topic=129994.msg716489#msg716489
https://forum.pfsense.org/index.php?topic=129994.msg716532#msg716532
https://forum.pfsense.org/index.php?topic=129994.msg716541#msg716541
https://forum.pfsense.org/index.php?topic=129994.msg716719#msg716719 -
Took the plunge and updated from the last 2.3.3_p1. Worked great, everything came back up don't see any issues so far.
-
I have just upgraded from 2.3.3-p1 to 2.3.4. This time I used the webGUI. The system runs without issues so far.
I use an APU1D4 with a full installation of pfSense on an mSATA. My installation uses the NUT package which "survived" the upgrade without the need of reinstallation or reconfiguration - great.
-
Hi All,
I have issues with update from 2.3.3-RELEASE-p1 to 2.3.4.
Web GUI says: Unable to check for updates.
From command line, I got the following:
pfSense-upgrade -4
Updating repositories metadata…
Updating pfSense-core repository catalogue...
pkg: https://pkg.pfsense.org/pfSense_v2_3_4_amd64-core/meta.txz: Not Found
repository pfSense-core has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_3_4_amd64-core/packagesite.txz: Not Found
Unable to update repository pfSense-core
Updating pfSense repository catalogue…
pkg: https://pkg.pfsense.org/pfSense_v2_3_4_amd64-pfSense_v2_3_4/meta.txz: Not Found
repository pfSense has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_3_4_amd64-pfSense_v2_3_4/packagesite.txz: Not Found
Unable to update repository pfSenseDNS resolution and internet connection are working fine.
I have copied and tried to get the file via browser, but it seems update site has issue:
404 Not Found
nginx/1.10.3Can you please help me?
-
I have two machines that I updated remotely that are no longer available via openvpn, although they are up and pingable. I use a TAP UDP configuration, and both machines are awake, but fail TLS negotiation. I am using the current Tunnelblick beta.
The relevant error from Tunnelblick reads:
2017-05-07 08:22:20 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
2017-05-07 08:22:20 TLS Error: TLS handshake failedOh well… There goes my Sunday. :-[