Watchguard WGT16641-WW Firebox T15-W with 1YR Total Security Suite User Manual

June 3, 2024
Watchguard

Watchguard WGT16641-WW Firebox T15-W with 1YR Total Security Suite

Watchguard-WGT16641-WW-Firebox-T15-W-with-1YR-Total-Security-Suite-prodact-
img

Fireware v12.5.8 Release Notes

Supported Devices| Firebox T10, T15, T30, T35, T50, M200, M300

WatchGuard AP

---|---
Release Date| 02 August 2021
Fireware OS Build| 644371
WatchGuard System Manager Build| 12.7.1: 643624
WatchGuard AP Firmware| AP120, AP320, AP322: 8.8.3-12

AP125, AP225W, AP325, AP327X, AP420: 10.0.0-124

Introduction

Fireware v12.5.8 is a maintenance release for Firebox T10, T15, T30, T35, T50, M200, and M300 appliances. This release includes enhancements to support Firebox configuration and management features in WatchGuard Cloud and important bug fixes. For a full list of the enhancements in this release, see Resolved Issues in Fireware v12.5.8.

Fireware v12.6.x and Fireware v12.7.x are based on Linux kernel 4.14. On some Firebox models, Linux kernel 4.14 does not provide sufficient quality and performance. Because of this, Fireware v12.6.x is not currently available for Firebox T10, T15, T30, T35, T55, T70, M200, and M300. Fireware v12.7.x adds support for T55 and T70 models but is not available for Firebox T10, T15, T30, T35, M200, and M300. For more information, see this Knowledge Base article.

Before You Begin

Before you install this release, make sure that you have:

  • A supported WatchGuard Firebox. This device can be a WatchGuard Firebox T Series (except T20, T40, T55, T70, T80), Firebox M200, and Firebox M300 appliance. We do not support Fireware v12.2.x or higher on XTM devices.
  • The required hardware and software components as shown below. If you use WatchGuard System Manager (WSM), make sure your WSM version is equal to or higher than the version of Fireware OS installed on your Firebox and the version of WSM installed on your Management Server. l Feature key for your Firebox — If you upgrade your device from an earlier version of Fireware OS, you can use your existing feature key. If you do not have a feature key for your device, you can log in to the WatchGuard website to download it.
  • If you are upgrading to Fireware v12.x from Fireware v11.10.x or earlier, we strongly recommend you review the Fireware v11.12.4 release notes for important information about significant feature changes that occurred in Fireware v11.12.x release cycle.
  • Some Known Issues are especially important to be aware of before you upgrade, either to or from specific versions of Fireware. To learn more, see Release-specific upgrade notes.

Note that you can install and use WatchGuard System Manager v12.x and all WSM server components1 with devices running earlier versions of Fireware. In this case, we recommend that you use the product documentation that matches your Fireware OS version. If you have a new Firebox, make sure you use the instructions in the Quick Start Guide that shipped with your device. We also recommend that you review the Hardware Guide for your Firebox model. The Hardware Guide contains useful information about your device interfaces, as well as information on resetting your device to factory default settings, if necessary.

Product documentation for all WatchGuard products is available on the WatchGuard web site at  https://www.watchguard.com/wgrd- help/documentation/overview. 1The WatchGuard System Manager WebBlocker server component is not supported by Fireboxes with v12.2 or higher, and it is no longer possible to download a database for the WebBlocker server bundled with WatchGuard System Manager.

Resolved Issues in Fireware v12.5.8

  • In WatchGuard Cloud, you can now upgrade, reboot, and fail over your locally-managed FireCluster. [FBX125X-13]
  • When FTP traffic uses SD-WAN and ECMP routing, the FTP connection now establishes successfully for both passive and active FTP modes. [FBX125X-64]
  • Traffic Management now works correctly with VLANs that have link aggregation configured. [FBX125X- 60]
  • This release includes important fixes to resolve security issues. [FBX-22002]
  • This release includes support for the AT&T Global Modem USB800. [FBX125X-71]

Resolved Issues in Fireware v12.5.7 Update 3

  • This release includes important fixes to resolve a security issue. [FBX-21579, FBX-21590, FBX-21596]
  • A scheduled reboot of a FireCluster no longer causes a cluster member to become inactive. [FBX-17099]
  • This release resolves a stuck Homer process for get_webblocker requests. [FBX-20438]
  • For Yahoo or AOL mail servers, email no longer fails to send when an inbound/outbound SMTP Proxy policy is configured to inspect on port 465. [FBX-20570]

