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

    pfSense 2.4.4-RELEASE-p2 is now available!

    Scheduled Pinned Locked Moved Messages from the pfSense Team
    15 Posts 13 Posters 12.2k 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.
    • jimpJ
      jimp Rebel Alliance Developer Netgate
      last edited by jimp

      We have published pfSense 2.4.4-p2 today, coinciding with the release of the SG-1100. This is a small update primarily dealing with hardware support for the SG-1100 along with a few bug fixes.

      Enjoy!

      If you have a problem, please start a new thread in the appropriate category here on the forum rather than making a reply to this post.

      Before reporting problems, please read the linked blog post above as well as the Upgrade Guide and Upgrade Troubleshooting documents

      Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

      Need help fast? Netgate Global Support!

      Do not Chat/PM for help!

      1 Reply Last reply Reply Quote 8
      • M
        Making_sense_of_pfSense
        last edited by

        Is it ok to reply here about successful upgrades?

        I just successfully updated pfSense on a Qotom MiniPC from 2.4.4_1 to 2.4.4_2 via the web UI, no problem whatsoever.
        No warnings or error messages due to PHP or package updates. In fact, no packages needed updating at all.

        >>> 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.
        >>> Removing vital flag from lang/php72... 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 (5 candidates): ..... done
        Processing candidates (5 candidates): ..... done
        The following 5 package(s) will be affected (of 0 checked):
        
        Installed packages to be UPGRADED:
        	pfSense-rc: 2.4.4_1 -> 2.4.4_2 [pfSense-core]
        	pfSense-kernel-pfSense: 2.4.4_1 -> 2.4.4_2 [pfSense-core]
        	pfSense-default-config: 2.4.4_1 -> 2.4.4_2 [pfSense-core]
        	pfSense-base: 2.4.4_1 -> 2.4.4_2 [pfSense-core]
        	pfSense: 2.4.4_1 -> 2.4.4_2 [pfSense]
        
        Number of packages to be upgraded: 5
        
        51 MiB to be downloaded.
        [1/5] Fetching pfSense-rc-2.4.4_2.txz: .. done
        [2/5] Fetching pfSense-kernel-pfSense-2.4.4_2.txz: .......... done
        [3/5] Fetching pfSense-default-config-2.4.4_2.txz: . done
        [4/5] Fetching pfSense-base-2.4.4_2.txz: .......... done
        [5/5] Fetching pfSense-2.4.4_2.txz: . done
        Checking integrity... done (0 conflicting)
        >>> Upgrading pfSense-rc... 
        Checking integrity... done (0 conflicting)
        The following 1 package(s) will be affected (of 0 checked):
        
        Installed packages to be UPGRADED:
        	pfSense-rc: 2.4.4_1 -> 2.4.4_2 [pfSense-core]
        
        Number of packages to be upgraded: 1
        [1/1] Upgrading pfSense-rc from 2.4.4_1 to 2.4.4_2...
        [1/1] Extracting pfSense-rc-2.4.4_2: .... done
        >>> Upgrading pfSense kernel... 
        Checking integrity... done (0 conflicting)
        The following 1 package(s) will be affected (of 0 checked):
        
        Installed packages to be UPGRADED:
        	pfSense-kernel-pfSense: 2.4.4_1 -> 2.4.4_2 [pfSense-core]
        
        Number of packages to be upgraded: 1
        [1/1] Upgrading pfSense-kernel-pfSense from 2.4.4_1 to 2.4.4_2...
        [1/1] Extracting pfSense-kernel-pfSense-2.4.4_2: .......... done
        ===> Keeping a copy of current kernel in /boot/kernel.old
        >>> Removing unnecessary packages... done.
        Upgrade is complete.  Rebooting in 10 seconds.
        Success
        

        Running pfSense Community Edition 2.7.2 on a Qotom Mini PC.

        1 Reply Last reply Reply Quote 0
        • jimpJ
          jimp Rebel Alliance Developer Netgate
          last edited by

          Sure, that's fine!

          I prefer to keep the problems separate that way it's easier to help those with issues individually rather than getting all the conversations tangled up in a single large thread.

          Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

          Need help fast? Netgate Global Support!

          Do not Chat/PM for help!

          1 Reply Last reply Reply Quote 1
          • A
            ataru75
            last edited by

            Hi, i've lost swap file after update to 2.4.4_2

            GrimsonG 1 Reply Last reply Reply Quote 0
            • GrimsonG
              Grimson Banned @ataru75
              last edited by

              @ataru75 said in pfSense 2.4.4-RELEASE-p2 is now available!:

              Hi, i've lost swap file after update to 2.4.4_2

              And you can't read:
              @jimp said in pfSense 2.4.4-RELEASE-p2 is now available!:

              If you have a problem, please start a new thread in the appropriate category here on the forum rather than making a reply to this post.

              A 1 Reply Last reply Reply Quote 0
              • A
                ataru75 @Grimson
                last edited by

                @grimson said in pfSense 2.4.4-RELEASE-p2 is now available!:

                t

                sorry

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

                  Successful upgrade here from 2.4.4_1 to 2.4.4_2. This is on a native ZFS install running a Celeron J3455 and an Intel I340-T4. No errors and the system came up clean afterwards. Thanks for the bugfix release!

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

                    Successful upgrade on Netgate SG-3100.

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

                      Successful upgrade here from 2.4.4 to 2.4.4_2 on a Netgate SG-88601U. Did it remote (after a backup), and it took less than 10 minutes.

                      Jeff

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

                        Updated to 2.4.4_2 worked perfect. Ruuning on a i7-7500u. Took about 2 minutes.

                        fireodoF 1 Reply Last reply Reply Quote 0
                        • fireodoF
                          fireodo @musicwizard
                          last edited by

                          Here too: 2.4.4-p1 -> 2.4.4-p2 on a APU2C0 without problems!

                          Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
                          SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
                          pfsense 2.8.0 CE
                          Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

                          1 Reply Last reply Reply Quote 0
                          • XentrkX
                            Xentrk
                            last edited by

                            Update to 2.4.4_2 was successful on Intel i5. Took around 2 minutes.

                            pfSense 2.4.4_2 | Intel i5-3450 @ 3.10GHz  | AES-NI enabled |  pfBlockerNG | Snort
                            Blog Site: https://x3mtek.com || GitHub: https://github.com/Xentrk

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

                              upgraded from 2.4.4 to 2.4.4_2 on Intel Celeron J3455 with no problems, removed installed packages first then upgraded. after upgrade completed I reinstalled the packages and all is good. probably < 4 minutes with the package re-installs. Thank you Devs!

                              1 Reply Last reply Reply Quote 0
                              • J
                                Josef
                                last edited by

                                One of the resolved bugs - Bug #9178
                                Fixes or introduces the population of the 'Calling-Station-ID' attribute.
                                But it seems that the attribute is populated with the listening address and port of the OpenVPN server.
                                And the Called-Station-ID attribute is populated with the MAC address and hostname of the OpenVPN server.

                                In my opinion, the calling-station-id should be populated with the IP address of the connecting client because this is the caller that is "calling" into the service,
                                And the Called-station-id should be the IP address of the OpenVPN server because that is the address of service that has been "called".

                                So there is still no reference to the IP address and therefore the location of the connecting client.

                                Most Radius servers and 2FA systems use the calling-station-id to assess the location of the connecting client to help make a decision of whether to allow, deny or to further challenge the user.
                                Most commercial remote access products I have used work in this way. And I'm pretty sure the OpenVPN Access Server also populates the calling-station-id with the client IP address.

                                This seems backward to me.
                                I cannot imagine any scenario where the MAC address of the OpenVPN server will be of any relevance to the Radius server....

                                KOMK 1 Reply Last reply Reply Quote 1
                                • KOMK
                                  KOM @Josef
                                  last edited by

                                  @josef "If you have a problem, please start a new thread in the appropriate category here on the forum rather than making a reply to this post."

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