@stephenw10 [24.11-RELEASE][admin@gateway.nlfunhouse.com]/root: pfSense-upgrade -d >>> Updating repositories metadata... Updating pfSense-core repository catalogue... Fetching meta.conf: . done Fetching data.pkg: . done Processing entries: . done pfSense-core repository update completed. 5 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: . done Fetching data.pkg: .......... done Processing entries: Processing entries............. done pfSense repository update completed. 734 packages processed. All repositories are up to date. The following 75 package(s) will be affected (of 0 checked): New packages to be INSTALLED: brotli: 1.1.0,1 [pfSense] if_pppoe-kmod: 25.07.1.1500029 [pfSense] Installed packages to be UPGRADED: 7-zip: 24.08 -> 24.09 [pfSense] bind-tools: 9.20.2 -> 9.20.6 [pfSense] boost-libs: 1.85.0 -> 1.86.0 [pfSense] bwi-firmware-kmod: 3.130.20 -> 3.130.20.1500029 [pfSense] ca_root_nss: 3.104 -> 3.104_1 [pfSense] cpu-microcode-amd: 20240810 -> 20241121 [pfSense] cpu-microcode-intel: 20240910 -> 20250211 [pfSense] curl: 8.10.1 -> 8.11.0_1 [pfSense] dhcpcd: 10.1.0 -> 10.2.0 [pfSense] dnsmasq: 2.90_2,1 -> 2.90_4,1 [pfSense] expat: 2.6.3 -> 2.7.1 [pfSense] glib: 2.80.5,2 -> 2.80.5_1,2 [pfSense] iperf3: 3.17.1 -> 3.18 [pfSense] kea: 2.6.1_1 -> 2.6.2 [pfSense] libnghttp2: 1.63.0 -> 1.64.0 [pfSense] libpfctl: 0.13 -> 0.15 [pfSense] libssh2: 1.11.0_1,3 -> 1.11.1,3 [pfSense] libuv: 1.49.1 -> 1.49.2 [pfSense] luajit-openresty: 2.1.20240815 -> 2.1.20241104 [pfSense] miniupnpd: 2.3.7,1 -> 2.3.7_1,1 [pfSense] nginx: 1.26.2_6,3 -> 1.26.3,3 [pfSense] ntp: 4.2.8p18_1 -> 4.2.8p18_5 [pfSense] openldap26-client: 2.6.8 -> 2.6.9 [pfSense] opensc: 0.25.1 -> 0.26.0 [pfSense] openvpn: 2.6.12 -> 2.6.14 [pfSense] pfSense: 24.11 -> 25.07.1 [pfSense] pfSense-base: 24.11 -> 25.07.1 [pfSense-core] pfSense-boot: 24.11 -> 25.07.1 [pfSense-core] pfSense-composer-deps: 0.1 -> 0.3 [pfSense] pfSense-default-config: 24.11 -> 25.07.1 [pfSense] pfSense-kernel-pfSense: 24.11 -> 25.07.1 [pfSense-core] pfSense-repo: 24.11 -> 25.07.1 [pfSense] pftop: 0.10_1 -> 0.13 [pfSense] php83: 8.3.12 -> 8.3.19 [pfSense] php83-bcmath: 8.3.12 -> 8.3.19 [pfSense] php83-bz2: 8.3.12 -> 8.3.19 [pfSense] php83-ctype: 8.3.12 -> 8.3.19 [pfSense] php83-curl: 8.3.12 -> 8.3.19 [pfSense] php83-dom: 8.3.12 -> 8.3.19 [pfSense] php83-filter: 8.3.12 -> 8.3.19 [pfSense] php83-gettext: 8.3.12 -> 8.3.19 [pfSense] php83-gmp: 8.3.12 -> 8.3.19 [pfSense] php83-intl: 8.3.12 -> 8.3.19 [pfSense] php83-ldap: 8.3.12 -> 8.3.19 [pfSense] php83-mbstring: 8.3.12 -> 8.3.19 [pfSense] php83-opcache: 8.3.12 -> 8.3.19 [pfSense] php83-pcntl: 8.3.12 -> 8.3.19 [pfSense] php83-pdo: 8.3.12 -> 8.3.19 [pfSense] php83-pdo_sqlite: 8.3.12 -> 8.3.19 [pfSense] php83-pfSense-module: 0.99 -> 0.105 [pfSense] php83-posix: 8.3.12 -> 8.3.19 [pfSense] php83-readline: 8.3.12 -> 8.3.19 [pfSense] php83-session: 8.3.12 -> 8.3.19 [pfSense] php83-shmop: 8.3.12 -> 8.3.19 [pfSense] php83-simplexml: 8.3.12 -> 8.3.19 [pfSense] php83-sockets: 8.3.12 -> 8.3.19 [pfSense] php83-sqlite3: 8.3.12 -> 8.3.19 [pfSense] php83-sysvmsg: 8.3.12 -> 8.3.19 [pfSense] php83-sysvsem: 8.3.12 -> 8.3.19 [pfSense] php83-sysvshm: 8.3.12 -> 8.3.19 [pfSense] php83-tokenizer: 8.3.12 -> 8.3.19 [pfSense] php83-xml: 8.3.12 -> 8.3.19 [pfSense] php83-xmlreader: 8.3.12 -> 8.3.19 [pfSense] php83-xmlwriter: 8.3.12 -> 8.3.19 [pfSense] php83-zlib: 8.3.12 -> 8.3.19 [pfSense] protobuf: 28.2,1 -> 28.3,1 [pfSense] protobuf-c: 1.4.1_6 -> 1.4.1_7 [pfSense] py311-libzfs: 1.1.2023020700_2 -> 1.1.2023020700_3 [pfSense] py311-packaging: 24.1 -> 24.2 [pfSense] python311: 3.11.10 -> 3.11.11 [pfSense] radvd: 2.19_4 -> 2.20 [pfSense] unbound: 1.22.0 -> 1.23.0 [pfSense] zip: 3.0_2 -> 3.0_3 [pfSense] Number of packages to be installed: 2 Number of packages to be upgraded: 73 The operation will free 19 MiB. 318 MiB to be downloaded. **** WARNING **** Reboot will be required!! Proceed with upgrade? (y/N) y >>> Renaming current boot environment from default to default_20250828064458...done. >>> Cloning current boot environment default_20250828064458...done. >>> Removing vital flag from php83... >>> Downloading Netgate Nexus... The following packages will be fetched: New packages to be FETCHED: pfSense-pkg-Nexus: 25.07.1_1 (43 MiB: 100.00% of the 43 MiB to download) Number of packages to be fetched: 1 The process will require 43 MiB more space. 43 MiB to be downloaded. Fetching pfSense-pkg-Nexus-25.07.1_1.pkg: .......... done >>> Upgrading packages in cloned boot environment default... 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 (73 candidates): .......... done Processing candidates (73 candidates): .......... done The following 75 package(s) will be affected (of 0 checked): New packages to be INSTALLED: brotli: 1.1.0,1 [pfSense] if_pppoe-kmod: 25.07.1.1500029 [pfSense] Installed packages to be UPGRADED: 7-zip: 24.08 -> 24.09 [pfSense] bind-tools: 9.20.2 -> 9.20.6 [pfSense] boost-libs: 1.85.0 -> 1.86.0 [pfSense] bwi-firmware-kmod: 3.130.20 -> 3.130.20.1500029 [pfSense] ca_root_nss: 3.104 -> 3.104_1 [pfSense] cpu-microcode-amd: 20240810 -> 20241121 [pfSense] cpu-microcode-intel: 20240910 -> 20250211 [pfSense] curl: 8.10.1 -> 8.11.0_1 [pfSense] dhcpcd: 10.1.0 -> 10.2.0 [pfSense] dnsmasq: 2.90_2,1 -> 2.90_4,1 [pfSense] expat: 2.6.3 -> 2.7.1 [pfSense] glib: 2.80.5,2 -> 2.80.5_1,2 [pfSense] iperf3: 3.17.1 -> 3.18 [pfSense] kea: 2.6.1_1 -> 2.6.2 [pfSense] libnghttp2: 1.63.0 -> 1.64.0 [pfSense] libpfctl: 0.13 -> 0.15 [pfSense] libssh2: 1.11.0_1,3 -> 1.11.1,3 [pfSense] libuv: 1.49.1 -> 1.49.2 [pfSense] luajit-openresty: 2.1.20240815 -> 2.1.20241104 [pfSense] miniupnpd: 2.3.7,1 -> 2.3.7_1,1 [pfSense] nginx: 1.26.2_6,3 -> 1.26.3,3 [pfSense] ntp: 4.2.8p18_1 -> 4.2.8p18_5 [pfSense] openldap26-client: 2.6.8 -> 2.6.9 [pfSense] opensc: 0.25.1 -> 0.26.0 [pfSense] openvpn: 2.6.12 -> 2.6.14 [pfSense] pfSense: 24.11 -> 25.07.1 [pfSense] pfSense-base: 24.11 -> 25.07.1 [pfSense-core] pfSense-boot: 24.11 -> 25.07.1 [pfSense-core] pfSense-composer-deps: 0.1 -> 0.3 [pfSense] pfSense-default-config: 24.11 -> 25.07.1 [pfSense] pfSense-kernel-pfSense: 24.11 -> 25.07.1 [pfSense-core] pfSense-repo: 24.11 -> 25.07.1 [pfSense] pftop: 0.10_1 -> 0.13 [pfSense] php83: 8.3.12 -> 8.3.19 [pfSense] php83-bcmath: 8.3.12 -> 8.3.19 [pfSense] php83-bz2: 8.3.12 -> 8.3.19 [pfSense] php83-ctype: 8.3.12 -> 8.3.19 [pfSense] php83-curl: 8.3.12 -> 8.3.19 [pfSense] php83-dom: 8.3.12 -> 8.3.19 [pfSense] php83-filter: 8.3.12 -> 8.3.19 [pfSense] php83-gettext: 8.3.12 -> 8.3.19 [pfSense] php83-gmp: 8.3.12 -> 8.3.19 [pfSense] php83-intl: 8.3.12 -> 8.3.19 [pfSense] php83-ldap: 8.3.12 -> 8.3.19 [pfSense] php83-mbstring: 8.3.12 -> 8.3.19 [pfSense] php83-opcache: 8.3.12 -> 8.3.19 [pfSense] php83-pcntl: 8.3.12 -> 8.3.19 [pfSense] php83-pdo: 8.3.12 -> 8.3.19 [pfSense] php83-pdo_sqlite: 8.3.12 -> 8.3.19 [pfSense] php83-pfSense-module: 0.99 -> 0.105 [pfSense] php83-posix: 8.3.12 -> 8.3.19 [pfSense] php83-readline: 8.3.12 -> 8.3.19 [pfSense] php83-session: 8.3.12 -> 8.3.19 [pfSense] php83-shmop: 8.3.12 -> 8.3.19 [pfSense] php83-simplexml: 8.3.12 -> 8.3.19 [pfSense] php83-sockets: 8.3.12 -> 8.3.19 [pfSense] php83-sqlite3: 8.3.12 -> 8.3.19 [pfSense] php83-sysvmsg: 8.3.12 -> 8.3.19 [pfSense] php83-sysvsem: 8.3.12 -> 8.3.19 [pfSense] php83-sysvshm: 8.3.12 -> 8.3.19 [pfSense] php83-tokenizer: 8.3.12 -> 8.3.19 [pfSense] php83-xml: 8.3.12 -> 8.3.19 [pfSense] php83-xmlreader: 8.3.12 -> 8.3.19 [pfSense] php83-xmlwriter: 8.3.12 -> 8.3.19 [pfSense] php83-zlib: 8.3.12 -> 8.3.19 [pfSense] protobuf: 28.2,1 -> 28.3,1 [pfSense] protobuf-c: 1.4.1_6 -> 1.4.1_7 [pfSense] py311-libzfs: 1.1.2023020700_2 -> 1.1.2023020700_3 [pfSense] py311-packaging: 24.1 -> 24.2 [pfSense] python311: 3.11.10 -> 3.11.11 [pfSense] radvd: 2.19_4 -> 2.20 [pfSense] unbound: 1.22.0 -> 1.23.0 [pfSense] zip: 3.0_2 -> 3.0_3 [pfSense] Number of packages to be installed: 2 Number of packages to be upgraded: 73 The operation will free 19 MiB. 318 MiB to be downloaded. [1/75] Fetching unbound-1.23.0.pkg: .......... done [2/75] Fetching nginx-1.26.3,3.pkg: .......... done [3/75] Fetching pfSense-base-25.07.1.pkg: .......... done [4/75] Fetching php83-filter-8.3.19.pkg: .. done [5/75] Fetching php83-pdo_sqlite-8.3.19.pkg: . done [6/75] Fetching php83-curl-8.3.19.pkg: ... done [7/75] Fetching libuv-1.49.2.pkg: .......... done [8/75] Fetching boost-libs-1.86.0.pkg: .......... done [9/75] Fetching php83-gmp-8.3.19.pkg: .. done [10/75] Fetching cpu-microcode-amd-20241121.pkg: .......... done [11/75] Fetching php83-ldap-8.3.19.pkg: . done [12/75] Fetching openvpn-2.6.14.pkg: .......... done [13/75] Fetching libnghttp2-1.64.0.pkg: ........ done [14/75] Fetching php83-xmlwriter-8.3.19.pkg: . done [15/75] Fetching pfSense-default-config-25.07.1.pkg: . done [16/75] Fetching dnsmasq-2.90_4,1.pkg: .......... done [17/75] Fetching bind-tools-9.20.6.pkg: .......... done [18/75] Fetching py311-packaging-24.2.pkg: .......... done [19/75] Fetching php83-simplexml-8.3.19.pkg: .. done [20/75] Fetching php83-pdo-8.3.19.pkg: .... done [21/75] Fetching pfSense-25.07.1.pkg: .......... done [22/75] Fetching radvd-2.20.pkg: .... done [23/75] Fetching ntp-4.2.8p18_5.pkg: .......... done [24/75] Fetching php83-opcache-8.3.19.pkg: .......... done [25/75] Fetching php83-bz2-8.3.19.pkg: . done [26/75] Fetching php83-sockets-8.3.19.pkg: ... done [27/75] Fetching if_pppoe-kmod-25.07.1.1500029.pkg: ... done [28/75] Fetching php83-pfSense-module-0.105.pkg: ... done [29/75] Fetching opensc-0.26.0.pkg: .......... done [30/75] Fetching protobuf-c-1.4.1_7.pkg: ....... done [31/75] Fetching php83-sysvshm-8.3.19.pkg: . done [32/75] Fetching php83-posix-8.3.19.pkg: . done [33/75] Fetching php83-pcntl-8.3.19.pkg: . done [34/75] Fetching pfSense-boot-25.07.1.pkg: .......... done [35/75] Fetching php83-xmlreader-8.3.19.pkg: . done [36/75] Fetching php83-readline-8.3.19.pkg: . done [37/75] Fetching miniupnpd-2.3.7_1,1.pkg: ..... done [38/75] Fetching ca_root_nss-3.104_1.pkg: .......... done [39/75] Fetching php83-sqlite3-8.3.19.pkg: .. done [40/75] Fetching python311-3.11.11.pkg: .......... done [41/75] Fetching iperf3-3.18.pkg: ...... done [42/75] Fetching pfSense-repo-25.07.1.pkg: . done [43/75] Fetching php83-session-8.3.19.pkg: .. done [44/75] Fetching kea-2.6.2.pkg: .......... done [45/75] Fetching dhcpcd-10.2.0.pkg: .......... done [46/75] Fetching php83-mbstring-8.3.19.pkg: .......... done [47/75] Fetching pfSense-composer-deps-0.3.pkg: .......... done [48/75] Fetching php83-gettext-8.3.19.pkg: . done [49/75] Fetching php83-zlib-8.3.19.pkg: .. done [50/75] Fetching pfSense-kernel-pfSense-25.07.1.pkg: .......... done [51/75] Fetching php83-ctype-8.3.19.pkg: . done [52/75] Fetching brotli-1.1.0,1.pkg: .......... done [53/75] Fetching curl-8.11.0_1.pkg: .......... done [54/75] Fetching php83-tokenizer-8.3.19.pkg: . done [55/75] Fetching php83-8.3.19.pkg: .......... done [56/75] Fetching bwi-firmware-kmod-3.130.20.1500029.pkg: ... done [57/75] Fetching libpfctl-0.15.pkg: ... done [58/75] Fetching php83-xml-8.3.19.pkg: . done [59/75] Fetching php83-dom-8.3.19.pkg: ..... done [60/75] Fetching zip-3.0_3.pkg: .......... done [61/75] Fetching php83-intl-8.3.19.pkg: ....... done [62/75] Fetching php83-sysvmsg-8.3.19.pkg: . done [63/75] Fetching openldap26-client-2.6.9.pkg: ........ done [64/75] Fetching protobuf-28.3,1.pkg: .......... done [65/75] Fetching glib-2.80.5_1,2.pkg: .......... done [66/75] Fetching luajit-openresty-2.1.20241104.pkg: .......... done [67/75] Fetching php83-shmop-8.3.19.pkg: . done [68/75] Fetching cpu-microcode-intel-20250211.pkg: .......... done [69/75] Fetching libssh2-1.11.1,3.pkg: .......... done [70/75] Fetching php83-bcmath-8.3.19.pkg: .. done [71/75] Fetching pftop-0.13.pkg: ..... done [72/75] Fetching php83-sysvsem-8.3.19.pkg: . done [73/75] Fetching expat-2.7.1.pkg: ....... done [74/75] Fetching py311-libzfs-1.1.2023020700_3.pkg: .......... done [75/75] Fetching 7-zip-24.09.pkg: .......... done Checking integrity... done (0 conflicting) [1/75] Upgrading python311 from 3.11.10 to 3.11.11... [1/75] Extracting python311-3.11.11: .......... done [2/75] Upgrading php83 from 8.3.12 to 8.3.19... [2/75] Extracting php83-8.3.19: .......... done [3/75] Upgrading py311-packaging from 24.1 to 24.2... [3/75] Extracting py311-packaging-24.2: .......... done [4/75] Upgrading php83-zlib from 8.3.12 to 8.3.19... [4/75] Extracting php83-zlib-8.3.19: ........ done [5/75] Upgrading php83-xml from 8.3.12 to 8.3.19... [5/75] Extracting php83-xml-8.3.19: ......... done [6/75] Upgrading expat from 2.6.3 to 2.7.1... [6/75] Extracting expat-2.7.1: .......... done [7/75] Upgrading libnghttp2 from 1.63.0 to 1.64.0... [7/75] Extracting libnghttp2-1.64.0: .......... done [8/75] Installing brotli-1.1.0,1... [8/75] Extracting brotli-1.1.0,1: .......... done [9/75] Upgrading glib from 2.80.5,2 to 2.80.5_1,2... [9/75] Extracting glib-2.80.5_1,2: .......... done [10/75] Upgrading luajit-openresty from 2.1.20240815 to 2.1.20241104... [10/75] Extracting luajit-openresty-2.1.20241104: .......... done [11/75] Upgrading libssh2 from 1.11.0_1,3 to 1.11.1,3... [11/75] Extracting libssh2-1.11.1,3: .......... done [12/75] Upgrading unbound from 1.22.0 to 1.23.0... ===> Creating groups Using existing group 'unbound' ===> Creating users Using existing user 'unbound' [12/75] Extracting unbound-1.23.0: .......... done [13/75] Upgrading curl from 8.10.1 to 8.11.0_1... [13/75] Extracting curl-8.11.0_1: .......... done [14/75] Upgrading protobuf from 28.2,1 to 28.3,1... [14/75] Extracting protobuf-28.3,1: .......... done [15/75] Upgrading php83-curl from 8.3.12 to 8.3.19... [15/75] Extracting php83-curl-8.3.19: .......... done [16/75] Upgrading libuv from 1.49.1 to 1.49.2... [16/75] Extracting libuv-1.49.2: .......... done [17/75] Upgrading boost-libs from 1.85.0 to 1.86.0... [17/75] Extracting boost-libs-1.86.0: .......... done [18/75] Upgrading cpu-microcode-amd from 20240810 to 20241121... [18/75] Extracting cpu-microcode-amd-20241121: ......... done [19/75] Upgrading php83-pdo from 8.3.12 to 8.3.19... [19/75] Extracting php83-pdo-8.3.19: .......... done [20/75] Upgrading protobuf-c from 1.4.1_6 to 1.4.1_7... [20/75] Extracting protobuf-c-1.4.1_7: .......... done [21/75] Upgrading libpfctl from 0.13 to 0.15... [21/75] Extracting libpfctl-0.15: ...... done [22/75] Upgrading php83-dom from 8.3.12 to 8.3.19... [22/75] Extracting php83-dom-8.3.19: .......... done [23/75] Upgrading openldap26-client from 2.6.8 to 2.6.9... [23/75] Extracting openldap26-client-2.6.9: .......... done [24/75] Upgrading cpu-microcode-intel from 20240910 to 20250211... [24/75] Extracting cpu-microcode-intel-20250211: .......... done [25/75] Upgrading php83-bcmath from 8.3.12 to 8.3.19... [25/75] Extracting php83-bcmath-8.3.19: .......... done [26/75] Upgrading nginx from 1.26.2_6,3 to 1.26.3,3... ===> Creating groups Using existing group 'www' ===> Creating users Using existing user 'www' [26/75] Extracting nginx-1.26.3,3: .......... done [27/75] Upgrading php83-filter from 8.3.12 to 8.3.19... [27/75] Extracting php83-filter-8.3.19: ......... done [28/75] Upgrading php83-pdo_sqlite from 8.3.12 to 8.3.19... [28/75] Extracting php83-pdo_sqlite-8.3.19: ......... done [29/75] Upgrading php83-gmp from 8.3.12 to 8.3.19... [29/75] Extracting php83-gmp-8.3.19: ......... done [30/75] Upgrading php83-ldap from 8.3.12 to 8.3.19... [30/75] Extracting php83-ldap-8.3.19: ........ done [31/75] Upgrading openvpn from 2.6.12 to 2.6.14... ===> Creating groups Using existing group 'openvpn' ===> Creating users Using existing user 'openvpn' [31/75] Extracting openvpn-2.6.14: .......... done [32/75] Upgrading php83-xmlwriter from 8.3.12 to 8.3.19... [32/75] Extracting php83-xmlwriter-8.3.19: ........ done [33/75] Upgrading dnsmasq from 2.90_2,1 to 2.90_4,1... [33/75] Extracting dnsmasq-2.90_4,1: .......... done [34/75] Upgrading bind-tools from 9.20.2 to 9.20.6... [34/75] Extracting bind-tools-9.20.6: .......... done [35/75] Upgrading php83-simplexml from 8.3.12 to 8.3.19... [35/75] Extracting php83-simplexml-8.3.19: ......... done [36/75] Upgrading radvd from 2.19_4 to 2.20... [36/75] Extracting radvd-2.20: .......... done [37/75] Upgrading ntp from 4.2.8p18_1 to 4.2.8p18_5... [37/75] Extracting ntp-4.2.8p18_5: .......... done [38/75] Upgrading php83-opcache from 8.3.12 to 8.3.19... [38/75] Extracting php83-opcache-8.3.19: .......... done [39/75] Upgrading php83-bz2 from 8.3.12 to 8.3.19... [39/75] Extracting php83-bz2-8.3.19: ........ done [40/75] Upgrading php83-sockets from 8.3.12 to 8.3.19... [40/75] Extracting php83-sockets-8.3.19: .......... done [41/75] Installing if_pppoe-kmod-25.07.1.1500029... [41/75] Extracting if_pppoe-kmod-25.07.1.1500029: .. done [42/75] Upgrading php83-pfSense-module from 0.99 to 0.105... [42/75] Extracting php83-pfSense-module-0.105: ....... done [43/75] Upgrading opensc from 0.25.1 to 0.26.0... [43/75] Extracting opensc-0.26.0: .......... done [44/75] Upgrading php83-sysvshm from 8.3.12 to 8.3.19... [44/75] Extracting php83-sysvshm-8.3.19: ........ done [45/75] Upgrading php83-posix from 8.3.12 to 8.3.19... [45/75] Extracting php83-posix-8.3.19: ........ done [46/75] Upgrading php83-pcntl from 8.3.12 to 8.3.19... [46/75] Extracting php83-pcntl-8.3.19: ......... done [47/75] Upgrading pfSense-boot from 24.11 to 25.07.1... [47/75] Extracting pfSense-boot-25.07.1: .......... done [48/75] Upgrading php83-xmlreader from 8.3.12 to 8.3.19... [48/75] Extracting php83-xmlreader-8.3.19: ........ done [49/75] Upgrading php83-readline from 8.3.12 to 8.3.19... [49/75] Extracting php83-readline-8.3.19: ......... done [50/75] Upgrading miniupnpd from 2.3.7,1 to 2.3.7_1,1... [50/75] Extracting miniupnpd-2.3.7_1,1: ....... done [51/75] Upgrading ca_root_nss from 3.104 to 3.104_1... [51/75] Extracting ca_root_nss-3.104_1: ....... done [52/75] Upgrading php83-sqlite3 from 8.3.12 to 8.3.19... [52/75] Extracting php83-sqlite3-8.3.19: ......... done [53/75] Upgrading pfSense-repo from 24.11 to 25.07.1... [53/75] Extracting pfSense-repo-25.07.1: .......... done [54/75] Upgrading php83-session from 8.3.12 to 8.3.19... [54/75] Extracting php83-session-8.3.19: .......... done [55/75] Upgrading kea from 2.6.1_1 to 2.6.2... [55/75] Extracting kea-2.6.2: .......... done [56/75] Upgrading dhcpcd from 10.1.0 to 10.2.0... [56/75] Extracting dhcpcd-10.2.0: .......... done [57/75] Upgrading php83-mbstring from 8.3.12 to 8.3.19... [57/75] Extracting php83-mbstring-8.3.19: .......... done [58/75] Upgrading pfSense-composer-deps from 0.1 to 0.3... [58/75] Extracting pfSense-composer-deps-0.3: .......... done [59/75] Upgrading php83-gettext from 8.3.12 to 8.3.19... [59/75] Extracting php83-gettext-8.3.19: ........ done [60/75] Upgrading php83-ctype from 8.3.12 to 8.3.19... [60/75] Extracting php83-ctype-8.3.19: ........ done [61/75] Upgrading php83-tokenizer from 8.3.12 to 8.3.19... [61/75] Extracting php83-tokenizer-8.3.19: ......... done [62/75] Upgrading bwi-firmware-kmod from 3.130.20 to 3.130.20.1500029... [62/75] Extracting bwi-firmware-kmod-3.130.20.1500029: . done [63/75] Upgrading php83-intl from 8.3.12 to 8.3.19... [63/75] Extracting php83-intl-8.3.19: .......... done [64/75] Upgrading php83-sysvmsg from 8.3.12 to 8.3.19... [64/75] Extracting php83-sysvmsg-8.3.19: ........ done [65/75] Upgrading php83-shmop from 8.3.12 to 8.3.19... [65/75] Extracting php83-shmop-8.3.19: ........ done [66/75] Upgrading pftop from 0.10_1 to 0.13... [66/75] Extracting pftop-0.13: ..... done [67/75] Upgrading php83-sysvsem from 8.3.12 to 8.3.19... [67/75] Extracting php83-sysvsem-8.3.19: ........ done [68/75] Upgrading py311-libzfs from 1.1.2023020700_2 to 1.1.2023020700_3... [68/75] Extracting py311-libzfs-1.1.2023020700_3: ........ done [69/75] Upgrading pfSense-base from 24.11 to 25.07.1... [69/75] Extracting pfSense-base-25.07.1: ... done ===> Keeping a copy of current version mtree ===> Removing schg flag from base files ===> Extracting new base tarball ===> Removing static obsoleted files [70/75] Upgrading pfSense-default-config from 24.11 to 25.07.1... [70/75] Extracting pfSense-default-config-25.07.1: .... done [71/75] Upgrading pfSense from 24.11 to 25.07.1... [71/75] Extracting pfSense-25.07.1: .......... done [72/75] Upgrading iperf3 from 3.17.1 to 3.18... [72/75] Extracting iperf3-3.18: .......... done [73/75] Upgrading pfSense-kernel-pfSense from 24.11 to 25.07.1... [73/75] Extracting pfSense-kernel-pfSense-25.07.1: .......... done [74/75] Upgrading zip from 3.0_2 to 3.0_3... [74/75] Extracting zip-3.0_3: .......... done [75/75] Upgrading 7-zip from 24.08 to 24.09... [75/75] Extracting 7-zip-24.09: ........ done ==> Running trigger: glib-schemas.ucl Compiling glib schemas No schema files found: doing nothing. ==> Running trigger: gio-modules.ucl Generating GIO modules cache ===== Message from openvpn-2.6.14: -- Note that OpenVPN now configures a separate user and group "openvpn", which should be used instead of the NFS user "nobody" when an unprivileged user account is desired. It is advisable to review existing configuration files and to consider adding/changing user openvpn and group openvpn. ===== Message from dnsmasq-2.90_4,1: -- To enable dnsmasq, edit /usr/local/etc/dnsmasq.conf and set dnsmasq_enable="YES" in /etc/rc.conf[.local] Further options and actions are documented inside /usr/local/etc/rc.d/dnsmasq SECURITY RECOMMENDATION ~~~~~~~~~~~~~~~~~~~~~~~ It is recommended to enable the wpad-related options at the end of the configuration file (you may need to copy them from the example file to yours) to fix CERT Vulnerability VU#598349. You may need to manually remove /usr/local/etc/kea/kea-dhcp4.conf if it is no longer needed. You may need to manually remove /usr/local/etc/kea/kea-dhcp6.conf if it is no longer needed. ===== Message from py311-libzfs-1.1.2023020700_3: -- ===> NOTICE: The py311-libzfs port currently does not have a maintainer. As a result, it is more likely to have unresolved issues, not be up-to-date, or even be removed in the future. To volunteer to maintain this port, please create an issue at: https://bugs.freebsd.org/bugzilla More information about port maintainership is available at: https://docs.freebsd.org/en/articles/contributing/#ports-contributing ===== Message from zip-3.0_3: -- ===> NOTICE: The zip port currently does not have a maintainer. As a result, it is more likely to have unresolved issues, not be up-to-date, or even be removed in the future. To volunteer to maintain this port, please create an issue at: https://bugs.freebsd.org/bugzilla More information about port maintainership is available at: https://docs.freebsd.org/en/articles/contributing/#ports-contributing >>> Installing Netgate Nexus... Checking integrity... done (1 conflicting) - pfSense-pkg-Nexus-25.07.1_1 [pfSense] conflicts with pfSense-mim-24.11_1 [installed] on /usr/local/bin/controller-ctl Checking integrity... done (0 conflicting) The following 2 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: pfSense-mim: 24.11_1 New packages to be INSTALLED: pfSense-pkg-Nexus: 25.07.1_1 [pfSense] Number of packages to be removed: 1 Number of packages to be installed: 1 The process will require 10 MiB more space. [24.11-RELEASE][admin@gateway.nlfunhouse.com]/root: Error in GUI: pkg: "out of space" returned error code 3 @ 2025-08-28 06:47:39 I saw in another topic that a NVME in read-only mode was the cultprit, from what I can see my NVME is passing the test [24.11-RELEASE][admin@gateway.nlfunhouse.com]/root: smartctl -a /dev/nvme0 smartctl 7.4 2023-08-01 r5530 [FreeBSD 15.0-CURRENT amd64] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: BC711 NVMe SK hynix 256GB Serial Number: FNACN41981290C53Q Firmware Version: 41002131 PCI Vendor/Subsystem ID: 0x1c5c IEEE OUI Identifier: 0xace42e Controller ID: 1 NVMe Version: 1.3 Number of Namespaces: 1 Namespace 1 Size/Capacity: 256,060,514,304 [256 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64: ffffff ffffffffff Local Time is: Thu Aug 28 06:51:30 2025 CEST Firmware Updates (0x16): 3 Slots, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg Maximum Data Transfer Size: 64 Pages Warning Comp. Temp. Threshold: 83 Celsius Critical Comp. Temp. Threshold: 85 Celsius Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 6.3000W - - 0 0 0 0 5 5 1 + 2.4000W - - 1 1 1 1 30 30 2 + 1.9000W - - 2 2 2 2 100 100 3 - 0.0500W - - 3 3 3 3 1000 1000 4 - 0.0040W - - 3 3 3 3 1000 9000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 0 1 - 4096 0 0 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature: 39 Celsius Available Spare: 100% Available Spare Threshold: 50% Percentage Used: 0% Data Units Read: 269,896 [138 GB] Data Units Written: 21,066,145 [10.7 TB] Host Read Commands: 3,338,190 Host Write Commands: 933,789,908 Controller Busy Time: 336 Power Cycles: 67 Power On Hours: 10,304 Unsafe Shutdowns: 51 Media and Data Integrity Errors: 0 Error Information Log Entries: 0 Warning Comp. Temperature Time: 0 Critical Comp. Temperature Time: 0 Temperature Sensor 1: 39 Celsius Temperature Sensor 2: 45 Celsius Error Information (NVMe Log 0x01, 16 of 256 entries) No Errors Logged Self-test Log (NVMe Log 0x06) Self-test status: No self-test in progress Num Test_Description Status Power_on_Hours Failing_LBA NSID Seg SCT Code 0 Short Aborted: Controller Reset 5 - - - - - 1 Short Aborted: Self-test command 4 - - - - - 2 Short Aborted: Self-test command 4 - - - - - 3 Short Aborted: Self-test command 3 - - - - - 4 Short Completed without error 0 - - - - -