Resolved Issues in Fireware v12.5.7 Update 2

  • To address CVE-2021-3449 and CVE-2021-3450, the OpenSSL version used in Fireware is updated to version 1.1.1k. [FBX-21412]

Resolved Issues in Fireware v12.5.7 Update 1

  • The Firebox proxy module no longer caches the server timeout action for sites when the WebBlocker Server is unavailable. [FBX-21307]
  • This release resolves an issue that caused some web pages to fail to load and generated a URI normalization failed log when an HTTPS-proxy policy is configured with IPS enabled. [FBX-20526]
  • Allowed WebBlocker categories are no longer incorrectly denied when multiple WebBlocker actions are configured. [FBX-21036]
  • SMTP proxy auto detection no longer detects application/x-pkcs7-signature as binary. [FBX-15726]
  • Traffic is no longer delayed when Google Safe Browsing is enabled with HTTPS content inspection and Application Control. [FBX-20731]
  • When the IMAP proxy Enable content type auto detection option is selected, the configured action is now correctly performed on the value stated in the Content-Type header. [FBX-20409]
  • This release resolves an FQDND process crash when domain names were longer than 64 bytes. [FBX- 21096]
  • This release resolves an issue that disconnected Mobile VPN with SSL users while a Firebox saves a configuration. [FBX-21183]
  • NAT is no longer applied to Mobile VPN with IPSec traffic when that traffic is sent between Mobile VPN clients. [FBX-20960]
  • Branch office VPNs that use IKEv2 now connect correctly to third-party endpoints when the Start Phase 1 tunnel when Firebox starts option is enabled. [FBX-21065]
  • An issue that caused the Firebox to respond to ARP requests on the wrong interface is resolved. [FBX- 21044]
  • OSPF default route distribution logic is improved. [FBX-21032, FBX-21033]
  • Interface link status is now updated correctly when you use Multi-WAN with FireCluster. [FBX-20984]
  • DHCP relay packets are now correctly delivered through VPN tunnels after a FireCluster failover event. [FBX-19805]
  • You can now edit policies that use VIF from Fireware Web UI. [FBX-21280]
  • When you configure DHCP with reserved IP addresses, DHCP addresses are now correctly assigned. [FBX-21189]
  • Dynu.com dynamic DNS registration now works correctly. [FBX-20970]
  • This release removes expired Trusted Proxy CA certificates. [FBX-21003]

Enhancements and Resolved Issues in AP Firmware Update 10.0.0-124

  • This update release maintains compatibility for the latest AP firmware across all WatchGuard AP platforms and cloud services

Known Issues and Limitations

Known issues for Fireware v12.5.8 and its management applications, including workarounds where available, can be found on the Technical Search > Knowledge Base tab. To see known issues for a specific release, from the Product & Version filters you can expand the Fireware version list and select the check box for that version. Some Known Issues are especially important to be aware of before you upgrade, either to or from specific versions of Fireware. To learn more, see Release-specific upgrade notes.

Download Software

You can download software from the WatchGuard Software Downloads Center. There are several software files available for download with this release. See the descriptions below so you know what software packages you will need for your upgrade

WatchGuard System Manager

There is no WSM v12.5.8. Use WSM v12.7.1 to manage Fireboxes that run Fireware v12.5.8. With this software package you can install WSM and the WatchGuard Server Center software: WSM_12_7_1.exe — Use this file to install WSM v12.7.1 or to upgrade WatchGuard System Manager from an earlier version

Fireware OS

You can upgrade the Fireware OS on your Firebox automatically from the Fireware Web UI System > Upgrade OS page or from WatchGuard Cloud. If you prefer to upgrade from Policy Manager, or from an earlier version of Fireware, you can download the Fireware OS image for your Firebox. Use the .exe file if you want to install or upgrade the OS using WSM. Use the .zip file if you want to install or upgrade the OS manually using Fireware Web UI.

The file name for software downloads always includes the product group, such as T30_50 for the Firebox T30 or T50.Watchguard-WGT16641-WW-Firebox-T15-W
-with-1YR-Total-Security-Suite-fig-1

Additional Firebox Software

