Version 2.3.4 is available.

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)

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.

NOYB

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

Finger79

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

Jailer

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

damir

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.

JasonAU

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

empbilly

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
}

empbilly

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

NOYB

@Jailer:

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

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.

dorap

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

biggsy

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.

k625

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-p16

The 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

doktornotor

Already discussed here: https://forum.pfsense.org/index.php?topic=129998.0

k625

I did everything as well in https://forum.pfsense.org/index.php?topic=129998.0 with the same result that is unsuccessfully.

Thx

doktornotor

Yeah, I'm pointing out that there's an already existing thread about the issue, no need to duplicate it.

M3PH

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 >:( ::)

Sealr0x

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.