@stephenw10 Thanks, since pfS runs in KVM, I can restore an old backup in a few seconds if there are problems.

Yes, it probably failed the boot verification check after booting into the upgraded BE. Which means it's not a drive space issue. But you should see an alert on the dashboard if it fails to boot check and rolls back. You would need to see the boot log from the new BE to see where it's failing.

It appears to hang immediately after loading the kernel at the UEFI console? Try booting legacy to confirm it's the same issue.

@stephenw10 honestly I am not too sure at this point. First day after the fix, I've been randomly losing LTE links for shorts periods. Since last 2 days it's been all right, it would have been such a coincidence that the provider had problems at the same time. Though not impossible... Last night I lost IPSEC tunnel (one site only) for maybe ±30mins and then it came back. No indication of LTE down/gateway down during this time. I've adjusted the log level for IPSEC so I can go back when it happened (level was too high). We did NOT downgrade the units for now. We had NO init string using 2.7.2 and it was working fine!

@WB3FFV said in Update or Fresh install of 25.07 causes HP ProLiant DL20 Gen9 to Reboot after PFSense Menu: @stephenw10 The million dollar question is, should load modern servers in BIOS or UEFI mode? I assumed now days UEFI was an improvement and the preferred method, but maybe not.. There is no million dollar answer. Recently I run into issues due to a bug in freebsd that would only affect NON uefi installs. Using uefi, all worked fine. It was fixed later on. Now it seems you are facing the opposite. Apart from that, uefi is probably the only way to go, longterm.