The files in the list below are not directly used by the Firebox or for Firebox management, but are necessary for key features to work. In most cases, the file name includes the Fireware version that was current at the time of release.Watchguard-WGT16641-WW-Firebox-T15-W-with-1YR-Total-Security-Suite-
fig-2

  1. The version number in this file name does not match any Fireware version number.
  2. There is a license required for this premium client, with a 30-day free trial available with download.
  3. Click here for more information about MVLS. If you have a VPN bundle ID for macOS, it must be updated on the license server to support the macOS 3.00 or later client. To update your bundle ID, contact WatchGuard Customer Support. Make sure to have your existing bundle ID available to expedite the update.
  4. SSO Agent v12.7 supports Fireware v12.5.4 or higher only. Before you install SSO Agent v12.7, you must upgrade the Firebox to Fireware v12.5.4 or higher. If you install SSO Agent v12.7, we recommend that you upgrade all SSO Clients to v12.7. You cannot use SSO Client v12.7 with versions of the SSO Agent lower than v12.5.4. Fireware v12.5.8 supports previous versions of the SSO Agent.
  5. Not supported on ARM processor architecture.

Upgrade to Fireware v12.5.8

Important information about the upgrade process

  • We recommend you use Fireware Web UI to upgrade to Fireware v12.x.
  • We strongly recommend that you save a local copy of your Firebox configuration and create a Firebox backup image before you upgrade.
  • If you use WatchGuard System Manager (WSM), make sure your WSM version is equal to or higher than the version of Fireware OS installed on your Firebox and the version of WSM installed on your Management Server. Also, make sure to upgrade WSM before you upgrade the version of Fireware OS on your Firebox.
  • In Fireware v12.5.5 or higher, Fireware Web UI prevents the addition of users with reserved user names to the Firebox-DB authentication server. We recommend that you delete or replace any user with a reserved name before you upgrade to Fireware v12.5.5 or higher. For more information, see Reserved Firebox-DB authentication server user names.
  • If your Firebox has Fireware v12.1.1 or later, the Firebox might temporarily disable some security services to free up enough memory to successfully perform a backup. To learn more, see Backup and Restore for XTM 25, XTM 26, and Firebox T10.

If you want to upgrade a Firebox T10 device, we recommend that you reboot your Firebox before you upgrade. This clears your device memory and can prevent many problems commonly associated with upgrades in those devices. If your Firebox T10 has Fireware v12.1 or older, you might not be able to perform a backup before you upgrade the Firebox. This occurs because the memory use by Fireware v12.1 or older does not leave enough memory free to successfully complete the upgrade process on these devices. For these devices, we recommend you save a copy of the .xml configuration file with a distinctive name, as described here: Save the Configuration File.

Back Up Your WatchGuard Servers

It is not usually necessary to uninstall your previous v11.x or v12.x server or client software when you upgrade to WSM v12.x. You can install the v12.x server and client software on top of your existing installation to upgrade your WatchGuard software components. We do, however, strongly recommend that you back up your WatchGuard Servers (for example, your WatchGuard Management Server) to a safe location before you upgrade. You will need these backup files if you ever want to downgrade

For instructions on how to back up your Management Server configuration, see Fireware Help.

Upgrade to Fireware v12.5.8 from WatchGuard Cloud
From WatchGuard Cloud, you can upgrade the firmware for a Firebox that runs Fireware v12.5.2 or higher. To upgrade from WatchGuard Cloud, see Upgrade Firmware from WatchGuard Cloud in WatchGuard Cloud Help.

Upgrade to Fireware v12.5.8 from Web UI

You can upgrade the Fireware OS on your Firebox automatically from the System

Upgrade OS page. To upgrade manually, see Upgrade Fireware OS or WatchGuard System Manager in Fireware Help. If your Firebox runs Fireware v11.9.x or lower, follow the steps in this knowledge base article. If you have installed another release of this OS version on your computer, you must run the installer twice (once to remove the previous release and again to install this release).

Upgrade to Fireware v12.5.8 from WSM/Policy Manager

To upgrade from WSM/Policy Manager, see Upgrade Fireware OS or WatchGuard System Manager in Fireware Help. If you have installed another release of this OS version on your computer, you must run the installer twice (once to remove the previous release and again to install this release).

If you like to make updates to your Firebox configuration from a saved configuration file, make sure you open the configuration from the Firebox and save it to a new file after you upgrade. This is to make sure that you do not overwrite any configuration changes that were made as part of the upgrade.

Update Access Points

