Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Version 2.3.4 is available.

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    69 Posts 35 Posters 19.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K
      kpa
      last edited by

      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.

      1 Reply Last reply Reply Quote 0
      • D
        dorap
        last edited by

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

        1 Reply Last reply Reply Quote 0
        • B
          biggsy
          last edited by

          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.

          1 Reply Last reply Reply Quote 0
          • K
            k625
            last edited by

            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

            1 Reply Last reply Reply Quote 0
            • D
              doktornotor Banned
              last edited by

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

              1 Reply Last reply Reply Quote 0
              • K
                k625
                last edited by

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

                Thx

                1 Reply Last reply Reply Quote 0
                • D
                  doktornotor Banned
                  last edited by

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

                  1 Reply Last reply Reply Quote 0
                  • M
                    M3PH
                    last edited by

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

                    1 Reply Last reply Reply Quote 0
                    • S
                      Sealr0x
                      last edited by

                      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.

                      1 Reply Last reply Reply Quote 0
                      • D
                        dread
                        last edited by

                        Hi,

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

                        I had no problems, thanks for developers!

                        1 Reply Last reply Reply Quote 0
                        • C
                          Crispix
                          last edited by

                          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.

                          1 Reply Last reply Reply Quote 0
                          • C
                            colinstu
                            last edited by

                            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?

                            1 Reply Last reply Reply Quote 0
                            • N
                              NOYB
                              last edited by

                              @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

                              1 Reply Last reply Reply Quote 0
                              • N
                                NOYB
                                last edited by

                                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

                                1 Reply Last reply Reply Quote 0
                                • A
                                  apara
                                  last edited by

                                  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.

                                  1 Reply Last reply Reply Quote 0
                                  • P
                                    pvoigt
                                    last edited by

                                    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.

                                    1 Reply Last reply Reply Quote 0
                                    • L
                                      lalamper
                                      last edited by

                                      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?

                                      1 Reply Last reply Reply Quote 0
                                      • B
                                        bfeitell
                                        last edited by

                                        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. :-[

                                        1 Reply Last reply Reply Quote 0
                                        • L
                                          lalamper
                                          last edited by

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

                                          1 Reply Last reply Reply Quote 0
                                          • P
                                            pppfsense
                                            last edited by

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

                                            Good job pfSense Team!

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.