Version 2.3.4 is available.

dread · May 6, 2017, 5:08 PM

Hi,

Upgaded yesterday. pfSense SG-4860, pfBlockerNG and Snort. Mostly just simple setup.

I had no problems, thanks for developers!

Crispix · May 6, 2017, 5:43 PM

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.

colinstu · May 6, 2017, 7:01 PM

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?

NOYB · May 6, 2017, 8:53 PM

@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#FS

Don'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

NOYB · May 6, 2017, 9:35 PM

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

apara · May 7, 2017, 12:17 AM

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.

pvoigt · May 7, 2017, 9:41 AM

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.

lalamper · May 7, 2017, 10:35 AM

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 pfSense

DNS 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.3

Can you please help me?

bfeitell · May 7, 2017, 12:29 PM

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 failed

Oh well… There goes my Sunday. :-[

lalamper · May 7, 2017, 5:25 PM

@bfeitell:

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 failed

Oh well… There goes my Sunday. :-[
[/quote]

Maybe your clients use outdated TLS version or the configuration of the server and clients differs.

pppfsense · May 8, 2017, 3:08 PM

Upgraded my main and backup pfsense under ESXi.
Quicker and smoother than previous times.

Good job pfSense Team!

steve_v · May 9, 2017, 6:53 AM

I award this update a solid E. E for Epic fail.

PCEngines APU2, applied update from webui -> fails to boot.

And here I am with all my serial cables at work. Awesome.

Is this one of the "new features"?

NOYB · May 9, 2017, 7:03 AM

@steve_v:

I award this update a solid E. E for Epic fail.

PCEngines APU2, applied update from webui -> fails to boot.

And here I am with all my serial cables at work. Awesome.

Is this one of the "new features"?

I award your update preparedness a solid F. F for fail.

Apparently without even knowing what the issue is you assign blame. Another F.

steve_v · May 9, 2017, 7:16 AM

@NOYB:

I award your update preparedness a solid F. F for fail.

Update preparedness == I have another router preconfigured.

Apparently without even knowing what the issue is you assign blame. Another F.

Considering that the only change involved here is an update via the webui, I have a fairly good idea as to what broke it…
Took a backup -> rebooted -> ran update -> boot fail.

Sure, I'd love to see the console messages, but like I said I won't have a serial cable handy until tomorrow.
Given the almost total lack of disk access, it appears to be failing at the bootloader, or at the very start of the boot process.

This thing is supposed to be a network appliance, needing to break out a console cable for a minor point-release is pretty sad...

bennyc · May 9, 2017, 10:29 AM

It's not all bad news. Updated 3 APU1's over the last 3 days, without one issue.
Next on the list is a 4860 HA setup…

khorton · May 9, 2017, 11:50 AM

My APU2C4 updated to 2.3.4 with no issues, not that this helps you much.

jimp · May 9, 2017, 12:06 PM

Without knowing what is on the console it's impossible to speculate as to cause. You could have a hardware failure that didn't present itself until reboot, in which case the update did nothing.

jimp · May 9, 2017, 12:07 PM

Locking this. If you encounter problems, please start new threads in appropriate areas of this forum.