All AP firmware is managed by the Gateway Wireless Controller on your Firebox. The Gateway Wireless Controller automatically checks for new AP firmware updates and enables you to download the firmware directly from WatchGuard servers.

AP Firmware Upgrade

To manage AP firmware and download the latest AP firmware to your Firebox

  • From Fireware Web UI, select Dashboard > Gateway Wireless Controller. From the Summary tab, click Manage Firmware.
  • From Firebox System Manager, select the Gateway Wireless Controller tab, then click Manage Firmware.

If you have enabled automatic AP firmware updates in Gateway Wireless Controller, your APs are automatically updated between midnight and 4:00am local time.

To manually update firmware on your APs

  1. On the Access Points tab, select one or more APs.
  2. From the Actions drop-down list, click Upgrade.
  3. Click Yes to confirm that you want to upgrade the AP.

About AP Firmware and Fireware Versions

You must upgrade your APs to firmware version 8.6.0 or higher before you upgrade to Fireware v12.5.4 or higher to remain compatible with the latest versions of Fireware.

Important Steps for Upgrades from Fireware 12.0 or Lower

If you have not previously upgraded to Fireware 12.0.1 or higher and the latest AP firmware, you must perform these steps

  1. Make sure all your APs are online. You can check AP status from Fireware Web UI in Dashboard > Gateway Wireless Controller on the Access Points tab, or from Firebox System Manager, select the Gateway Wireless Controller tab.
  2. Make sure you are not using insecure default AP passphrases such as wgwap or watchguard. Your current AP passphrase must be secure and at least 8 characters in length. You can change your AP passphrase in Network > Gateway Wireless Controller > Settings.

If you do not have a secure passphrase correctly configured before the upgrade, you will lose the management connection with your deployed APs. If this occurs, you must physically reset the APs to factory default settings before you can manage the APs from Gateway Wireless Controller

Depending on the version of Fireware you upgrade from, you may need to mark APs as trusted after the upgrade to Fireware v12.0.1 or higher. You can mark APs as trusted from Fireware Web UI in Dashboard > Gateway Wireless Controller on the Access Points tab, or from Firebox System Manager, select the Gateway Wireless Controller tab.

Upgrade your FireCluster to Fireware v12.5.8

You can upgrade Fireware OS for a FireCluster from Policy Manager or Fireware Web UI. To upgrade a FireCluster from Fireware v11.10.x or lower, we recommend you use Policy Manager. As part of the upgrade process, each cluster member reboots and rejoins the cluster. Because the cluster cannot do load balancing while a cluster member reboot is in progress, we recommend you upgrade an active/active cluster at a time when the network traffic is lightest. For information on how to upgrade your FireCluster, see this Help topic .Watchguard-WGT16641-WW-Firebox-T15-W-with-1YR-Total-Security-Suite-
fig-3

Fireware 12.5.8 Operating System Compatibility Matrix

Watchguard-
WGT16641-WW-Firebox-T15-W-with-1YR-Total-Security-Suite-
fig-4

Notes about Microsoft Windows support

  • Windows 8.x support does not include Windows RT.
  • Documentation might include references and examples for Windows OS versions that are no longer
  • supported. This is provided to assist users with those OS versions, but we cannot guarantee compatibility.

The following browsers are supported for both Fireware Web UI and WebCenter (Javascript required):

  • IE 11
  • Microsoft Edge42
  • Firefox v82
  • Safari 13
  • Safari iOS 14
  • Safari (macOS Catalina)
  • Safari (macOS Big Sur)
  • Chrome v86
  1. The Server Core installation option is supported for Windows Server 2016.
  2. Microsoft Exchange Server 2010 SP3 and Microsoft Exchange Server 2013 is supported if you install Windows Server 2012 or 2012 R2 and .NET Framework 3.5.
  3. Terminal Services support with manual or Single Sign-On authentication operates in a Microsoft Terminal Services or Citrix XenApp 6.0, 6.5, 7.6, or 7.12 environment.
  4. On 11 November 2019, WatchGuard released multiple new client applications for macOS. These releases add support for macOS Catalina 10.15, and require macOS High Sierra 10.13 or later. To learn more about client support for macOS Catalina, see macOS Catalina 10.15 software compatibility. To learn more about client support for macOS Big Sur 11.x, see macOS Big Sur 11.x software compatibility. The WatchGuard Mobile VPN with IPSec client does not currently support macOS Big Sur 11.x and does not support Mac devices that have the ARM-based Apple M1 processor.
  5. Native (Cisco) IPSec client is supported for all recent versions of macOS and iOS.
  6. OpenVPN is supported for all recent versions of Android and iOS.
  7. StrongSwan is supported for all recent versions of Android.
  8. In macOS 10.15 (Catalina) or higher, you must install v12.5.2 or higher of the WatchGuard Mobile VPN with SSL client.