@Unoptanio per the upgrade guide https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide-prepare.html#packages “The safest practice is to remove all packages before upgrading to a new release. The upgrade process will handle packages automatically, but packages are frequently a source of problems. To ensure a smooth upgrade, note the installed packages, remove them, perform the upgrade, and then reinstall when the upgrade is complete.” No it’s not required. pfSense will upgrade packages. Yes the package setting remain in the configuration file by default.

Vendors have firmware bugs similar to this quite often, and usually you'd see the OS failing suddenly for no good reason. Falling back to PCI IO access for the config space will probably only allowing boot-through, but any time something allocates memory into that region, it won't be going to DRAM... leading to data corruption. If you enable above 4GB decoding (and it successfully boots), there could be a change to the ACPI tables that the firmware generates. In any case, we'll need to find a way to let FreeBSD know not to use that memory region for allocations.

@JonnyQuest im on 2.8.0 and i also had no problems Shell Output - pkg update -f Updating ntop repository catalogue... Fetching meta.conf: . done Fetching data.pkg: . done Processing entries: . done ntop repository update completed. 6 packages processed. Updating pfSense-core repository catalogue... Fetching meta.conf: . done Fetching data.pkg: . done Processing entries: . done pfSense-core repository update completed. 4 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: . done Fetching data.pkg: ......... done Processing entries: .......... done pfSense repository update completed. 541 packages processed. All repositories are up to date.

