>>> Setting vital flag on lang/php72... done. >>> Updating repositories metadata... done. 2.4.4_3 version of pfSense is available >>> Removing vital flag from lang/php72... done. >>> Locking package pfSense-pkg-Netgate_Coreboot_Upgrade... done. >>> Locking package pfSense-pkg-aws-wizard... done. >>> Locking package pfSense-pkg-ipsec-profile-wizard... done. >>> Upgrading necessary packages... Checking for upgrades (20 candidates): .......... done Processing candidates (20 candidates): ......... done Checking integrity... done (0 conflicting) The following 16 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: wpa_supplicant: 2.6_2 -> 2.8 [pfSense] unbound: 1.8.1 -> 1.9.1 [pfSense] sshguard: 2.2.0_4 -> 2.3.1 [pfSense] sqlite3: 3.24.0_1 -> 3.28.0 [pfSense] python27: 2.7.15 -> 2.7.16 [pfSense] pfSense-default-config-serial: 2.4.4_2 -> 2.4.4_3 [pfSense-core] pfSense-base: 2.4.4_2 -> 2.4.4_3 [pfSense-core] pfSense-Status_Monitoring: 1.7.6 -> 1.7.7 [pfSense] pfSense: 2.4.4_2 -> 2.4.4_3 [pfSense] ntp: 4.2.8p12 -> 4.2.8p13 [pfSense] nginx: 1.14.0_6,2 -> 1.14.1,2 [pfSense] libzmq4: 4.2.3 -> 4.3.1 [pfSense] hostapd: 2.6_2 -> 2.8 [pfSense] dhcpleases: 0.3_1 -> 0.3_2 [pfSense] devcpu-data: 1.19 -> 1.22 [pfSense] curl: 7.62.0 -> 7.64.0 [pfSense] Number of packages to be upgraded: 16 The process will require 4 MiB more space. [1/16] Upgrading python27 from 2.7.15 to 2.7.16... [1/16] Extracting python27-2.7.16: .......... done [2/16] Upgrading unbound from 1.8.1 to 1.9.1... ===> Creating groups. Using existing group 'unbound'. ===> Creating users Using existing user 'unbound'. [2/16] Extracting unbound-1.9.1: .......... done [3/16] Upgrading curl from 7.62.0 to 7.64.0... [3/16] Extracting curl-7.64.0: .......... done [4/16] Upgrading sqlite3 from 3.24.0_1 to 3.28.0... [4/16] Extracting sqlite3-3.28.0: .......... done [5/16] Upgrading libzmq4 from 4.2.3 to 4.3.1... [5/16] Extracting libzmq4-4.3.1: .......... done [6/16] Upgrading wpa_supplicant from 2.6_2 to 2.8... [6/16] Extracting wpa_supplicant-2.8: ....... done [7/16] Upgrading sshguard from 2.2.0_4 to 2.3.1... [7/16] Extracting sshguard-2.3.1: .......... done You may need to manually remove /usr/local/etc/sshguard.conf if it is no longer needed. [8/16] Upgrading pfSense-Status_Monitoring from 1.7.6 to 1.7.7... [8/16] Extracting pfSense-Status_Monitoring-1.7.7: ........ done [9/16] Upgrading ntp from 4.2.8p12 to 4.2.8p13... [9/16] Extracting ntp-4.2.8p13: .......... done [10/16] Upgrading nginx from 1.14.0_6,2 to 1.14.1,2... ===> Creating groups. Using existing group 'www'. ===> Creating users Using existing user 'www'. [10/16] Extracting nginx-1.14.1,2: .......... done [11/16] Upgrading hostapd from 2.6_2 to 2.8... [11/16] Extracting hostapd-2.8: ....... done [12/16] Upgrading dhcpleases from 0.3_1 to 0.3_2... [12/16] Extracting dhcpleases-0.3_2: .... done [13/16] Upgrading devcpu-data from 1.19 to 1.22... [13/16] Extracting devcpu-data-1.22: .......... done [14/16] Upgrading pfSense-default-config-serial from 2.4.4_2 to 2.4.4_3... [14/16] Extracting pfSense-default-config-serial-2.4.4_3: .. done [15/16] Upgrading pfSense-base from 2.4.4_2 to 2.4.4_3... [15/16] Extracting pfSense-base-2.4.4_3: .. done ===> Keeping a copy of current version mtree ===> Removing schg flag from base files ===> Extracting new base tarball ===> Removing static obsoleted files [16/16] Upgrading pfSense from 2.4.4_2 to 2.4.4_3... [16/16] Extracting pfSense-2.4.4_3: ..... done Message from python27-2.7.16: =========================================================================== Note that some standard Python modules are provided as separate ports as they require additional dependencies. They are available as: bsddb databases/py-bsddb gdbm databases/py-gdbm sqlite3 databases/py-sqlite3 tkinter x11-toolkits/py-tkinter =========================================================================== Message from wpa_supplicant-2.8: To use the ports version of WPA Supplicant instead of the base, add: wpa_supplicant_program="/usr/local/sbin/wpa_supplicant" to /etc/rc.conf Message from sshguard-2.3.1: To enable SSHGuard at startup, add the following line to your 'rc.conf': sshguard_enable="YES" Starting SSHGuard through syslogd(8) is discouraged and not supported. Configure SSHGuard by editing BACKEND in '/usr/local/etc/sshguard.conf'. See sshguard-setup(7) for instructions on setting up your firewall. Please note that a few rc script parameters have been renamed to better reflect the documentation: sshguard_safety_thresh -> sshguard_danger_thresh sshguard_pardon_min_interval -> sshguard_release_interval sshguard_prescribe_interval -> sshguard_reset_interval Message from ntp-4.2.8p13: Please add ntpd_program="/usr/local/sbin/ntpd" ntpdate_program="/usr/local/sbin/ntpdate" to your /etc/rc.conf or run sysrc ntpd_program="/usr/local/sbin/ntpd" sysrc ntpdate_program="/usr/local/sbin/ntpdate" to enable ntp from ports/packages instead of base ntp. Message from nginx-1.14.1,2: =================================================================== Recent version of the NGINX introduces dynamic modules support. In FreeBSD ports tree this feature was enabled by default with the DSO knob. Several vendor's and third-party modules have been converted to dynamic modules. Unset the DSO knob builds an NGINX without dynamic modules support. To load a module at runtime, include the new `load_module' directive in the main context, specifying the path to the shared object file for the module, enclosed in quotation marks. When you reload the configuration or restart NGINX, the module is loaded in. It is possible to specify a path relative to the source directory, or a full path, please see https://www.nginx.com/blog/dynamic-modules-nginx-1-9-11/ and http://nginx.org/en/docs/ngx_core_module.html#load_module for details. Default path for the NGINX dynamic modules is /usr/local/libexec/nginx. =================================================================== Message from hostapd-2.8: Add the following to /etc/rc.conf to use the ports version instead of the base version: hostapd_program="/usr/local/sbin/hostapd" Message from devcpu-data-1.22: Installing this port will allow host startup to update the CPU microcode on a FreeBSD system automatically. There are two methods for updating CPU microcode: the first methods loads and applies the update before the kernel begins booting, and the second method loads and applies updates using an rc script. The first method is preferred, but is currently only supported on Intel i386 and amd64 processors running FreeBSD 12.0. It is safe to enable both methods. The first method ensures that any CPU features introduced by a microcode update are visible to the kernel. In other words, the update is loaded before the kernel performs CPU feature detection. To enable updates using the first method, add the following lines to the system's /boot/loader.conf: cpu_microcode_load="YES" cpu_microcode_name="/boot/firmware/intel-ucode.bin" This method will not load the microcode update until the system is rebooted. To enable updates using the second method, add the following line to the system's /etc/rc.conf: microcode_update_enable="YES" Then, to ensure the update is applied, reboot the system or start the microcode update service via: # service microcode_update start If the CPU requires a microcode update, a console message such as the following will appear: Updating CPU Microcode... /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl0 from rev 0x17 to rev 0x22... done. /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl2 from rev 0x17 to rev 0x22... done. /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl4 from rev 0x17 to rev 0x22... done. /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl6 from rev 0x17 to rev 0x22... done. Done. >>> Setting vital flag on pfSense... done. >>> Unlocking package pfSense-pkg-Netgate_Coreboot_Upgrade... done. >>> Unlocking package pfSense-pkg-aws-wizard... done. >>> Unlocking package pfSense-pkg-ipsec-profile-wizard... done. >>> Upgrading necessary packages... Checking for upgrades (4 candidates): .... done Processing candidates (4 candidates): .... done Checking integrity... done (0 conflicting) The following 3 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense-pkg-ipsec-profile-wizard: 0.11 -> 0.12 [pfSense] pfSense-pkg-aws-wizard: 0.7_6 -> 0.8 [pfSense] pfSense-pkg-Netgate_Coreboot_Upgrade: 0.26 -> 0.27_1 [pfSense] Number of packages to be upgraded: 3 [1/3] Upgrading pfSense-pkg-ipsec-profile-wizard from 0.11 to 0.12... [1/3] Extracting pfSense-pkg-ipsec-profile-wizard-0.12: ........ done Removing ipsec-profile-wizard components... Menu items... done. Saving updated package information... overwrite! Loading package configuration... done. Configuring package components... Custom commands... Menu items... done. Writing configuration... done. [2/3] Upgrading pfSense-pkg-aws-wizard from 0.7_6 to 0.8... [2/3] Extracting pfSense-pkg-aws-wizard-0.8: ....... done Removing aws-wizard components... Menu items... done. Saving updated package information... overwrite! Loading package configuration... done. Configuring package components... Custom commands... Menu items... done. Writing configuration... done. [3/3] Upgrading pfSense-pkg-Netgate_Coreboot_Upgrade from 0.26 to 0.27_1... [3/3] Extracting pfSense-pkg-Netgate_Coreboot_Upgrade-0.27_1: ......... done Removing Netgate_Coreboot_Upgrade components... Menu items... done. Loading package instructions... Saving updated package information... overwrite! Loading package configuration... done. Configuring package components... Loading package instructions... Custom commands... Menu items... done. Writing configuration... done. >>> Removing unnecessary packages... done. >>> Cleanup pkg cache... done.