Authentication Support

This table gives you a quick view of the types of authentication servers supported by key features of Fireware. Using an authentication server gives you the ability to configure user and group-based firewall and VPN policies in your Firebox or XTM device configuration. With each type of third-party authentication server supported, you can specify a backup server IP address for failover.

Fireware 12.5.8 Operating System Compatibility MatrixWatchguard-WGT16641
-WW-Firebox-T15-W-with-1YR-Total-Security-Suite-fig-5

Active Directory authentication methods are supported only through a RADIUS server

**System Requirements

Watchguard-WGT16641-WW-Firebox-T15-W-with-1YR-
Total-Security-Suite-fig-6 Downgrade Instructions**

Downgrade from WSM v12.7.1

You must use WSM v12.7.1 to manage devices that run Fireware v12.5.8. If you want to revert from WSM v12.7.1 to an earlier version, you must uninstall WSM v12.7.1. When you uninstall, choose Yes when the uninstaller asks if you want to delete server configuration and data files. After the server configuration and data files are deleted, you must restore the data and server configuration files you backed up before you upgraded to WSM v12.7.1.

Downgrade from Fireware v12.5.8

If you want to downgrade from Fireware v12.5.8 to an earlier version of Fireware, we recommend you use a backup image that you created before the upgrade to Fireware v12.5.8. With a backup image, you can either

  • Restore the full backup image you created when you upgraded to Fireware v12.5.8 to complete the downgrade; or
  • Use the USB backup file you created before the upgrade as your auto-restore image, and then boot into recovery mode with the USB drive plugged in to your device.

If you need to downgrade a Firebox without a backup file after you complete the upgrade to Fireware v12.x, we recommend you Downgrade with Web UI. This process deletes the configuration file, but does not remove the device feature keys and certificates. After you downgrade the Firebox, you can use Policy Manager to Save the Configuration File to the Firebox.

If you use the Fireware Web UI or CLI to downgrade to an earlier version, the downgrade process resets the network and security settings on your device to their factory-default settings. The downgrade process does not change the device passphrases and does not remove the feature keys and certificates.

See Fireware Help for more information about these downgrade procedures, and information about how to downgrade if you do not have a backup image

Downgrade Restrictions

See this Knowledge Base article for a list of downgrade restrictions

Technical Assistance

For technical assistance, contact WatchGuard Technical Support by telephone or log in to the WatchGuard Portal on the Web at https://www.watchguard.com /wgrd-support/overview. When you contact Technical Support, you must supply your registered Product Serial Number or Partner ID.

Localization

This release includes updates to the localization for the management user interfaces (WSM application suite and Web UI) through Fireware v12.5.2. UI changes introduced since v12.5.2 may remain in English. Supported languages are

  • French (France)
  • Japanese
  • Spanish (Latin American)

Note that most data input must still be made using standard ASCII characters. You can use non-ASCII characters in some areas of the UI, including

  • Proxy deny message
  • Wireless hotspot title, terms and conditions, and message
  • WatchGuard Server Center users, groups, and role names

Any data returned from the device operating system (e.g. log data) is displayed in English only. Additionally, all items in the Web UI System Status menu and any software components provided by third-party companies remain in English

Fireware Web UI

The Web UI will launch in the language you have set in your web browser by default.

WatchGuard System Manager

When you install WSM, you can choose what language packs you want to install. The language displayed in WSM will match the language you select in your Microsoft Windows environment. For example, if you use Windows 10 and want to use WSM in Japanese, go to Control Panel > Language and select Japanese as your Display Language.

Dimension, WebCenter, Quarantine Web UI, and Wireless Hotspot

These web pages automatically display in whatever language preference you have set in your web browser

Documentation

The latest version of localized Fireware Help is available from WatchGuard Help Center. In the top-right of a Fireware Help page, click the Globe icon and select your language from the drop-down list.

References

Read User Manual Online (PDF format)

Loading......

Download This Manual (PDF format)

Download this manual  >>

Related Manuals