@SteveITS I went back and retraced my steps, ONLY to realized that I had actually been attempting to restore an OPNsense config and NOT a pfSense config into pfSense 2.8.0... Today I had been running the same exercise (prep for switching from Cable to Fiber) in both... Hence False Alarm: pfSense 2.8.0 was "Correct", in fact it was NOT a pfSense config!!! Restoring Today's Initial Chrome config into pfSense 2.8.0 works as expected... Lawrence Houston

@m80s said in Update 2.7.2 to 2.8.0 Dynamic DNS not working with Cloudflare: @stephenw10 in my case I tried with 25.07.1: DuckDNS DeSec both with IPv4 and both failing. Yeah that's unexpected. Unless they are using a WAN with a gateway that shows as down. In which case you would be hitting the new behaviour requiring gateway monitoring be corrected.

Your root filesystem is down to 1.5G with only 345MB available. It is a space issue. Go to System> Boot Environments and remove any older snapshots you're no longer using. I usually recommend removing all but the currently running BE and one previous one. Then retry upgrading.

@dennypage Last night I upgraded the 2100 via the console with pfBlockerNG and Avahi packages left in place, and after 20 minutes or so it came back up and avahi appears to be working properly.

@stephenw10 Hi Stephen. That's why I posted -- the 25.07.1 update has been out for well over 24 hours and yet there was no upgrade available LED flashing. I upgraded last night so we'll see if it picks up when the next upgrade is available.

Ah, good and bad news then I guess. Thanks for following up. Yes, some SSDs will fail to a read-only state such that they appear to take changes but lose it at reboot. And that can be confusing!