fireware v12.1.3 release notes - watchguard.com · m300,m370,m400,m440,m470,m500,m570,...
TRANSCRIPT
Fireware v1213 Release Notes
Supported Devices Firebox T10 T15 T30 T35 T50 T55 T70 M200M300 M370 M400 M440 M470 M500 M570M670 M4600 M5600XTM 8 800 1500 and 2500 SeriesXTM 25 XTM 26 XTM 33 XTM 330XTM 515 XTM525 XTM 535 XTM 545 XTM 1050 XTM 2050FireboxV XTMv Firebox Cloud WatchGuard AP
Release Date 29May 2018
Release Notes Revision 1 June 2018
Fireware OS Build 563398
WatchGuard SystemManager Build 562818
WatchGuard AP Device Firmware For AP100 AP102 AP200 Build 12915For AP300 Build 20010For AP120 AP320 AP322 AP325 AP420 Build850-646
IntroductionWatchGuard is pleased to announce the release of WSM and Fireware v1213 Fireware v1213 is a plannedmaintenance update to the Firebox operating system that resolves a number of outstanding Firebox issues andbugs SeeEnhancements and Resolved Issues in Fireware 1213 for more information
Before You BeginBefore you install this release make sure that you have
l A supportedWatchGuard Firebox or XTM device This device can be aWatchGuard Firebox T10 T15T30 T35 T50 T55 T70 XTM 2Series (models 25 and 26 only) XTM 33 or 330 5 Series(515525535545) 8 Series 800 Series XTM 1050 XTM 1500 Series XTM 2050 device XTM 2500Series or Firebox M Series You can also use this version of Fireware on FireboxV or XTMv (anyedition) and Firebox Cloud for AWS and AzureWedo not support Fireware v12x on XTM 505 510520 or 530 devices
l The required hardware and software components as shown below If you useWatchGuard SystemManager (WSM) make sure yourWSM version is equal to or higher than the version of Fireware OSinstalled on your Firebox or XTM device and the version of WSM installed on your Management Server
l Feature key for your Firebox or XTM devicemdash If you upgrade your device from an earlier version ofFireware OS you can use your existing feature key If you do not have a feature key for your device youcan log in to theWatchGuard website to download it
l If you are upgrading to Fireware v12x from Fireware v1110x or earlier we strongly recommend youreview the Fireware v11124 release notes for important information about significant feature changesthat occurred in Fireware v1112x release cycle
Note that you can install and useWatchGuard SystemManager v12x and all WSM server components withdevices running earlier versions of Fireware In this case we recommend that you use the productdocumentation that matches your Fireware OS version
If you have a new Firebox or XTM physical device make sure you use the instructions in theQuick Start Guidethat shipped with your device If this is a new FireboxV installation make sure you carefully review Firewarehelp in theWatchGuard Help Center for important installation and setup instructions We also recommend thatyou review the Hardware Guide for your Firebox or XTM devicemodel TheHardware Guide contains usefulinformation about your device interfaces as well as information on resetting your device to factory defaultsettings if necessary
Product documentation for all WatchGuard products is available on theWatchGuard web site athttpswwwwatchguardcomwgrd-helpdocumentationoverview
Before You Begin
2 WatchGuard Technologies Inc
Localization
Release Notes 3
LocalizationThis release includes localization update for themanagement user interfaces (WSM application suite andWebUI) current as of Fireware v120 UI changes introduced since v120may remain in English Supportedlanguages are
l French (France)l Japanesel Spanish (Latin American)
Note that most data input must still bemade using standard ASCII characters You can use non-ASCIIcharacters in some areas of the UI including
l Proxy deny messagel Wireless hotspot title terms and conditions andmessagel WatchGuard Server Center users groups and role names
Any data returned from the device operating system (eg log data) is displayed in English only Additionally allitems in theWebUI System Status menu and any software components provided by third-party companiesremain in English
Fireware Web UITheWebUI will launch in the language you have set in your web browser by default
WatchGuard System ManagerWhen you install WSM you can choose what language packs you want to install The language displayed inWSMwill match the language you select in your Microsoft Windows environment For example if you useWindows 7 and want to useWSM in Japanese go to Control Panel gt Regions and Languages and selectJapanese on the Keyboards and Languages tab as your Display Language
Dimension WebCenter Quarantine Web UI and Wireless HotspotThese web pages automatically display in whatever language preference you have set in your web browser
DocumentationLocalization updates are not yet available for Fireware Help
Important Information about Firebox CertificatesSHA-1 is being deprecated by many popular web browsers andWatchGuard recommends that you now useSHA-256 certificates Because of this we have upgraded our default Firebox certificates Starting withFireware v11104 all newly generated default Firebox certificates use a 2048-bit key length In addition newlygenerated default Proxy Server and Proxy Authority certificates use SHA-256 for their signature hashalgorithm Starting with Fireware v11105 all newly generated default Firebox certificates use SHA-256 fortheir signature hash algorithm New CSRs created from the Firebox also use SHA-256 for their signature hashalgorithm
Default certificates are not automatically upgraded after you install Fireware v11105 or later releases
To regenerate any default Firebox certificates delete the certificate and reboot the Firebox If you want toregenerate default certificates without a reboot you can use the CLI commands described in the next sectionBefore you regenerate the Proxy Server or Proxy Authority certification there are some important things toknow
The Proxy Server certificate is used for inbound HTTPS with content inspection and SMTP with TLSinspection The Proxy Authority certificate is used for outbound HTTPS with content inspection The twocertificates are linked because the default Proxy Server certificate is signed by the default Proxy Authoritycertificate If you use the CLI to regenerate these certificates after you upgrade youmust redistribute the newProxy Authority certificate to your clients or users will receive web browser warnings when they browseHTTPS sites if content inspection is enabled
Also if you use a third-party Proxy Server or Proxy Authority certificate
l The CLI commandwill not work unless you first delete either the Proxy Server or Proxy Authoritycertificate The CLI commandwill regenerate both the Proxy Server and Proxy Authority defaultcertificates
l If you originally used a third-party tool to create the CSR you can simply re-import your existing third-party certificate and private key
l If you originally created your CSR from the Firebox youmust create a new CSR to be signed and thenimport a new third-party certificate
CLI Commands to Regenerate Default Firebox CertificatesTo regenerate any default Firebox certificates delete the certificate and reboot the Firebox If you want toregenerate default certificates without a reboot you can use these CLI commands
l To upgrade the default Proxy Authority and Proxy Server certificates for use with HTTPS contentinspection you can use the CLI command upgrade certificate proxy
l To upgrade the Firebox web server certificate use the CLI command upgrade certificate webl To upgrade the SSLVPN certificate use the CLI command upgrade certificate sslvpnl To upgrade the 8021x certificate use the CLI command upgrade certificate 8021x
Formore information about the CLI see the Command Line Interface Reference
Important Information about Firebox Certificates
4 WatchGuard Technologies Inc
Fireware andWSM v1213 Operating System Compatibility
Release Notes 5
Fireware and WSM v1213 Operating System CompatibilityLast revised 12 December 2017
WSMFirewareComponent
MicrosoftWindows788110
(32-bitamp64-bit)
MicrosoftWindowsServer2012amp2012R2(64-bit)
MicrosoftWindowsServer2016(64-bit)
MacOSXmacOSv1010
v1011v1012ampv1013
Android6x
7x amp8x
iOSv8 v9v10 ampv11
WatchGuard SystemManager
WatchGuard Servers
For information onWatchGuardDimension see the Dimension ReleaseNotes
Single Sign-On Agent(Includes Event LogMonitor)1
Single Sign-On Client
Single Sign-On ExchangeMonitor2
Terminal Services Agent3
Mobile VPN with IPSec 4 4
Mobile VPN with SSL
Notes about Microsoft Windows supportl Windows 8x support does not includeWindows RT
The following browsers are supported for both FirewareWebUI andWebCenter (Javascript required)l IE 11 and laterl Microsoft Edgel Firefox v55l Safari 10l Safari iOS 10l Chrome v60
1The Server Core installation option is supported forWindows Server 20162Microsoft Exchange Server 2007 and 2010 are supported Microsoft Exchange Server 2013 is supported if youinstall Windows Server 2012 or 2012 R2 and NET Framework 353Terminal Services support with manual or Single Sign-On authentication operates in aMicrosoft TerminalServices or Citrix XenApp 45 50 60 65 76 or 712 environment4Native (Cisco) IPSec client andOpenVPN are supported for all recent versions of Mac OS and iOS To useTheWatchGuardMobile VPN with IPSec client with OS 1013 youmust upgrade to the v300 client release
Authentication SupportThis table gives you a quick view of the types of authentication servers supported by key features of FirewareUsing an authentication server gives you the ability to configure user and group-based firewall and VPN policiesin your Firebox or XTM device configuration With each type of third-party authentication server supported youcan specify a backup server IP address for failover
Fully supported by WatchGuard Not yet supported but tested with success by WatchGuardcustomers
Fireware andWSM v1213 Operating System Compatibility
6 WatchGuard Technologies Inc
Fireware andWSM v1213 Operating System Compatibility
Release Notes 7
ActiveDirectory
1 LDAPRADIUS
2SecurID
2
Firebox(Firebox-DB)
LocalAuthentication
Mobile VPN with IPSecShrew Soft 3 ndash
Mobile VPN withIPSecWatchGuard client (NCP)
Mobile VPN with IPSec for iOS andMacOS X native VPN client
Mobile VPN with IPSec for Androiddevices
ndash
Mobile VPN with SSL forWindows 4 4
Mobile VPN with SSL for Mac
Mobile VPN with SSL for iOS andAndroid devices
Mobile VPN with L2TP 6 ndash ndash
Built-in AuthenticationWeb Page onPort 4100
Single Sign-On Support (with or withoutclient software)
ndash ndash ndash
Terminal Services ManualAuthentication
Terminal Services Authentication withSingle Sign-On
5 ndash ndash ndash ndash
Citrix Manual Authentication
Citrix Manual Authentication with SingleSign-On
5 ndash ndash ndash ndash
1 Active Directory support includes both single domain and multi-domain support unless otherwise noted2 RADIUS and SecurID support includes support for both one-time passphrases and challengeresponse
authentication integrated with RADIUS In many cases SecurID can also be used with other RADIUSimplementations including Vasco
3 The Shrew Soft client does not support two-factor authentication4 Fireware supports RADIUS Filter ID 11 for group authentication5 Both single and multiple domain Active Directory configurations are supported For information about the
supported Operating System compatibility for the WatchGuard TO Agent and SSO Agent see the currentFireware and WSM Operating System Compatibility table
6 Active Directory authentication methods are supported only through a RADIUS server
System RequirementsIf you have WatchGuard SystemManager client software onlyinstalled
If you install WatchGuard SystemManager and WatchGuard Serversoftware
Minimum CPU Intel Core or Xeon
2GHz
Intel Core or Xeon
2GHz
MinimumMemory 1GB 2GB
Minimum AvailableDisk Space
250MB 1GB
MinimumRecommendedScreen Resolution
1024x768 1024x768
FireboxV System RequirementsWith support for installation in both a VMware and a Hyper-V environment aWatchGuard FireboxV virtualmachine can run on a VMware ESXi 55 60 or 65 host or onWindows Server 2012 R2 or 2016 or Hyper-VServer 2012 R2 or 2016
The hardware requirements for FireboxV are the same as for the hypervisor environment it runs in
Each FireboxV virtual machine requires 5 GB of disk space CPU andmemory requirements vary by model
FireboxV Model vCPUs (maximum) Memory (recommended)
Small 2 2048MB
Medium 4 4096MB
Large 8 4096MB
Extra Large 16 4096MB
System requirements for XTMv are included in Fireware Help
Fireware andWSM v1213 Operating System Compatibility
8 WatchGuard Technologies Inc
Downloading Software
Release Notes 9
Downloading SoftwareYou can download software from theWatchGuard Software Downloads Center
There are several software files available for download with this release See the descriptions below so youknow what software packages you will need for your upgrade
WatchGuard System ManagerWith this software package you can install WSM and theWatchGuard Server Center software
WSM12_1_3exemdashUse this file to install WSM v1213 or to upgradeWatchGuard SystemManagerfrom an earlier version toWSM v1213
Fireware OSIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from the FirewareWebUI System gt Upgrade OS page
If you prefer to upgrade from Policy Manager or from an earlier version of Fireware you can use download theFireware OS image for your Firebox or XTM device Use the exe file if you want to install or upgrade theOSusingWSM Use the zip file if you want to install or upgrade theOS manually using FirewareWebUI Use theova or vhd file to deploy a new XTMv device
If you havehellip Select from these Fireware OS packages
Firebox M5600 Firebox_OS_M4600_M5600_12_1_3exefirebox_M4600_M5600_12_1_3zip
Firebox M4600 Firebox_OS_M4600_M5600_12_1_3exefirebox_M4600_M5600_12_1_3zip
Firebox M670 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M570 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M500 Firebox_OS_M400_M500_12_1_3exefirebox_M400_M500_12_1_3zip
Firebox M470 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M440 Firebox_OS_M440_12_1_3exefirebox_M440_12_1_3zip
Firebox M400 Firebox_OS_M400_M500_12_1_3exefirebox_M400_M500_12_1_3zip
Firebox M370 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M300 Firebox_OS_M200_M300_12_1_3exefirebox_M200_M300_12_1_3zip
Firebox M200 Firebox_OS_M200_M300_12_1_3exefirebox_M200_M300_12_1_3zip
Firebox T70 Firebox_OS_T70_12_1_3exefirebox_T70_12_1_3zip
Firebox T55 Firebox_OS_T55_12_1_3exefirebox_T55_12_1_3zip
Firebox T50 Firebox_OS_T30_T50_12_1_3exefirebox_T30_T50_12_1_3zip
Firebox T35 Firebox_OS_T35_12_1_3exefirebox_T35_12_1_3zip
Firebox T30 Firebox_OS_T30_T50_12_1_3exefirebox_T30_T50_12_1_3zip
Firebox T15 Firebox_OS_T15_12_1_3exefirebox_T15_12_1_3zip
Firebox T10 Firebox_OS_T10_12_1_3exefirebox_T10_12_1_3zip
Downloading Software
10 WatchGuard Technologies Inc
Downloading Software
Release Notes 11
If you havehellip Select from these Fireware OS packages
FireboxVAll editions for VMware
FireboxV_12_1_3ovaXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
FireboxVAll editions for Hyper-V
FireboxV_12_1_3_vhdzipXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
Firebox Cloud FireboxCloud_12_1_3zip
XTM 2500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 2050 XTM_OS_XTM2050_12_1_3exextm_xtm2050_12_1_3zip
XTM 1500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 1050 XTM_OS_XTM1050_12_1_3exextm_xtm1050_12_1_3zip
XTM 800 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 8Series XTM_OS_XTM8_12_1_3exextm_xtm8_12_1_3zip
XTM 5Series Models515 525 535 and 545only
XTM_OS_XTM5_12_1_3exextm_xtm5_12_1_3zip
XTM 330 XTM_OS_XTM330_12_1_3exextm_xtm330_12_1_3zip
XTM 33 XTM_OS_XTM3_12_1_3exextm_xtm3_12_1_3zip
XTM 2526 XTM_OS_XTM2A6_12_1_3exextm_xtm2a6_12_1_3zip
XTMvAll editions for VMware
xtmv_12_1_3ovaXTM_OS_xtmv_12_1_3exextm_xtmv_12_1_3zip
XTMvAll editions for Hyper-V
xtmv_12_1_3_vhdzipXTM_OS_XTMv_12_1_3exextm_xtmv_12_1_3zip
Single Sign-On SoftwareThese files are available for Single Sign-On There are no updates with the v1213 release
l WG-Authentication-Gateway_12_0exe (SSOAgent software - required for Single Sign-On andincludes optional Event LogMonitor for clientless SSO)
l WG-Authentication-Client_11122msi (SSOClient software forWindows)l WG-SSOCLIENT-MAC_12_0dmg (SSOClient software for Mac OS X)l SSOExchangeMonitor_x86_12_0exe (ExchangeMonitor for 32-bit operating systems)l SSOExchangeMonitor_x64_12_0exe (ExchangeMonitor for 64-bit operating systems)
For information about how to install and set up Single Sign-On see the product documentation
Terminal Services Authentication SoftwareThis file is not updated with the Fireware v1213 release
l TO_AGENT_SETUP_11_12exe (This installer includes both 32-bit and 64-bit file support)
Mobile VPN with SSL Client for Windows and MacThere are two files available for download if you useMobile VPN with SSL
l WG-MVPN-SSL_12_0exe (Client software forWindows)l WG-MVPN-SSL_12_0dmg (Client software for Mac)
Mobile VPN with IPSec client for Windows and MacThere are several available files to download
Shrew Soft Client
l Shrew Soft Client 222 for Windows - No client license required
WatchGuard IPSec Mobile VPN Clients
The current WatchGuard IPSec Mobile VPN Client forWindows version is 1213
l WatchGuard IPSec Mobile VPN Client for Windows (32-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
l WatchGuard IPSec Mobile VPN Client for Windows (64-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
The current macOS client version is 300
l WatchGuard IPSec Mobile VPN Client for macOS powered by NCP - There is a license requiredfor this premium client with a 30-day free trial available with download
WatchGuard Mobile VPN License Server
l WatchGuard Mobile VPN License Server (MVLS) v20 powered by NCP- Click here for moreinformation about MVLS If you have a VPN bundle ID for macOS it must be updated on the licenseserver to support the new macOS 300 client To update your bundle ID contact WatchGuard CustomerSupport Make sure to have your existing bundle ID available to expedite the update
Downloading Software
12 WatchGuard Technologies Inc
Upgrade Notes
Release Notes 13
Upgrade Notes
SSLTLS Settings Precedence and InheritanceFour Firebox features use SSLTLS for secure communication and share the sameOpenVPN serverManagement Tunnel over SSL on hub devices BOVPN over TLS in Server mode Mobile VPN with SSL andthe Access Portal These features also share some settings When you enablemore than one of thesefeatures settings for some features have a higher precedence than settings for other features Shared settingsare not configurable for the features with lower precedence For more information see this topic in FirewareHelp
Modem Configurations Converted to External Interfaces with Failover EnabledIf your Firebox was configured for modem failover when you upgrade your Firebox to Fireware v121 or higherthemodem configuration is automatically converted to an external interface with modem failover enabled If allother external interfaces become unavailable traffic automatically fails over to themodem interface Modeminterfaces can also participate in multi-WAN on all devices except the Firebox T10 Firebox T15 and XTM 2Series devices that do not have the Pro upgrade
HTTPS Proxy Content Inspection with Fireware v121With Fireware 121 we updated the HTTPS proxy action to include a Content Inspection Exceptions list whichincludes domains for services such as Dropbox Skype andMicrosoft Office that are known to be incompatiblewith content inspection The HTTPS proxy does not perform content inspection for domains with enabledexceptions on the Content Inspection Exceptions list
When you upgrade your Firebox to Fireware v121 or higher the Content Inspection Exceptions list isautomatically enabled in all HTTPS proxy actions that have content inspection enabled After the upgrade werecommend that you review the Content Inspection Exceptions list in your configured HTTPS proxy actionsand disable the exception for any domain you do not want the HTTPS proxy to allow without content inspectionFor more information seeWhich applications are on the default exception list in an HTTPS proxy action in theKnowledge Base
Gateway AV Engine Upgrade with Fireware v120With Fireware v120 we updated the engine used by Gateway AV to a new engine from BitDefender As aresult any Firebox that upgrades from Fireware v11x version to v120 or later must download a new signatureset which can take 7-10minutes for the first update It can take an additional 5-7minutes to synchronize aFireCluster We recommend that you upgrade to Fireware v12x at a quiet time on your network After the initialupdate signature updates are incremental andmuch faster than in previous versions
While the new signature set is being downloaded network users could experience issues related to GatewayAV scan failures for several minutes after the update and inbound emails sent through the SMTP proxy couldbe locked
XTMv Upgrade NotesYou cannot upgrade an XTMv device to FireboxV For Fireware v1111 and higher the XTMv device is a 64-bitvirtual machine You cannot upgrade an XTMv device from Fireware v1110x or lower to Fireware v1111 orhigher Instead youmust use the OVA file to deploy a new 64-bit Fireware v1111x or v12x XTMv VM andthen use Policy Manager to move the existing configuration from the 32-bit XTMv VM to the 64-bit XTMv VMFor more information about how tomove the configuration or deploy a new XTMv VM see Fireware Help Whenyour XTMv instance has been updated to v1111 or higher you can then use the usual upgrade procedure asdetailed in the next section
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
If your Firebox is a T10 XTM 25 or XTM 26 device with OS version 121 or older youmightnot be able to perform a backup before you upgrade the Firebox This occurs because thememory use by Fireware v121 or older does not leave enoughmemory free to successfullycomplete the upgrade process on these devices For these devices we recommend you savea copy of the xml configuration file with a distinctive name as described here Save theConfiguration File
If you need to downgrade a Firebox without a backup file after you complete the upgrade toFireware v12x we recommend you Downgrade withWebUI This process deletes theconfiguration file but does not remove the device feature keys and certificates After youdowngrade the Firebox you can use Policy Manager to Save the Configuration File to theFireboxIf your Firebox has Fireware v1211 or later the Firebox will temporarily disable somesecurity services to free up enoughmemory to successfully perform a backup To learnmoresee Backup and Restore for XTM 25 XTM 26 and Firebox T10
Important Information about the upgrade process
l We recommend you use FirewareWebUI to upgrade to Fireware v12x You can also use PolicyManager if you prefer
l We strongly recommend that you save a local copy of your Firebox configuration and create a Fireboxbackup image before you upgrade
l If you useWatchGuard SystemManager (WSM) make sure yourWSM version is equal to or higherthan the version of Fireware OS installed on your Firebox and the version of WSM installed on yourManagement Server Also make sure to upgradeWSM before you upgrade the version of Fireware OSon your Firebox
Upgrade to Fireware v1213
14 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 15
If you want to upgrade a Firebox T10 XTM 2Series 33 330 or 5 Series device werecommend that you reboot your Firebox before you upgrade This clears your devicememoryand can prevent many problems commonly associated with upgrades in those devices
Back Up Your WatchGuard ServersIt is not usually necessary to uninstall your previous v11x or v12x server or client software when you upgradetoWSM v12x You can install the v12x server and client software on top of your existing installation toupgrade yourWatchGuard software components We do however strongly recommend that you back up yourWatchGuard Servers (for example yourWatchGuardManagement Server) to a safe location before youupgrade You will need these backup files if you ever want to downgrade
You cannot restore aWatchGuard Server backup file created withWatchGuard SystemManager v12x to to a v11x installation Make sure to retain your older server backup fileswhen you upgrade to v120 or later in case you want to downgrade in the future
To back up your Management Server configuration from the computer where you installed theManagementServer
1 FromWatchGuard Server Center select BackupRestore Management ServerThe WatchGuard Server Center BackupRestore Wizard starts
2 Click NextThe Select an action screen appears
3 Select Back up settings4 Click Next
The Specify a backup file screen appears5 Click Browse to select a location for the backup file Make sure you save the configuration file to a
location you can access later to restore the configuration6 Click Next
The WatchGuard Server Center BackupRestore Wizard is complete screen appears7 Click Finish to exit the wizard
Upgrade to Fireware v1213 fromWeb UIIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from theSystem gt Upgrade OS page If your Firebox is running v119x or earlier use thesesteps to upgrade
1 Before you begin save a local copy of your configuration file2 Go toSystem gt Backup Image or use the USB Backup feature to back up your current device image3 On your management computer launch the OS software file you downloaded from theWatchGuard
Software Downloads pageIf you use theWindows-based installer on a computer with aWindows 64-bit operating system thisinstallation extracts an upgrade file called [product series]_[product code]sysa-dl to the defaultlocation of CProgram Files(x86)Common FilesWatchGuardresourcesFirewareXTM1213[model]or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Connect to your Firebox with theWebUI and select System gt Upgrade OS5 Browse to the location of the [product series]_[product code]sysa-dl from Step 2 and click Upgrade
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v121 3installer twice (once to remove v1213 software and again to install v1213)
Upgrade to Fireware v1213
16 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 17
Upgrade to Fireware v1213 fromWSMPolicy Manager1 Before you begin save a local copy of your configuration file2 Select File gt Backup or use the USB Backup feature to back up your current device image3 On amanagement computer running aWindows 64-bit operating system launch the OS executable file
you downloaded from theWatchGuard Portal This installation extracts an upgrade file called [Firebox orxtm series]_[product code]sysa-dl to the default location of CProgram Files(x86)CommonfilesWatchGuardresourcesFirewareXTM1213[model] or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Install and openWatchGuard SystemManager v1213 Connect to your Firebox and launch PolicyManager
5 From Policy Manager select File gt Upgrade When prompted browse to and select the [productseries]_[product code]sysa-dl file from Step 2
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v1213installer twice (once to remove v1213 software and again to install v1213)
If you like tomake updates to your Firebox configuration from a saved configuration file makesure you open the configuration from the Firebox and save it to a new file after you upgradeThis is to make sure that you do not overwrite any configuration changes that weremade aspart of the upgrade
Other Upgrade IssuesThere is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Fireware v12x is not supported on XTM 5Series devices models 505 510 520 or 530
Before you upgrade to Fireware v12x your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is preventedIf you try to schedule anOS update of managed devices through aManagement Server theupgrade is also preventedIf you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x orv1110x before you upgrade to Fireware v12x or your Firebox will be reset to a default state
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
18 WatchGuard Technologies Inc
Update AP Devices
Release Notes 19
Update AP Devices
OnApril 12 2018 WatchGuard released AP firmware versions 12915 for the AP100 AP102and AP200 and 20010 for the AP300 to address security vulnerabilities We highlyrecommend you install these AP firmware updates For more detailed information on thesevulnerabilities see AP100AP102AP200 Chained Vulnerabilities In addition to addressingthese vulnerabilities the AP firmware updates disable the AP local web UI As these APmodels can only bemanaged with the Gateway Wireless Controller the AP local web UI is nolonger supported
Beginning with Fireware v11124 AP firmware is no longer bundled with Fireware OS All AP device firmwareis managed by the Gateway Wireless Controller on your Firebox TheGateway Wireless Controllerautomatically checks for new AP firmware updates and enables you to download the firmware directly fromWatchGuard servers
Important Upgrade StepsIf you have not previously upgraded to Fireware 1201 or higher and the latest AP firmware youmust performthese steps
1 Make sure all your APs are online You can check AP status from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager selecttheGateway Wireless Controller tab
2 Make sure you are not using insecure default AP passphrases such as wgwap orwatchguard Yourcurrent AP passphrasemust be secure and at least 8 characters in length You can change your APpassphrase inNetwork gt Gateway Wireless Controller gt Settings
If you do not have a secure passphrase correctly configured before the upgrade you will losethemanagement connection with your deployed APs If this occurs youmust physicallyreset the APs to factory default settings to be able tomanage the APs from GatewayWireless Controller
Depending on the version of Fireware you are upgrading from youmay need tomark APs as trusted after theupgrade to Fireware v1201 or higher You canmark APs as trusted from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager select theGateway Wireless Controller tab
AP Firmware UpgradeThe current AP firmware versions for each AP devicemodel are
AP Device Model Current Firmware Version
AP100 AP102 AP200 12915
AP300 20010
AP120 AP320 AP322 AP325AP420
850-646
Tomanage AP firmware and download the latest AP firmware to your Firebox
n From FirewareWebUI select Dashboard gt Gateway Wireless Controller From theSummary tabclick Manage Firmware
n From Firebox SystemManager select theGateway Wireless Controller tab then click ManageFirmware
Note that you cannot upgrade an AP120 AP320 AP322 or AP420 to 830-657 or higher unless your Firebox isrunning Fireware v11124 or higher If your Firebox does not run v11124 or higher you will not see an optionto upgrade to AP firmware v830-657 or higher
If you have enabled automatic AP device firmware updates in Gateway Wireless Controller your AP devicesare automatically updated betweenmidnight and 400am local time
Tomanually update firmware on your AP devices
1 On theAccess Points tab select one or more AP devices2 From theActions drop-down list click Upgrade3 Click Yes to confirm that you want to upgrade the AP device
Update AP Devices
20 WatchGuard Technologies Inc
Upgrade your FireCluster to Fireware v1213
Release Notes 21
Upgrade your FireCluster to Fireware v1213You can upgrade Fireware OS for a FireCluster from Policy Manager or FirewareWebUI To upgrade aFireCluster from Fireware v1110x or lower we recommend you use Policy Manager
As part of the upgrade process each cluster member reboots and rejoins the cluster Because the clustercannot do load balancing while a cluster member reboot is in progress we recommend you upgrade anactiveactive cluster at a time when the network traffic is lightest
For information on how to upgrade your FireCluster see this Help topic
There is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Before you upgrade to Fireware v1111 or higher your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is prevented
If you try to schedule anOS update of managed devices through aManagement Server theupgrade is also prevented
If you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x before youupgrade to Fireware v1111x or higher or your Firebox will be reset to a default state
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
Before You BeginBefore you install this release make sure that you have
l A supportedWatchGuard Firebox or XTM device This device can be aWatchGuard Firebox T10 T15T30 T35 T50 T55 T70 XTM 2Series (models 25 and 26 only) XTM 33 or 330 5 Series(515525535545) 8 Series 800 Series XTM 1050 XTM 1500 Series XTM 2050 device XTM 2500Series or Firebox M Series You can also use this version of Fireware on FireboxV or XTMv (anyedition) and Firebox Cloud for AWS and AzureWedo not support Fireware v12x on XTM 505 510520 or 530 devices
l The required hardware and software components as shown below If you useWatchGuard SystemManager (WSM) make sure yourWSM version is equal to or higher than the version of Fireware OSinstalled on your Firebox or XTM device and the version of WSM installed on your Management Server
l Feature key for your Firebox or XTM devicemdash If you upgrade your device from an earlier version ofFireware OS you can use your existing feature key If you do not have a feature key for your device youcan log in to theWatchGuard website to download it
l If you are upgrading to Fireware v12x from Fireware v1110x or earlier we strongly recommend youreview the Fireware v11124 release notes for important information about significant feature changesthat occurred in Fireware v1112x release cycle
Note that you can install and useWatchGuard SystemManager v12x and all WSM server components withdevices running earlier versions of Fireware In this case we recommend that you use the productdocumentation that matches your Fireware OS version
If you have a new Firebox or XTM physical device make sure you use the instructions in theQuick Start Guidethat shipped with your device If this is a new FireboxV installation make sure you carefully review Firewarehelp in theWatchGuard Help Center for important installation and setup instructions We also recommend thatyou review the Hardware Guide for your Firebox or XTM devicemodel TheHardware Guide contains usefulinformation about your device interfaces as well as information on resetting your device to factory defaultsettings if necessary
Product documentation for all WatchGuard products is available on theWatchGuard web site athttpswwwwatchguardcomwgrd-helpdocumentationoverview
Before You Begin
2 WatchGuard Technologies Inc
Localization
Release Notes 3
LocalizationThis release includes localization update for themanagement user interfaces (WSM application suite andWebUI) current as of Fireware v120 UI changes introduced since v120may remain in English Supportedlanguages are
l French (France)l Japanesel Spanish (Latin American)
Note that most data input must still bemade using standard ASCII characters You can use non-ASCIIcharacters in some areas of the UI including
l Proxy deny messagel Wireless hotspot title terms and conditions andmessagel WatchGuard Server Center users groups and role names
Any data returned from the device operating system (eg log data) is displayed in English only Additionally allitems in theWebUI System Status menu and any software components provided by third-party companiesremain in English
Fireware Web UITheWebUI will launch in the language you have set in your web browser by default
WatchGuard System ManagerWhen you install WSM you can choose what language packs you want to install The language displayed inWSMwill match the language you select in your Microsoft Windows environment For example if you useWindows 7 and want to useWSM in Japanese go to Control Panel gt Regions and Languages and selectJapanese on the Keyboards and Languages tab as your Display Language
Dimension WebCenter Quarantine Web UI and Wireless HotspotThese web pages automatically display in whatever language preference you have set in your web browser
DocumentationLocalization updates are not yet available for Fireware Help
Important Information about Firebox CertificatesSHA-1 is being deprecated by many popular web browsers andWatchGuard recommends that you now useSHA-256 certificates Because of this we have upgraded our default Firebox certificates Starting withFireware v11104 all newly generated default Firebox certificates use a 2048-bit key length In addition newlygenerated default Proxy Server and Proxy Authority certificates use SHA-256 for their signature hashalgorithm Starting with Fireware v11105 all newly generated default Firebox certificates use SHA-256 fortheir signature hash algorithm New CSRs created from the Firebox also use SHA-256 for their signature hashalgorithm
Default certificates are not automatically upgraded after you install Fireware v11105 or later releases
To regenerate any default Firebox certificates delete the certificate and reboot the Firebox If you want toregenerate default certificates without a reboot you can use the CLI commands described in the next sectionBefore you regenerate the Proxy Server or Proxy Authority certification there are some important things toknow
The Proxy Server certificate is used for inbound HTTPS with content inspection and SMTP with TLSinspection The Proxy Authority certificate is used for outbound HTTPS with content inspection The twocertificates are linked because the default Proxy Server certificate is signed by the default Proxy Authoritycertificate If you use the CLI to regenerate these certificates after you upgrade youmust redistribute the newProxy Authority certificate to your clients or users will receive web browser warnings when they browseHTTPS sites if content inspection is enabled
Also if you use a third-party Proxy Server or Proxy Authority certificate
l The CLI commandwill not work unless you first delete either the Proxy Server or Proxy Authoritycertificate The CLI commandwill regenerate both the Proxy Server and Proxy Authority defaultcertificates
l If you originally used a third-party tool to create the CSR you can simply re-import your existing third-party certificate and private key
l If you originally created your CSR from the Firebox youmust create a new CSR to be signed and thenimport a new third-party certificate
CLI Commands to Regenerate Default Firebox CertificatesTo regenerate any default Firebox certificates delete the certificate and reboot the Firebox If you want toregenerate default certificates without a reboot you can use these CLI commands
l To upgrade the default Proxy Authority and Proxy Server certificates for use with HTTPS contentinspection you can use the CLI command upgrade certificate proxy
l To upgrade the Firebox web server certificate use the CLI command upgrade certificate webl To upgrade the SSLVPN certificate use the CLI command upgrade certificate sslvpnl To upgrade the 8021x certificate use the CLI command upgrade certificate 8021x
Formore information about the CLI see the Command Line Interface Reference
Important Information about Firebox Certificates
4 WatchGuard Technologies Inc
Fireware andWSM v1213 Operating System Compatibility
Release Notes 5
Fireware and WSM v1213 Operating System CompatibilityLast revised 12 December 2017
WSMFirewareComponent
MicrosoftWindows788110
(32-bitamp64-bit)
MicrosoftWindowsServer2012amp2012R2(64-bit)
MicrosoftWindowsServer2016(64-bit)
MacOSXmacOSv1010
v1011v1012ampv1013
Android6x
7x amp8x
iOSv8 v9v10 ampv11
WatchGuard SystemManager
WatchGuard Servers
For information onWatchGuardDimension see the Dimension ReleaseNotes
Single Sign-On Agent(Includes Event LogMonitor)1
Single Sign-On Client
Single Sign-On ExchangeMonitor2
Terminal Services Agent3
Mobile VPN with IPSec 4 4
Mobile VPN with SSL
Notes about Microsoft Windows supportl Windows 8x support does not includeWindows RT
The following browsers are supported for both FirewareWebUI andWebCenter (Javascript required)l IE 11 and laterl Microsoft Edgel Firefox v55l Safari 10l Safari iOS 10l Chrome v60
1The Server Core installation option is supported forWindows Server 20162Microsoft Exchange Server 2007 and 2010 are supported Microsoft Exchange Server 2013 is supported if youinstall Windows Server 2012 or 2012 R2 and NET Framework 353Terminal Services support with manual or Single Sign-On authentication operates in aMicrosoft TerminalServices or Citrix XenApp 45 50 60 65 76 or 712 environment4Native (Cisco) IPSec client andOpenVPN are supported for all recent versions of Mac OS and iOS To useTheWatchGuardMobile VPN with IPSec client with OS 1013 youmust upgrade to the v300 client release
Authentication SupportThis table gives you a quick view of the types of authentication servers supported by key features of FirewareUsing an authentication server gives you the ability to configure user and group-based firewall and VPN policiesin your Firebox or XTM device configuration With each type of third-party authentication server supported youcan specify a backup server IP address for failover
Fully supported by WatchGuard Not yet supported but tested with success by WatchGuardcustomers
Fireware andWSM v1213 Operating System Compatibility
6 WatchGuard Technologies Inc
Fireware andWSM v1213 Operating System Compatibility
Release Notes 7
ActiveDirectory
1 LDAPRADIUS
2SecurID
2
Firebox(Firebox-DB)
LocalAuthentication
Mobile VPN with IPSecShrew Soft 3 ndash
Mobile VPN withIPSecWatchGuard client (NCP)
Mobile VPN with IPSec for iOS andMacOS X native VPN client
Mobile VPN with IPSec for Androiddevices
ndash
Mobile VPN with SSL forWindows 4 4
Mobile VPN with SSL for Mac
Mobile VPN with SSL for iOS andAndroid devices
Mobile VPN with L2TP 6 ndash ndash
Built-in AuthenticationWeb Page onPort 4100
Single Sign-On Support (with or withoutclient software)
ndash ndash ndash
Terminal Services ManualAuthentication
Terminal Services Authentication withSingle Sign-On
5 ndash ndash ndash ndash
Citrix Manual Authentication
Citrix Manual Authentication with SingleSign-On
5 ndash ndash ndash ndash
1 Active Directory support includes both single domain and multi-domain support unless otherwise noted2 RADIUS and SecurID support includes support for both one-time passphrases and challengeresponse
authentication integrated with RADIUS In many cases SecurID can also be used with other RADIUSimplementations including Vasco
3 The Shrew Soft client does not support two-factor authentication4 Fireware supports RADIUS Filter ID 11 for group authentication5 Both single and multiple domain Active Directory configurations are supported For information about the
supported Operating System compatibility for the WatchGuard TO Agent and SSO Agent see the currentFireware and WSM Operating System Compatibility table
6 Active Directory authentication methods are supported only through a RADIUS server
System RequirementsIf you have WatchGuard SystemManager client software onlyinstalled
If you install WatchGuard SystemManager and WatchGuard Serversoftware
Minimum CPU Intel Core or Xeon
2GHz
Intel Core or Xeon
2GHz
MinimumMemory 1GB 2GB
Minimum AvailableDisk Space
250MB 1GB
MinimumRecommendedScreen Resolution
1024x768 1024x768
FireboxV System RequirementsWith support for installation in both a VMware and a Hyper-V environment aWatchGuard FireboxV virtualmachine can run on a VMware ESXi 55 60 or 65 host or onWindows Server 2012 R2 or 2016 or Hyper-VServer 2012 R2 or 2016
The hardware requirements for FireboxV are the same as for the hypervisor environment it runs in
Each FireboxV virtual machine requires 5 GB of disk space CPU andmemory requirements vary by model
FireboxV Model vCPUs (maximum) Memory (recommended)
Small 2 2048MB
Medium 4 4096MB
Large 8 4096MB
Extra Large 16 4096MB
System requirements for XTMv are included in Fireware Help
Fireware andWSM v1213 Operating System Compatibility
8 WatchGuard Technologies Inc
Downloading Software
Release Notes 9
Downloading SoftwareYou can download software from theWatchGuard Software Downloads Center
There are several software files available for download with this release See the descriptions below so youknow what software packages you will need for your upgrade
WatchGuard System ManagerWith this software package you can install WSM and theWatchGuard Server Center software
WSM12_1_3exemdashUse this file to install WSM v1213 or to upgradeWatchGuard SystemManagerfrom an earlier version toWSM v1213
Fireware OSIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from the FirewareWebUI System gt Upgrade OS page
If you prefer to upgrade from Policy Manager or from an earlier version of Fireware you can use download theFireware OS image for your Firebox or XTM device Use the exe file if you want to install or upgrade theOSusingWSM Use the zip file if you want to install or upgrade theOS manually using FirewareWebUI Use theova or vhd file to deploy a new XTMv device
If you havehellip Select from these Fireware OS packages
Firebox M5600 Firebox_OS_M4600_M5600_12_1_3exefirebox_M4600_M5600_12_1_3zip
Firebox M4600 Firebox_OS_M4600_M5600_12_1_3exefirebox_M4600_M5600_12_1_3zip
Firebox M670 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M570 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M500 Firebox_OS_M400_M500_12_1_3exefirebox_M400_M500_12_1_3zip
Firebox M470 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M440 Firebox_OS_M440_12_1_3exefirebox_M440_12_1_3zip
Firebox M400 Firebox_OS_M400_M500_12_1_3exefirebox_M400_M500_12_1_3zip
Firebox M370 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M300 Firebox_OS_M200_M300_12_1_3exefirebox_M200_M300_12_1_3zip
Firebox M200 Firebox_OS_M200_M300_12_1_3exefirebox_M200_M300_12_1_3zip
Firebox T70 Firebox_OS_T70_12_1_3exefirebox_T70_12_1_3zip
Firebox T55 Firebox_OS_T55_12_1_3exefirebox_T55_12_1_3zip
Firebox T50 Firebox_OS_T30_T50_12_1_3exefirebox_T30_T50_12_1_3zip
Firebox T35 Firebox_OS_T35_12_1_3exefirebox_T35_12_1_3zip
Firebox T30 Firebox_OS_T30_T50_12_1_3exefirebox_T30_T50_12_1_3zip
Firebox T15 Firebox_OS_T15_12_1_3exefirebox_T15_12_1_3zip
Firebox T10 Firebox_OS_T10_12_1_3exefirebox_T10_12_1_3zip
Downloading Software
10 WatchGuard Technologies Inc
Downloading Software
Release Notes 11
If you havehellip Select from these Fireware OS packages
FireboxVAll editions for VMware
FireboxV_12_1_3ovaXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
FireboxVAll editions for Hyper-V
FireboxV_12_1_3_vhdzipXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
Firebox Cloud FireboxCloud_12_1_3zip
XTM 2500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 2050 XTM_OS_XTM2050_12_1_3exextm_xtm2050_12_1_3zip
XTM 1500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 1050 XTM_OS_XTM1050_12_1_3exextm_xtm1050_12_1_3zip
XTM 800 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 8Series XTM_OS_XTM8_12_1_3exextm_xtm8_12_1_3zip
XTM 5Series Models515 525 535 and 545only
XTM_OS_XTM5_12_1_3exextm_xtm5_12_1_3zip
XTM 330 XTM_OS_XTM330_12_1_3exextm_xtm330_12_1_3zip
XTM 33 XTM_OS_XTM3_12_1_3exextm_xtm3_12_1_3zip
XTM 2526 XTM_OS_XTM2A6_12_1_3exextm_xtm2a6_12_1_3zip
XTMvAll editions for VMware
xtmv_12_1_3ovaXTM_OS_xtmv_12_1_3exextm_xtmv_12_1_3zip
XTMvAll editions for Hyper-V
xtmv_12_1_3_vhdzipXTM_OS_XTMv_12_1_3exextm_xtmv_12_1_3zip
Single Sign-On SoftwareThese files are available for Single Sign-On There are no updates with the v1213 release
l WG-Authentication-Gateway_12_0exe (SSOAgent software - required for Single Sign-On andincludes optional Event LogMonitor for clientless SSO)
l WG-Authentication-Client_11122msi (SSOClient software forWindows)l WG-SSOCLIENT-MAC_12_0dmg (SSOClient software for Mac OS X)l SSOExchangeMonitor_x86_12_0exe (ExchangeMonitor for 32-bit operating systems)l SSOExchangeMonitor_x64_12_0exe (ExchangeMonitor for 64-bit operating systems)
For information about how to install and set up Single Sign-On see the product documentation
Terminal Services Authentication SoftwareThis file is not updated with the Fireware v1213 release
l TO_AGENT_SETUP_11_12exe (This installer includes both 32-bit and 64-bit file support)
Mobile VPN with SSL Client for Windows and MacThere are two files available for download if you useMobile VPN with SSL
l WG-MVPN-SSL_12_0exe (Client software forWindows)l WG-MVPN-SSL_12_0dmg (Client software for Mac)
Mobile VPN with IPSec client for Windows and MacThere are several available files to download
Shrew Soft Client
l Shrew Soft Client 222 for Windows - No client license required
WatchGuard IPSec Mobile VPN Clients
The current WatchGuard IPSec Mobile VPN Client forWindows version is 1213
l WatchGuard IPSec Mobile VPN Client for Windows (32-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
l WatchGuard IPSec Mobile VPN Client for Windows (64-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
The current macOS client version is 300
l WatchGuard IPSec Mobile VPN Client for macOS powered by NCP - There is a license requiredfor this premium client with a 30-day free trial available with download
WatchGuard Mobile VPN License Server
l WatchGuard Mobile VPN License Server (MVLS) v20 powered by NCP- Click here for moreinformation about MVLS If you have a VPN bundle ID for macOS it must be updated on the licenseserver to support the new macOS 300 client To update your bundle ID contact WatchGuard CustomerSupport Make sure to have your existing bundle ID available to expedite the update
Downloading Software
12 WatchGuard Technologies Inc
Upgrade Notes
Release Notes 13
Upgrade Notes
SSLTLS Settings Precedence and InheritanceFour Firebox features use SSLTLS for secure communication and share the sameOpenVPN serverManagement Tunnel over SSL on hub devices BOVPN over TLS in Server mode Mobile VPN with SSL andthe Access Portal These features also share some settings When you enablemore than one of thesefeatures settings for some features have a higher precedence than settings for other features Shared settingsare not configurable for the features with lower precedence For more information see this topic in FirewareHelp
Modem Configurations Converted to External Interfaces with Failover EnabledIf your Firebox was configured for modem failover when you upgrade your Firebox to Fireware v121 or higherthemodem configuration is automatically converted to an external interface with modem failover enabled If allother external interfaces become unavailable traffic automatically fails over to themodem interface Modeminterfaces can also participate in multi-WAN on all devices except the Firebox T10 Firebox T15 and XTM 2Series devices that do not have the Pro upgrade
HTTPS Proxy Content Inspection with Fireware v121With Fireware 121 we updated the HTTPS proxy action to include a Content Inspection Exceptions list whichincludes domains for services such as Dropbox Skype andMicrosoft Office that are known to be incompatiblewith content inspection The HTTPS proxy does not perform content inspection for domains with enabledexceptions on the Content Inspection Exceptions list
When you upgrade your Firebox to Fireware v121 or higher the Content Inspection Exceptions list isautomatically enabled in all HTTPS proxy actions that have content inspection enabled After the upgrade werecommend that you review the Content Inspection Exceptions list in your configured HTTPS proxy actionsand disable the exception for any domain you do not want the HTTPS proxy to allow without content inspectionFor more information seeWhich applications are on the default exception list in an HTTPS proxy action in theKnowledge Base
Gateway AV Engine Upgrade with Fireware v120With Fireware v120 we updated the engine used by Gateway AV to a new engine from BitDefender As aresult any Firebox that upgrades from Fireware v11x version to v120 or later must download a new signatureset which can take 7-10minutes for the first update It can take an additional 5-7minutes to synchronize aFireCluster We recommend that you upgrade to Fireware v12x at a quiet time on your network After the initialupdate signature updates are incremental andmuch faster than in previous versions
While the new signature set is being downloaded network users could experience issues related to GatewayAV scan failures for several minutes after the update and inbound emails sent through the SMTP proxy couldbe locked
XTMv Upgrade NotesYou cannot upgrade an XTMv device to FireboxV For Fireware v1111 and higher the XTMv device is a 64-bitvirtual machine You cannot upgrade an XTMv device from Fireware v1110x or lower to Fireware v1111 orhigher Instead youmust use the OVA file to deploy a new 64-bit Fireware v1111x or v12x XTMv VM andthen use Policy Manager to move the existing configuration from the 32-bit XTMv VM to the 64-bit XTMv VMFor more information about how tomove the configuration or deploy a new XTMv VM see Fireware Help Whenyour XTMv instance has been updated to v1111 or higher you can then use the usual upgrade procedure asdetailed in the next section
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
If your Firebox is a T10 XTM 25 or XTM 26 device with OS version 121 or older youmightnot be able to perform a backup before you upgrade the Firebox This occurs because thememory use by Fireware v121 or older does not leave enoughmemory free to successfullycomplete the upgrade process on these devices For these devices we recommend you savea copy of the xml configuration file with a distinctive name as described here Save theConfiguration File
If you need to downgrade a Firebox without a backup file after you complete the upgrade toFireware v12x we recommend you Downgrade withWebUI This process deletes theconfiguration file but does not remove the device feature keys and certificates After youdowngrade the Firebox you can use Policy Manager to Save the Configuration File to theFireboxIf your Firebox has Fireware v1211 or later the Firebox will temporarily disable somesecurity services to free up enoughmemory to successfully perform a backup To learnmoresee Backup and Restore for XTM 25 XTM 26 and Firebox T10
Important Information about the upgrade process
l We recommend you use FirewareWebUI to upgrade to Fireware v12x You can also use PolicyManager if you prefer
l We strongly recommend that you save a local copy of your Firebox configuration and create a Fireboxbackup image before you upgrade
l If you useWatchGuard SystemManager (WSM) make sure yourWSM version is equal to or higherthan the version of Fireware OS installed on your Firebox and the version of WSM installed on yourManagement Server Also make sure to upgradeWSM before you upgrade the version of Fireware OSon your Firebox
Upgrade to Fireware v1213
14 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 15
If you want to upgrade a Firebox T10 XTM 2Series 33 330 or 5 Series device werecommend that you reboot your Firebox before you upgrade This clears your devicememoryand can prevent many problems commonly associated with upgrades in those devices
Back Up Your WatchGuard ServersIt is not usually necessary to uninstall your previous v11x or v12x server or client software when you upgradetoWSM v12x You can install the v12x server and client software on top of your existing installation toupgrade yourWatchGuard software components We do however strongly recommend that you back up yourWatchGuard Servers (for example yourWatchGuardManagement Server) to a safe location before youupgrade You will need these backup files if you ever want to downgrade
You cannot restore aWatchGuard Server backup file created withWatchGuard SystemManager v12x to to a v11x installation Make sure to retain your older server backup fileswhen you upgrade to v120 or later in case you want to downgrade in the future
To back up your Management Server configuration from the computer where you installed theManagementServer
1 FromWatchGuard Server Center select BackupRestore Management ServerThe WatchGuard Server Center BackupRestore Wizard starts
2 Click NextThe Select an action screen appears
3 Select Back up settings4 Click Next
The Specify a backup file screen appears5 Click Browse to select a location for the backup file Make sure you save the configuration file to a
location you can access later to restore the configuration6 Click Next
The WatchGuard Server Center BackupRestore Wizard is complete screen appears7 Click Finish to exit the wizard
Upgrade to Fireware v1213 fromWeb UIIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from theSystem gt Upgrade OS page If your Firebox is running v119x or earlier use thesesteps to upgrade
1 Before you begin save a local copy of your configuration file2 Go toSystem gt Backup Image or use the USB Backup feature to back up your current device image3 On your management computer launch the OS software file you downloaded from theWatchGuard
Software Downloads pageIf you use theWindows-based installer on a computer with aWindows 64-bit operating system thisinstallation extracts an upgrade file called [product series]_[product code]sysa-dl to the defaultlocation of CProgram Files(x86)Common FilesWatchGuardresourcesFirewareXTM1213[model]or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Connect to your Firebox with theWebUI and select System gt Upgrade OS5 Browse to the location of the [product series]_[product code]sysa-dl from Step 2 and click Upgrade
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v121 3installer twice (once to remove v1213 software and again to install v1213)
Upgrade to Fireware v1213
16 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 17
Upgrade to Fireware v1213 fromWSMPolicy Manager1 Before you begin save a local copy of your configuration file2 Select File gt Backup or use the USB Backup feature to back up your current device image3 On amanagement computer running aWindows 64-bit operating system launch the OS executable file
you downloaded from theWatchGuard Portal This installation extracts an upgrade file called [Firebox orxtm series]_[product code]sysa-dl to the default location of CProgram Files(x86)CommonfilesWatchGuardresourcesFirewareXTM1213[model] or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Install and openWatchGuard SystemManager v1213 Connect to your Firebox and launch PolicyManager
5 From Policy Manager select File gt Upgrade When prompted browse to and select the [productseries]_[product code]sysa-dl file from Step 2
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v1213installer twice (once to remove v1213 software and again to install v1213)
If you like tomake updates to your Firebox configuration from a saved configuration file makesure you open the configuration from the Firebox and save it to a new file after you upgradeThis is to make sure that you do not overwrite any configuration changes that weremade aspart of the upgrade
Other Upgrade IssuesThere is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Fireware v12x is not supported on XTM 5Series devices models 505 510 520 or 530
Before you upgrade to Fireware v12x your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is preventedIf you try to schedule anOS update of managed devices through aManagement Server theupgrade is also preventedIf you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x orv1110x before you upgrade to Fireware v12x or your Firebox will be reset to a default state
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
18 WatchGuard Technologies Inc
Update AP Devices
Release Notes 19
Update AP Devices
OnApril 12 2018 WatchGuard released AP firmware versions 12915 for the AP100 AP102and AP200 and 20010 for the AP300 to address security vulnerabilities We highlyrecommend you install these AP firmware updates For more detailed information on thesevulnerabilities see AP100AP102AP200 Chained Vulnerabilities In addition to addressingthese vulnerabilities the AP firmware updates disable the AP local web UI As these APmodels can only bemanaged with the Gateway Wireless Controller the AP local web UI is nolonger supported
Beginning with Fireware v11124 AP firmware is no longer bundled with Fireware OS All AP device firmwareis managed by the Gateway Wireless Controller on your Firebox TheGateway Wireless Controllerautomatically checks for new AP firmware updates and enables you to download the firmware directly fromWatchGuard servers
Important Upgrade StepsIf you have not previously upgraded to Fireware 1201 or higher and the latest AP firmware youmust performthese steps
1 Make sure all your APs are online You can check AP status from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager selecttheGateway Wireless Controller tab
2 Make sure you are not using insecure default AP passphrases such as wgwap orwatchguard Yourcurrent AP passphrasemust be secure and at least 8 characters in length You can change your APpassphrase inNetwork gt Gateway Wireless Controller gt Settings
If you do not have a secure passphrase correctly configured before the upgrade you will losethemanagement connection with your deployed APs If this occurs youmust physicallyreset the APs to factory default settings to be able tomanage the APs from GatewayWireless Controller
Depending on the version of Fireware you are upgrading from youmay need tomark APs as trusted after theupgrade to Fireware v1201 or higher You canmark APs as trusted from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager select theGateway Wireless Controller tab
AP Firmware UpgradeThe current AP firmware versions for each AP devicemodel are
AP Device Model Current Firmware Version
AP100 AP102 AP200 12915
AP300 20010
AP120 AP320 AP322 AP325AP420
850-646
Tomanage AP firmware and download the latest AP firmware to your Firebox
n From FirewareWebUI select Dashboard gt Gateway Wireless Controller From theSummary tabclick Manage Firmware
n From Firebox SystemManager select theGateway Wireless Controller tab then click ManageFirmware
Note that you cannot upgrade an AP120 AP320 AP322 or AP420 to 830-657 or higher unless your Firebox isrunning Fireware v11124 or higher If your Firebox does not run v11124 or higher you will not see an optionto upgrade to AP firmware v830-657 or higher
If you have enabled automatic AP device firmware updates in Gateway Wireless Controller your AP devicesare automatically updated betweenmidnight and 400am local time
Tomanually update firmware on your AP devices
1 On theAccess Points tab select one or more AP devices2 From theActions drop-down list click Upgrade3 Click Yes to confirm that you want to upgrade the AP device
Update AP Devices
20 WatchGuard Technologies Inc
Upgrade your FireCluster to Fireware v1213
Release Notes 21
Upgrade your FireCluster to Fireware v1213You can upgrade Fireware OS for a FireCluster from Policy Manager or FirewareWebUI To upgrade aFireCluster from Fireware v1110x or lower we recommend you use Policy Manager
As part of the upgrade process each cluster member reboots and rejoins the cluster Because the clustercannot do load balancing while a cluster member reboot is in progress we recommend you upgrade anactiveactive cluster at a time when the network traffic is lightest
For information on how to upgrade your FireCluster see this Help topic
There is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Before you upgrade to Fireware v1111 or higher your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is prevented
If you try to schedule anOS update of managed devices through aManagement Server theupgrade is also prevented
If you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x before youupgrade to Fireware v1111x or higher or your Firebox will be reset to a default state
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
Localization
Release Notes 3
LocalizationThis release includes localization update for themanagement user interfaces (WSM application suite andWebUI) current as of Fireware v120 UI changes introduced since v120may remain in English Supportedlanguages are
l French (France)l Japanesel Spanish (Latin American)
Note that most data input must still bemade using standard ASCII characters You can use non-ASCIIcharacters in some areas of the UI including
l Proxy deny messagel Wireless hotspot title terms and conditions andmessagel WatchGuard Server Center users groups and role names
Any data returned from the device operating system (eg log data) is displayed in English only Additionally allitems in theWebUI System Status menu and any software components provided by third-party companiesremain in English
Fireware Web UITheWebUI will launch in the language you have set in your web browser by default
WatchGuard System ManagerWhen you install WSM you can choose what language packs you want to install The language displayed inWSMwill match the language you select in your Microsoft Windows environment For example if you useWindows 7 and want to useWSM in Japanese go to Control Panel gt Regions and Languages and selectJapanese on the Keyboards and Languages tab as your Display Language
Dimension WebCenter Quarantine Web UI and Wireless HotspotThese web pages automatically display in whatever language preference you have set in your web browser
DocumentationLocalization updates are not yet available for Fireware Help
Important Information about Firebox CertificatesSHA-1 is being deprecated by many popular web browsers andWatchGuard recommends that you now useSHA-256 certificates Because of this we have upgraded our default Firebox certificates Starting withFireware v11104 all newly generated default Firebox certificates use a 2048-bit key length In addition newlygenerated default Proxy Server and Proxy Authority certificates use SHA-256 for their signature hashalgorithm Starting with Fireware v11105 all newly generated default Firebox certificates use SHA-256 fortheir signature hash algorithm New CSRs created from the Firebox also use SHA-256 for their signature hashalgorithm
Default certificates are not automatically upgraded after you install Fireware v11105 or later releases
To regenerate any default Firebox certificates delete the certificate and reboot the Firebox If you want toregenerate default certificates without a reboot you can use the CLI commands described in the next sectionBefore you regenerate the Proxy Server or Proxy Authority certification there are some important things toknow
The Proxy Server certificate is used for inbound HTTPS with content inspection and SMTP with TLSinspection The Proxy Authority certificate is used for outbound HTTPS with content inspection The twocertificates are linked because the default Proxy Server certificate is signed by the default Proxy Authoritycertificate If you use the CLI to regenerate these certificates after you upgrade youmust redistribute the newProxy Authority certificate to your clients or users will receive web browser warnings when they browseHTTPS sites if content inspection is enabled
Also if you use a third-party Proxy Server or Proxy Authority certificate
l The CLI commandwill not work unless you first delete either the Proxy Server or Proxy Authoritycertificate The CLI commandwill regenerate both the Proxy Server and Proxy Authority defaultcertificates
l If you originally used a third-party tool to create the CSR you can simply re-import your existing third-party certificate and private key
l If you originally created your CSR from the Firebox youmust create a new CSR to be signed and thenimport a new third-party certificate
CLI Commands to Regenerate Default Firebox CertificatesTo regenerate any default Firebox certificates delete the certificate and reboot the Firebox If you want toregenerate default certificates without a reboot you can use these CLI commands
l To upgrade the default Proxy Authority and Proxy Server certificates for use with HTTPS contentinspection you can use the CLI command upgrade certificate proxy
l To upgrade the Firebox web server certificate use the CLI command upgrade certificate webl To upgrade the SSLVPN certificate use the CLI command upgrade certificate sslvpnl To upgrade the 8021x certificate use the CLI command upgrade certificate 8021x
Formore information about the CLI see the Command Line Interface Reference
Important Information about Firebox Certificates
4 WatchGuard Technologies Inc
Fireware andWSM v1213 Operating System Compatibility
Release Notes 5
Fireware and WSM v1213 Operating System CompatibilityLast revised 12 December 2017
WSMFirewareComponent
MicrosoftWindows788110
(32-bitamp64-bit)
MicrosoftWindowsServer2012amp2012R2(64-bit)
MicrosoftWindowsServer2016(64-bit)
MacOSXmacOSv1010
v1011v1012ampv1013
Android6x
7x amp8x
iOSv8 v9v10 ampv11
WatchGuard SystemManager
WatchGuard Servers
For information onWatchGuardDimension see the Dimension ReleaseNotes
Single Sign-On Agent(Includes Event LogMonitor)1
Single Sign-On Client
Single Sign-On ExchangeMonitor2
Terminal Services Agent3
Mobile VPN with IPSec 4 4
Mobile VPN with SSL
Notes about Microsoft Windows supportl Windows 8x support does not includeWindows RT
The following browsers are supported for both FirewareWebUI andWebCenter (Javascript required)l IE 11 and laterl Microsoft Edgel Firefox v55l Safari 10l Safari iOS 10l Chrome v60
1The Server Core installation option is supported forWindows Server 20162Microsoft Exchange Server 2007 and 2010 are supported Microsoft Exchange Server 2013 is supported if youinstall Windows Server 2012 or 2012 R2 and NET Framework 353Terminal Services support with manual or Single Sign-On authentication operates in aMicrosoft TerminalServices or Citrix XenApp 45 50 60 65 76 or 712 environment4Native (Cisco) IPSec client andOpenVPN are supported for all recent versions of Mac OS and iOS To useTheWatchGuardMobile VPN with IPSec client with OS 1013 youmust upgrade to the v300 client release
Authentication SupportThis table gives you a quick view of the types of authentication servers supported by key features of FirewareUsing an authentication server gives you the ability to configure user and group-based firewall and VPN policiesin your Firebox or XTM device configuration With each type of third-party authentication server supported youcan specify a backup server IP address for failover
Fully supported by WatchGuard Not yet supported but tested with success by WatchGuardcustomers
Fireware andWSM v1213 Operating System Compatibility
6 WatchGuard Technologies Inc
Fireware andWSM v1213 Operating System Compatibility
Release Notes 7
ActiveDirectory
1 LDAPRADIUS
2SecurID
2
Firebox(Firebox-DB)
LocalAuthentication
Mobile VPN with IPSecShrew Soft 3 ndash
Mobile VPN withIPSecWatchGuard client (NCP)
Mobile VPN with IPSec for iOS andMacOS X native VPN client
Mobile VPN with IPSec for Androiddevices
ndash
Mobile VPN with SSL forWindows 4 4
Mobile VPN with SSL for Mac
Mobile VPN with SSL for iOS andAndroid devices
Mobile VPN with L2TP 6 ndash ndash
Built-in AuthenticationWeb Page onPort 4100
Single Sign-On Support (with or withoutclient software)
ndash ndash ndash
Terminal Services ManualAuthentication
Terminal Services Authentication withSingle Sign-On
5 ndash ndash ndash ndash
Citrix Manual Authentication
Citrix Manual Authentication with SingleSign-On
5 ndash ndash ndash ndash
1 Active Directory support includes both single domain and multi-domain support unless otherwise noted2 RADIUS and SecurID support includes support for both one-time passphrases and challengeresponse
authentication integrated with RADIUS In many cases SecurID can also be used with other RADIUSimplementations including Vasco
3 The Shrew Soft client does not support two-factor authentication4 Fireware supports RADIUS Filter ID 11 for group authentication5 Both single and multiple domain Active Directory configurations are supported For information about the
supported Operating System compatibility for the WatchGuard TO Agent and SSO Agent see the currentFireware and WSM Operating System Compatibility table
6 Active Directory authentication methods are supported only through a RADIUS server
System RequirementsIf you have WatchGuard SystemManager client software onlyinstalled
If you install WatchGuard SystemManager and WatchGuard Serversoftware
Minimum CPU Intel Core or Xeon
2GHz
Intel Core or Xeon
2GHz
MinimumMemory 1GB 2GB
Minimum AvailableDisk Space
250MB 1GB
MinimumRecommendedScreen Resolution
1024x768 1024x768
FireboxV System RequirementsWith support for installation in both a VMware and a Hyper-V environment aWatchGuard FireboxV virtualmachine can run on a VMware ESXi 55 60 or 65 host or onWindows Server 2012 R2 or 2016 or Hyper-VServer 2012 R2 or 2016
The hardware requirements for FireboxV are the same as for the hypervisor environment it runs in
Each FireboxV virtual machine requires 5 GB of disk space CPU andmemory requirements vary by model
FireboxV Model vCPUs (maximum) Memory (recommended)
Small 2 2048MB
Medium 4 4096MB
Large 8 4096MB
Extra Large 16 4096MB
System requirements for XTMv are included in Fireware Help
Fireware andWSM v1213 Operating System Compatibility
8 WatchGuard Technologies Inc
Downloading Software
Release Notes 9
Downloading SoftwareYou can download software from theWatchGuard Software Downloads Center
There are several software files available for download with this release See the descriptions below so youknow what software packages you will need for your upgrade
WatchGuard System ManagerWith this software package you can install WSM and theWatchGuard Server Center software
WSM12_1_3exemdashUse this file to install WSM v1213 or to upgradeWatchGuard SystemManagerfrom an earlier version toWSM v1213
Fireware OSIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from the FirewareWebUI System gt Upgrade OS page
If you prefer to upgrade from Policy Manager or from an earlier version of Fireware you can use download theFireware OS image for your Firebox or XTM device Use the exe file if you want to install or upgrade theOSusingWSM Use the zip file if you want to install or upgrade theOS manually using FirewareWebUI Use theova or vhd file to deploy a new XTMv device
If you havehellip Select from these Fireware OS packages
Firebox M5600 Firebox_OS_M4600_M5600_12_1_3exefirebox_M4600_M5600_12_1_3zip
Firebox M4600 Firebox_OS_M4600_M5600_12_1_3exefirebox_M4600_M5600_12_1_3zip
Firebox M670 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M570 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M500 Firebox_OS_M400_M500_12_1_3exefirebox_M400_M500_12_1_3zip
Firebox M470 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M440 Firebox_OS_M440_12_1_3exefirebox_M440_12_1_3zip
Firebox M400 Firebox_OS_M400_M500_12_1_3exefirebox_M400_M500_12_1_3zip
Firebox M370 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M300 Firebox_OS_M200_M300_12_1_3exefirebox_M200_M300_12_1_3zip
Firebox M200 Firebox_OS_M200_M300_12_1_3exefirebox_M200_M300_12_1_3zip
Firebox T70 Firebox_OS_T70_12_1_3exefirebox_T70_12_1_3zip
Firebox T55 Firebox_OS_T55_12_1_3exefirebox_T55_12_1_3zip
Firebox T50 Firebox_OS_T30_T50_12_1_3exefirebox_T30_T50_12_1_3zip
Firebox T35 Firebox_OS_T35_12_1_3exefirebox_T35_12_1_3zip
Firebox T30 Firebox_OS_T30_T50_12_1_3exefirebox_T30_T50_12_1_3zip
Firebox T15 Firebox_OS_T15_12_1_3exefirebox_T15_12_1_3zip
Firebox T10 Firebox_OS_T10_12_1_3exefirebox_T10_12_1_3zip
Downloading Software
10 WatchGuard Technologies Inc
Downloading Software
Release Notes 11
If you havehellip Select from these Fireware OS packages
FireboxVAll editions for VMware
FireboxV_12_1_3ovaXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
FireboxVAll editions for Hyper-V
FireboxV_12_1_3_vhdzipXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
Firebox Cloud FireboxCloud_12_1_3zip
XTM 2500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 2050 XTM_OS_XTM2050_12_1_3exextm_xtm2050_12_1_3zip
XTM 1500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 1050 XTM_OS_XTM1050_12_1_3exextm_xtm1050_12_1_3zip
XTM 800 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 8Series XTM_OS_XTM8_12_1_3exextm_xtm8_12_1_3zip
XTM 5Series Models515 525 535 and 545only
XTM_OS_XTM5_12_1_3exextm_xtm5_12_1_3zip
XTM 330 XTM_OS_XTM330_12_1_3exextm_xtm330_12_1_3zip
XTM 33 XTM_OS_XTM3_12_1_3exextm_xtm3_12_1_3zip
XTM 2526 XTM_OS_XTM2A6_12_1_3exextm_xtm2a6_12_1_3zip
XTMvAll editions for VMware
xtmv_12_1_3ovaXTM_OS_xtmv_12_1_3exextm_xtmv_12_1_3zip
XTMvAll editions for Hyper-V
xtmv_12_1_3_vhdzipXTM_OS_XTMv_12_1_3exextm_xtmv_12_1_3zip
Single Sign-On SoftwareThese files are available for Single Sign-On There are no updates with the v1213 release
l WG-Authentication-Gateway_12_0exe (SSOAgent software - required for Single Sign-On andincludes optional Event LogMonitor for clientless SSO)
l WG-Authentication-Client_11122msi (SSOClient software forWindows)l WG-SSOCLIENT-MAC_12_0dmg (SSOClient software for Mac OS X)l SSOExchangeMonitor_x86_12_0exe (ExchangeMonitor for 32-bit operating systems)l SSOExchangeMonitor_x64_12_0exe (ExchangeMonitor for 64-bit operating systems)
For information about how to install and set up Single Sign-On see the product documentation
Terminal Services Authentication SoftwareThis file is not updated with the Fireware v1213 release
l TO_AGENT_SETUP_11_12exe (This installer includes both 32-bit and 64-bit file support)
Mobile VPN with SSL Client for Windows and MacThere are two files available for download if you useMobile VPN with SSL
l WG-MVPN-SSL_12_0exe (Client software forWindows)l WG-MVPN-SSL_12_0dmg (Client software for Mac)
Mobile VPN with IPSec client for Windows and MacThere are several available files to download
Shrew Soft Client
l Shrew Soft Client 222 for Windows - No client license required
WatchGuard IPSec Mobile VPN Clients
The current WatchGuard IPSec Mobile VPN Client forWindows version is 1213
l WatchGuard IPSec Mobile VPN Client for Windows (32-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
l WatchGuard IPSec Mobile VPN Client for Windows (64-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
The current macOS client version is 300
l WatchGuard IPSec Mobile VPN Client for macOS powered by NCP - There is a license requiredfor this premium client with a 30-day free trial available with download
WatchGuard Mobile VPN License Server
l WatchGuard Mobile VPN License Server (MVLS) v20 powered by NCP- Click here for moreinformation about MVLS If you have a VPN bundle ID for macOS it must be updated on the licenseserver to support the new macOS 300 client To update your bundle ID contact WatchGuard CustomerSupport Make sure to have your existing bundle ID available to expedite the update
Downloading Software
12 WatchGuard Technologies Inc
Upgrade Notes
Release Notes 13
Upgrade Notes
SSLTLS Settings Precedence and InheritanceFour Firebox features use SSLTLS for secure communication and share the sameOpenVPN serverManagement Tunnel over SSL on hub devices BOVPN over TLS in Server mode Mobile VPN with SSL andthe Access Portal These features also share some settings When you enablemore than one of thesefeatures settings for some features have a higher precedence than settings for other features Shared settingsare not configurable for the features with lower precedence For more information see this topic in FirewareHelp
Modem Configurations Converted to External Interfaces with Failover EnabledIf your Firebox was configured for modem failover when you upgrade your Firebox to Fireware v121 or higherthemodem configuration is automatically converted to an external interface with modem failover enabled If allother external interfaces become unavailable traffic automatically fails over to themodem interface Modeminterfaces can also participate in multi-WAN on all devices except the Firebox T10 Firebox T15 and XTM 2Series devices that do not have the Pro upgrade
HTTPS Proxy Content Inspection with Fireware v121With Fireware 121 we updated the HTTPS proxy action to include a Content Inspection Exceptions list whichincludes domains for services such as Dropbox Skype andMicrosoft Office that are known to be incompatiblewith content inspection The HTTPS proxy does not perform content inspection for domains with enabledexceptions on the Content Inspection Exceptions list
When you upgrade your Firebox to Fireware v121 or higher the Content Inspection Exceptions list isautomatically enabled in all HTTPS proxy actions that have content inspection enabled After the upgrade werecommend that you review the Content Inspection Exceptions list in your configured HTTPS proxy actionsand disable the exception for any domain you do not want the HTTPS proxy to allow without content inspectionFor more information seeWhich applications are on the default exception list in an HTTPS proxy action in theKnowledge Base
Gateway AV Engine Upgrade with Fireware v120With Fireware v120 we updated the engine used by Gateway AV to a new engine from BitDefender As aresult any Firebox that upgrades from Fireware v11x version to v120 or later must download a new signatureset which can take 7-10minutes for the first update It can take an additional 5-7minutes to synchronize aFireCluster We recommend that you upgrade to Fireware v12x at a quiet time on your network After the initialupdate signature updates are incremental andmuch faster than in previous versions
While the new signature set is being downloaded network users could experience issues related to GatewayAV scan failures for several minutes after the update and inbound emails sent through the SMTP proxy couldbe locked
XTMv Upgrade NotesYou cannot upgrade an XTMv device to FireboxV For Fireware v1111 and higher the XTMv device is a 64-bitvirtual machine You cannot upgrade an XTMv device from Fireware v1110x or lower to Fireware v1111 orhigher Instead youmust use the OVA file to deploy a new 64-bit Fireware v1111x or v12x XTMv VM andthen use Policy Manager to move the existing configuration from the 32-bit XTMv VM to the 64-bit XTMv VMFor more information about how tomove the configuration or deploy a new XTMv VM see Fireware Help Whenyour XTMv instance has been updated to v1111 or higher you can then use the usual upgrade procedure asdetailed in the next section
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
If your Firebox is a T10 XTM 25 or XTM 26 device with OS version 121 or older youmightnot be able to perform a backup before you upgrade the Firebox This occurs because thememory use by Fireware v121 or older does not leave enoughmemory free to successfullycomplete the upgrade process on these devices For these devices we recommend you savea copy of the xml configuration file with a distinctive name as described here Save theConfiguration File
If you need to downgrade a Firebox without a backup file after you complete the upgrade toFireware v12x we recommend you Downgrade withWebUI This process deletes theconfiguration file but does not remove the device feature keys and certificates After youdowngrade the Firebox you can use Policy Manager to Save the Configuration File to theFireboxIf your Firebox has Fireware v1211 or later the Firebox will temporarily disable somesecurity services to free up enoughmemory to successfully perform a backup To learnmoresee Backup and Restore for XTM 25 XTM 26 and Firebox T10
Important Information about the upgrade process
l We recommend you use FirewareWebUI to upgrade to Fireware v12x You can also use PolicyManager if you prefer
l We strongly recommend that you save a local copy of your Firebox configuration and create a Fireboxbackup image before you upgrade
l If you useWatchGuard SystemManager (WSM) make sure yourWSM version is equal to or higherthan the version of Fireware OS installed on your Firebox and the version of WSM installed on yourManagement Server Also make sure to upgradeWSM before you upgrade the version of Fireware OSon your Firebox
Upgrade to Fireware v1213
14 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 15
If you want to upgrade a Firebox T10 XTM 2Series 33 330 or 5 Series device werecommend that you reboot your Firebox before you upgrade This clears your devicememoryand can prevent many problems commonly associated with upgrades in those devices
Back Up Your WatchGuard ServersIt is not usually necessary to uninstall your previous v11x or v12x server or client software when you upgradetoWSM v12x You can install the v12x server and client software on top of your existing installation toupgrade yourWatchGuard software components We do however strongly recommend that you back up yourWatchGuard Servers (for example yourWatchGuardManagement Server) to a safe location before youupgrade You will need these backup files if you ever want to downgrade
You cannot restore aWatchGuard Server backup file created withWatchGuard SystemManager v12x to to a v11x installation Make sure to retain your older server backup fileswhen you upgrade to v120 or later in case you want to downgrade in the future
To back up your Management Server configuration from the computer where you installed theManagementServer
1 FromWatchGuard Server Center select BackupRestore Management ServerThe WatchGuard Server Center BackupRestore Wizard starts
2 Click NextThe Select an action screen appears
3 Select Back up settings4 Click Next
The Specify a backup file screen appears5 Click Browse to select a location for the backup file Make sure you save the configuration file to a
location you can access later to restore the configuration6 Click Next
The WatchGuard Server Center BackupRestore Wizard is complete screen appears7 Click Finish to exit the wizard
Upgrade to Fireware v1213 fromWeb UIIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from theSystem gt Upgrade OS page If your Firebox is running v119x or earlier use thesesteps to upgrade
1 Before you begin save a local copy of your configuration file2 Go toSystem gt Backup Image or use the USB Backup feature to back up your current device image3 On your management computer launch the OS software file you downloaded from theWatchGuard
Software Downloads pageIf you use theWindows-based installer on a computer with aWindows 64-bit operating system thisinstallation extracts an upgrade file called [product series]_[product code]sysa-dl to the defaultlocation of CProgram Files(x86)Common FilesWatchGuardresourcesFirewareXTM1213[model]or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Connect to your Firebox with theWebUI and select System gt Upgrade OS5 Browse to the location of the [product series]_[product code]sysa-dl from Step 2 and click Upgrade
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v121 3installer twice (once to remove v1213 software and again to install v1213)
Upgrade to Fireware v1213
16 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 17
Upgrade to Fireware v1213 fromWSMPolicy Manager1 Before you begin save a local copy of your configuration file2 Select File gt Backup or use the USB Backup feature to back up your current device image3 On amanagement computer running aWindows 64-bit operating system launch the OS executable file
you downloaded from theWatchGuard Portal This installation extracts an upgrade file called [Firebox orxtm series]_[product code]sysa-dl to the default location of CProgram Files(x86)CommonfilesWatchGuardresourcesFirewareXTM1213[model] or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Install and openWatchGuard SystemManager v1213 Connect to your Firebox and launch PolicyManager
5 From Policy Manager select File gt Upgrade When prompted browse to and select the [productseries]_[product code]sysa-dl file from Step 2
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v1213installer twice (once to remove v1213 software and again to install v1213)
If you like tomake updates to your Firebox configuration from a saved configuration file makesure you open the configuration from the Firebox and save it to a new file after you upgradeThis is to make sure that you do not overwrite any configuration changes that weremade aspart of the upgrade
Other Upgrade IssuesThere is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Fireware v12x is not supported on XTM 5Series devices models 505 510 520 or 530
Before you upgrade to Fireware v12x your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is preventedIf you try to schedule anOS update of managed devices through aManagement Server theupgrade is also preventedIf you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x orv1110x before you upgrade to Fireware v12x or your Firebox will be reset to a default state
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
18 WatchGuard Technologies Inc
Update AP Devices
Release Notes 19
Update AP Devices
OnApril 12 2018 WatchGuard released AP firmware versions 12915 for the AP100 AP102and AP200 and 20010 for the AP300 to address security vulnerabilities We highlyrecommend you install these AP firmware updates For more detailed information on thesevulnerabilities see AP100AP102AP200 Chained Vulnerabilities In addition to addressingthese vulnerabilities the AP firmware updates disable the AP local web UI As these APmodels can only bemanaged with the Gateway Wireless Controller the AP local web UI is nolonger supported
Beginning with Fireware v11124 AP firmware is no longer bundled with Fireware OS All AP device firmwareis managed by the Gateway Wireless Controller on your Firebox TheGateway Wireless Controllerautomatically checks for new AP firmware updates and enables you to download the firmware directly fromWatchGuard servers
Important Upgrade StepsIf you have not previously upgraded to Fireware 1201 or higher and the latest AP firmware youmust performthese steps
1 Make sure all your APs are online You can check AP status from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager selecttheGateway Wireless Controller tab
2 Make sure you are not using insecure default AP passphrases such as wgwap orwatchguard Yourcurrent AP passphrasemust be secure and at least 8 characters in length You can change your APpassphrase inNetwork gt Gateway Wireless Controller gt Settings
If you do not have a secure passphrase correctly configured before the upgrade you will losethemanagement connection with your deployed APs If this occurs youmust physicallyreset the APs to factory default settings to be able tomanage the APs from GatewayWireless Controller
Depending on the version of Fireware you are upgrading from youmay need tomark APs as trusted after theupgrade to Fireware v1201 or higher You canmark APs as trusted from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager select theGateway Wireless Controller tab
AP Firmware UpgradeThe current AP firmware versions for each AP devicemodel are
AP Device Model Current Firmware Version
AP100 AP102 AP200 12915
AP300 20010
AP120 AP320 AP322 AP325AP420
850-646
Tomanage AP firmware and download the latest AP firmware to your Firebox
n From FirewareWebUI select Dashboard gt Gateway Wireless Controller From theSummary tabclick Manage Firmware
n From Firebox SystemManager select theGateway Wireless Controller tab then click ManageFirmware
Note that you cannot upgrade an AP120 AP320 AP322 or AP420 to 830-657 or higher unless your Firebox isrunning Fireware v11124 or higher If your Firebox does not run v11124 or higher you will not see an optionto upgrade to AP firmware v830-657 or higher
If you have enabled automatic AP device firmware updates in Gateway Wireless Controller your AP devicesare automatically updated betweenmidnight and 400am local time
Tomanually update firmware on your AP devices
1 On theAccess Points tab select one or more AP devices2 From theActions drop-down list click Upgrade3 Click Yes to confirm that you want to upgrade the AP device
Update AP Devices
20 WatchGuard Technologies Inc
Upgrade your FireCluster to Fireware v1213
Release Notes 21
Upgrade your FireCluster to Fireware v1213You can upgrade Fireware OS for a FireCluster from Policy Manager or FirewareWebUI To upgrade aFireCluster from Fireware v1110x or lower we recommend you use Policy Manager
As part of the upgrade process each cluster member reboots and rejoins the cluster Because the clustercannot do load balancing while a cluster member reboot is in progress we recommend you upgrade anactiveactive cluster at a time when the network traffic is lightest
For information on how to upgrade your FireCluster see this Help topic
There is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Before you upgrade to Fireware v1111 or higher your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is prevented
If you try to schedule anOS update of managed devices through aManagement Server theupgrade is also prevented
If you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x before youupgrade to Fireware v1111x or higher or your Firebox will be reset to a default state
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
To regenerate any default Firebox certificates delete the certificate and reboot the Firebox If you want toregenerate default certificates without a reboot you can use the CLI commands described in the next sectionBefore you regenerate the Proxy Server or Proxy Authority certification there are some important things toknow
The Proxy Server certificate is used for inbound HTTPS with content inspection and SMTP with TLSinspection The Proxy Authority certificate is used for outbound HTTPS with content inspection The twocertificates are linked because the default Proxy Server certificate is signed by the default Proxy Authoritycertificate If you use the CLI to regenerate these certificates after you upgrade youmust redistribute the newProxy Authority certificate to your clients or users will receive web browser warnings when they browseHTTPS sites if content inspection is enabled
Also if you use a third-party Proxy Server or Proxy Authority certificate
l The CLI commandwill not work unless you first delete either the Proxy Server or Proxy Authoritycertificate The CLI commandwill regenerate both the Proxy Server and Proxy Authority defaultcertificates
l If you originally used a third-party tool to create the CSR you can simply re-import your existing third-party certificate and private key
l If you originally created your CSR from the Firebox youmust create a new CSR to be signed and thenimport a new third-party certificate
CLI Commands to Regenerate Default Firebox CertificatesTo regenerate any default Firebox certificates delete the certificate and reboot the Firebox If you want toregenerate default certificates without a reboot you can use these CLI commands
l To upgrade the default Proxy Authority and Proxy Server certificates for use with HTTPS contentinspection you can use the CLI command upgrade certificate proxy
l To upgrade the Firebox web server certificate use the CLI command upgrade certificate webl To upgrade the SSLVPN certificate use the CLI command upgrade certificate sslvpnl To upgrade the 8021x certificate use the CLI command upgrade certificate 8021x
Formore information about the CLI see the Command Line Interface Reference
Important Information about Firebox Certificates
4 WatchGuard Technologies Inc
Fireware andWSM v1213 Operating System Compatibility
Release Notes 5
Fireware and WSM v1213 Operating System CompatibilityLast revised 12 December 2017
WSMFirewareComponent
MicrosoftWindows788110
(32-bitamp64-bit)
MicrosoftWindowsServer2012amp2012R2(64-bit)
MicrosoftWindowsServer2016(64-bit)
MacOSXmacOSv1010
v1011v1012ampv1013
Android6x
7x amp8x
iOSv8 v9v10 ampv11
WatchGuard SystemManager
WatchGuard Servers
For information onWatchGuardDimension see the Dimension ReleaseNotes
Single Sign-On Agent(Includes Event LogMonitor)1
Single Sign-On Client
Single Sign-On ExchangeMonitor2
Terminal Services Agent3
Mobile VPN with IPSec 4 4
Mobile VPN with SSL
Notes about Microsoft Windows supportl Windows 8x support does not includeWindows RT
The following browsers are supported for both FirewareWebUI andWebCenter (Javascript required)l IE 11 and laterl Microsoft Edgel Firefox v55l Safari 10l Safari iOS 10l Chrome v60
1The Server Core installation option is supported forWindows Server 20162Microsoft Exchange Server 2007 and 2010 are supported Microsoft Exchange Server 2013 is supported if youinstall Windows Server 2012 or 2012 R2 and NET Framework 353Terminal Services support with manual or Single Sign-On authentication operates in aMicrosoft TerminalServices or Citrix XenApp 45 50 60 65 76 or 712 environment4Native (Cisco) IPSec client andOpenVPN are supported for all recent versions of Mac OS and iOS To useTheWatchGuardMobile VPN with IPSec client with OS 1013 youmust upgrade to the v300 client release
Authentication SupportThis table gives you a quick view of the types of authentication servers supported by key features of FirewareUsing an authentication server gives you the ability to configure user and group-based firewall and VPN policiesin your Firebox or XTM device configuration With each type of third-party authentication server supported youcan specify a backup server IP address for failover
Fully supported by WatchGuard Not yet supported but tested with success by WatchGuardcustomers
Fireware andWSM v1213 Operating System Compatibility
6 WatchGuard Technologies Inc
Fireware andWSM v1213 Operating System Compatibility
Release Notes 7
ActiveDirectory
1 LDAPRADIUS
2SecurID
2
Firebox(Firebox-DB)
LocalAuthentication
Mobile VPN with IPSecShrew Soft 3 ndash
Mobile VPN withIPSecWatchGuard client (NCP)
Mobile VPN with IPSec for iOS andMacOS X native VPN client
Mobile VPN with IPSec for Androiddevices
ndash
Mobile VPN with SSL forWindows 4 4
Mobile VPN with SSL for Mac
Mobile VPN with SSL for iOS andAndroid devices
Mobile VPN with L2TP 6 ndash ndash
Built-in AuthenticationWeb Page onPort 4100
Single Sign-On Support (with or withoutclient software)
ndash ndash ndash
Terminal Services ManualAuthentication
Terminal Services Authentication withSingle Sign-On
5 ndash ndash ndash ndash
Citrix Manual Authentication
Citrix Manual Authentication with SingleSign-On
5 ndash ndash ndash ndash
1 Active Directory support includes both single domain and multi-domain support unless otherwise noted2 RADIUS and SecurID support includes support for both one-time passphrases and challengeresponse
authentication integrated with RADIUS In many cases SecurID can also be used with other RADIUSimplementations including Vasco
3 The Shrew Soft client does not support two-factor authentication4 Fireware supports RADIUS Filter ID 11 for group authentication5 Both single and multiple domain Active Directory configurations are supported For information about the
supported Operating System compatibility for the WatchGuard TO Agent and SSO Agent see the currentFireware and WSM Operating System Compatibility table
6 Active Directory authentication methods are supported only through a RADIUS server
System RequirementsIf you have WatchGuard SystemManager client software onlyinstalled
If you install WatchGuard SystemManager and WatchGuard Serversoftware
Minimum CPU Intel Core or Xeon
2GHz
Intel Core or Xeon
2GHz
MinimumMemory 1GB 2GB
Minimum AvailableDisk Space
250MB 1GB
MinimumRecommendedScreen Resolution
1024x768 1024x768
FireboxV System RequirementsWith support for installation in both a VMware and a Hyper-V environment aWatchGuard FireboxV virtualmachine can run on a VMware ESXi 55 60 or 65 host or onWindows Server 2012 R2 or 2016 or Hyper-VServer 2012 R2 or 2016
The hardware requirements for FireboxV are the same as for the hypervisor environment it runs in
Each FireboxV virtual machine requires 5 GB of disk space CPU andmemory requirements vary by model
FireboxV Model vCPUs (maximum) Memory (recommended)
Small 2 2048MB
Medium 4 4096MB
Large 8 4096MB
Extra Large 16 4096MB
System requirements for XTMv are included in Fireware Help
Fireware andWSM v1213 Operating System Compatibility
8 WatchGuard Technologies Inc
Downloading Software
Release Notes 9
Downloading SoftwareYou can download software from theWatchGuard Software Downloads Center
There are several software files available for download with this release See the descriptions below so youknow what software packages you will need for your upgrade
WatchGuard System ManagerWith this software package you can install WSM and theWatchGuard Server Center software
WSM12_1_3exemdashUse this file to install WSM v1213 or to upgradeWatchGuard SystemManagerfrom an earlier version toWSM v1213
Fireware OSIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from the FirewareWebUI System gt Upgrade OS page
If you prefer to upgrade from Policy Manager or from an earlier version of Fireware you can use download theFireware OS image for your Firebox or XTM device Use the exe file if you want to install or upgrade theOSusingWSM Use the zip file if you want to install or upgrade theOS manually using FirewareWebUI Use theova or vhd file to deploy a new XTMv device
If you havehellip Select from these Fireware OS packages
Firebox M5600 Firebox_OS_M4600_M5600_12_1_3exefirebox_M4600_M5600_12_1_3zip
Firebox M4600 Firebox_OS_M4600_M5600_12_1_3exefirebox_M4600_M5600_12_1_3zip
Firebox M670 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M570 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M500 Firebox_OS_M400_M500_12_1_3exefirebox_M400_M500_12_1_3zip
Firebox M470 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M440 Firebox_OS_M440_12_1_3exefirebox_M440_12_1_3zip
Firebox M400 Firebox_OS_M400_M500_12_1_3exefirebox_M400_M500_12_1_3zip
Firebox M370 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M300 Firebox_OS_M200_M300_12_1_3exefirebox_M200_M300_12_1_3zip
Firebox M200 Firebox_OS_M200_M300_12_1_3exefirebox_M200_M300_12_1_3zip
Firebox T70 Firebox_OS_T70_12_1_3exefirebox_T70_12_1_3zip
Firebox T55 Firebox_OS_T55_12_1_3exefirebox_T55_12_1_3zip
Firebox T50 Firebox_OS_T30_T50_12_1_3exefirebox_T30_T50_12_1_3zip
Firebox T35 Firebox_OS_T35_12_1_3exefirebox_T35_12_1_3zip
Firebox T30 Firebox_OS_T30_T50_12_1_3exefirebox_T30_T50_12_1_3zip
Firebox T15 Firebox_OS_T15_12_1_3exefirebox_T15_12_1_3zip
Firebox T10 Firebox_OS_T10_12_1_3exefirebox_T10_12_1_3zip
Downloading Software
10 WatchGuard Technologies Inc
Downloading Software
Release Notes 11
If you havehellip Select from these Fireware OS packages
FireboxVAll editions for VMware
FireboxV_12_1_3ovaXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
FireboxVAll editions for Hyper-V
FireboxV_12_1_3_vhdzipXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
Firebox Cloud FireboxCloud_12_1_3zip
XTM 2500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 2050 XTM_OS_XTM2050_12_1_3exextm_xtm2050_12_1_3zip
XTM 1500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 1050 XTM_OS_XTM1050_12_1_3exextm_xtm1050_12_1_3zip
XTM 800 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 8Series XTM_OS_XTM8_12_1_3exextm_xtm8_12_1_3zip
XTM 5Series Models515 525 535 and 545only
XTM_OS_XTM5_12_1_3exextm_xtm5_12_1_3zip
XTM 330 XTM_OS_XTM330_12_1_3exextm_xtm330_12_1_3zip
XTM 33 XTM_OS_XTM3_12_1_3exextm_xtm3_12_1_3zip
XTM 2526 XTM_OS_XTM2A6_12_1_3exextm_xtm2a6_12_1_3zip
XTMvAll editions for VMware
xtmv_12_1_3ovaXTM_OS_xtmv_12_1_3exextm_xtmv_12_1_3zip
XTMvAll editions for Hyper-V
xtmv_12_1_3_vhdzipXTM_OS_XTMv_12_1_3exextm_xtmv_12_1_3zip
Single Sign-On SoftwareThese files are available for Single Sign-On There are no updates with the v1213 release
l WG-Authentication-Gateway_12_0exe (SSOAgent software - required for Single Sign-On andincludes optional Event LogMonitor for clientless SSO)
l WG-Authentication-Client_11122msi (SSOClient software forWindows)l WG-SSOCLIENT-MAC_12_0dmg (SSOClient software for Mac OS X)l SSOExchangeMonitor_x86_12_0exe (ExchangeMonitor for 32-bit operating systems)l SSOExchangeMonitor_x64_12_0exe (ExchangeMonitor for 64-bit operating systems)
For information about how to install and set up Single Sign-On see the product documentation
Terminal Services Authentication SoftwareThis file is not updated with the Fireware v1213 release
l TO_AGENT_SETUP_11_12exe (This installer includes both 32-bit and 64-bit file support)
Mobile VPN with SSL Client for Windows and MacThere are two files available for download if you useMobile VPN with SSL
l WG-MVPN-SSL_12_0exe (Client software forWindows)l WG-MVPN-SSL_12_0dmg (Client software for Mac)
Mobile VPN with IPSec client for Windows and MacThere are several available files to download
Shrew Soft Client
l Shrew Soft Client 222 for Windows - No client license required
WatchGuard IPSec Mobile VPN Clients
The current WatchGuard IPSec Mobile VPN Client forWindows version is 1213
l WatchGuard IPSec Mobile VPN Client for Windows (32-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
l WatchGuard IPSec Mobile VPN Client for Windows (64-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
The current macOS client version is 300
l WatchGuard IPSec Mobile VPN Client for macOS powered by NCP - There is a license requiredfor this premium client with a 30-day free trial available with download
WatchGuard Mobile VPN License Server
l WatchGuard Mobile VPN License Server (MVLS) v20 powered by NCP- Click here for moreinformation about MVLS If you have a VPN bundle ID for macOS it must be updated on the licenseserver to support the new macOS 300 client To update your bundle ID contact WatchGuard CustomerSupport Make sure to have your existing bundle ID available to expedite the update
Downloading Software
12 WatchGuard Technologies Inc
Upgrade Notes
Release Notes 13
Upgrade Notes
SSLTLS Settings Precedence and InheritanceFour Firebox features use SSLTLS for secure communication and share the sameOpenVPN serverManagement Tunnel over SSL on hub devices BOVPN over TLS in Server mode Mobile VPN with SSL andthe Access Portal These features also share some settings When you enablemore than one of thesefeatures settings for some features have a higher precedence than settings for other features Shared settingsare not configurable for the features with lower precedence For more information see this topic in FirewareHelp
Modem Configurations Converted to External Interfaces with Failover EnabledIf your Firebox was configured for modem failover when you upgrade your Firebox to Fireware v121 or higherthemodem configuration is automatically converted to an external interface with modem failover enabled If allother external interfaces become unavailable traffic automatically fails over to themodem interface Modeminterfaces can also participate in multi-WAN on all devices except the Firebox T10 Firebox T15 and XTM 2Series devices that do not have the Pro upgrade
HTTPS Proxy Content Inspection with Fireware v121With Fireware 121 we updated the HTTPS proxy action to include a Content Inspection Exceptions list whichincludes domains for services such as Dropbox Skype andMicrosoft Office that are known to be incompatiblewith content inspection The HTTPS proxy does not perform content inspection for domains with enabledexceptions on the Content Inspection Exceptions list
When you upgrade your Firebox to Fireware v121 or higher the Content Inspection Exceptions list isautomatically enabled in all HTTPS proxy actions that have content inspection enabled After the upgrade werecommend that you review the Content Inspection Exceptions list in your configured HTTPS proxy actionsand disable the exception for any domain you do not want the HTTPS proxy to allow without content inspectionFor more information seeWhich applications are on the default exception list in an HTTPS proxy action in theKnowledge Base
Gateway AV Engine Upgrade with Fireware v120With Fireware v120 we updated the engine used by Gateway AV to a new engine from BitDefender As aresult any Firebox that upgrades from Fireware v11x version to v120 or later must download a new signatureset which can take 7-10minutes for the first update It can take an additional 5-7minutes to synchronize aFireCluster We recommend that you upgrade to Fireware v12x at a quiet time on your network After the initialupdate signature updates are incremental andmuch faster than in previous versions
While the new signature set is being downloaded network users could experience issues related to GatewayAV scan failures for several minutes after the update and inbound emails sent through the SMTP proxy couldbe locked
XTMv Upgrade NotesYou cannot upgrade an XTMv device to FireboxV For Fireware v1111 and higher the XTMv device is a 64-bitvirtual machine You cannot upgrade an XTMv device from Fireware v1110x or lower to Fireware v1111 orhigher Instead youmust use the OVA file to deploy a new 64-bit Fireware v1111x or v12x XTMv VM andthen use Policy Manager to move the existing configuration from the 32-bit XTMv VM to the 64-bit XTMv VMFor more information about how tomove the configuration or deploy a new XTMv VM see Fireware Help Whenyour XTMv instance has been updated to v1111 or higher you can then use the usual upgrade procedure asdetailed in the next section
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
If your Firebox is a T10 XTM 25 or XTM 26 device with OS version 121 or older youmightnot be able to perform a backup before you upgrade the Firebox This occurs because thememory use by Fireware v121 or older does not leave enoughmemory free to successfullycomplete the upgrade process on these devices For these devices we recommend you savea copy of the xml configuration file with a distinctive name as described here Save theConfiguration File
If you need to downgrade a Firebox without a backup file after you complete the upgrade toFireware v12x we recommend you Downgrade withWebUI This process deletes theconfiguration file but does not remove the device feature keys and certificates After youdowngrade the Firebox you can use Policy Manager to Save the Configuration File to theFireboxIf your Firebox has Fireware v1211 or later the Firebox will temporarily disable somesecurity services to free up enoughmemory to successfully perform a backup To learnmoresee Backup and Restore for XTM 25 XTM 26 and Firebox T10
Important Information about the upgrade process
l We recommend you use FirewareWebUI to upgrade to Fireware v12x You can also use PolicyManager if you prefer
l We strongly recommend that you save a local copy of your Firebox configuration and create a Fireboxbackup image before you upgrade
l If you useWatchGuard SystemManager (WSM) make sure yourWSM version is equal to or higherthan the version of Fireware OS installed on your Firebox and the version of WSM installed on yourManagement Server Also make sure to upgradeWSM before you upgrade the version of Fireware OSon your Firebox
Upgrade to Fireware v1213
14 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 15
If you want to upgrade a Firebox T10 XTM 2Series 33 330 or 5 Series device werecommend that you reboot your Firebox before you upgrade This clears your devicememoryand can prevent many problems commonly associated with upgrades in those devices
Back Up Your WatchGuard ServersIt is not usually necessary to uninstall your previous v11x or v12x server or client software when you upgradetoWSM v12x You can install the v12x server and client software on top of your existing installation toupgrade yourWatchGuard software components We do however strongly recommend that you back up yourWatchGuard Servers (for example yourWatchGuardManagement Server) to a safe location before youupgrade You will need these backup files if you ever want to downgrade
You cannot restore aWatchGuard Server backup file created withWatchGuard SystemManager v12x to to a v11x installation Make sure to retain your older server backup fileswhen you upgrade to v120 or later in case you want to downgrade in the future
To back up your Management Server configuration from the computer where you installed theManagementServer
1 FromWatchGuard Server Center select BackupRestore Management ServerThe WatchGuard Server Center BackupRestore Wizard starts
2 Click NextThe Select an action screen appears
3 Select Back up settings4 Click Next
The Specify a backup file screen appears5 Click Browse to select a location for the backup file Make sure you save the configuration file to a
location you can access later to restore the configuration6 Click Next
The WatchGuard Server Center BackupRestore Wizard is complete screen appears7 Click Finish to exit the wizard
Upgrade to Fireware v1213 fromWeb UIIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from theSystem gt Upgrade OS page If your Firebox is running v119x or earlier use thesesteps to upgrade
1 Before you begin save a local copy of your configuration file2 Go toSystem gt Backup Image or use the USB Backup feature to back up your current device image3 On your management computer launch the OS software file you downloaded from theWatchGuard
Software Downloads pageIf you use theWindows-based installer on a computer with aWindows 64-bit operating system thisinstallation extracts an upgrade file called [product series]_[product code]sysa-dl to the defaultlocation of CProgram Files(x86)Common FilesWatchGuardresourcesFirewareXTM1213[model]or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Connect to your Firebox with theWebUI and select System gt Upgrade OS5 Browse to the location of the [product series]_[product code]sysa-dl from Step 2 and click Upgrade
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v121 3installer twice (once to remove v1213 software and again to install v1213)
Upgrade to Fireware v1213
16 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 17
Upgrade to Fireware v1213 fromWSMPolicy Manager1 Before you begin save a local copy of your configuration file2 Select File gt Backup or use the USB Backup feature to back up your current device image3 On amanagement computer running aWindows 64-bit operating system launch the OS executable file
you downloaded from theWatchGuard Portal This installation extracts an upgrade file called [Firebox orxtm series]_[product code]sysa-dl to the default location of CProgram Files(x86)CommonfilesWatchGuardresourcesFirewareXTM1213[model] or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Install and openWatchGuard SystemManager v1213 Connect to your Firebox and launch PolicyManager
5 From Policy Manager select File gt Upgrade When prompted browse to and select the [productseries]_[product code]sysa-dl file from Step 2
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v1213installer twice (once to remove v1213 software and again to install v1213)
If you like tomake updates to your Firebox configuration from a saved configuration file makesure you open the configuration from the Firebox and save it to a new file after you upgradeThis is to make sure that you do not overwrite any configuration changes that weremade aspart of the upgrade
Other Upgrade IssuesThere is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Fireware v12x is not supported on XTM 5Series devices models 505 510 520 or 530
Before you upgrade to Fireware v12x your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is preventedIf you try to schedule anOS update of managed devices through aManagement Server theupgrade is also preventedIf you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x orv1110x before you upgrade to Fireware v12x or your Firebox will be reset to a default state
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
18 WatchGuard Technologies Inc
Update AP Devices
Release Notes 19
Update AP Devices
OnApril 12 2018 WatchGuard released AP firmware versions 12915 for the AP100 AP102and AP200 and 20010 for the AP300 to address security vulnerabilities We highlyrecommend you install these AP firmware updates For more detailed information on thesevulnerabilities see AP100AP102AP200 Chained Vulnerabilities In addition to addressingthese vulnerabilities the AP firmware updates disable the AP local web UI As these APmodels can only bemanaged with the Gateway Wireless Controller the AP local web UI is nolonger supported
Beginning with Fireware v11124 AP firmware is no longer bundled with Fireware OS All AP device firmwareis managed by the Gateway Wireless Controller on your Firebox TheGateway Wireless Controllerautomatically checks for new AP firmware updates and enables you to download the firmware directly fromWatchGuard servers
Important Upgrade StepsIf you have not previously upgraded to Fireware 1201 or higher and the latest AP firmware youmust performthese steps
1 Make sure all your APs are online You can check AP status from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager selecttheGateway Wireless Controller tab
2 Make sure you are not using insecure default AP passphrases such as wgwap orwatchguard Yourcurrent AP passphrasemust be secure and at least 8 characters in length You can change your APpassphrase inNetwork gt Gateway Wireless Controller gt Settings
If you do not have a secure passphrase correctly configured before the upgrade you will losethemanagement connection with your deployed APs If this occurs youmust physicallyreset the APs to factory default settings to be able tomanage the APs from GatewayWireless Controller
Depending on the version of Fireware you are upgrading from youmay need tomark APs as trusted after theupgrade to Fireware v1201 or higher You canmark APs as trusted from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager select theGateway Wireless Controller tab
AP Firmware UpgradeThe current AP firmware versions for each AP devicemodel are
AP Device Model Current Firmware Version
AP100 AP102 AP200 12915
AP300 20010
AP120 AP320 AP322 AP325AP420
850-646
Tomanage AP firmware and download the latest AP firmware to your Firebox
n From FirewareWebUI select Dashboard gt Gateway Wireless Controller From theSummary tabclick Manage Firmware
n From Firebox SystemManager select theGateway Wireless Controller tab then click ManageFirmware
Note that you cannot upgrade an AP120 AP320 AP322 or AP420 to 830-657 or higher unless your Firebox isrunning Fireware v11124 or higher If your Firebox does not run v11124 or higher you will not see an optionto upgrade to AP firmware v830-657 or higher
If you have enabled automatic AP device firmware updates in Gateway Wireless Controller your AP devicesare automatically updated betweenmidnight and 400am local time
Tomanually update firmware on your AP devices
1 On theAccess Points tab select one or more AP devices2 From theActions drop-down list click Upgrade3 Click Yes to confirm that you want to upgrade the AP device
Update AP Devices
20 WatchGuard Technologies Inc
Upgrade your FireCluster to Fireware v1213
Release Notes 21
Upgrade your FireCluster to Fireware v1213You can upgrade Fireware OS for a FireCluster from Policy Manager or FirewareWebUI To upgrade aFireCluster from Fireware v1110x or lower we recommend you use Policy Manager
As part of the upgrade process each cluster member reboots and rejoins the cluster Because the clustercannot do load balancing while a cluster member reboot is in progress we recommend you upgrade anactiveactive cluster at a time when the network traffic is lightest
For information on how to upgrade your FireCluster see this Help topic
There is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Before you upgrade to Fireware v1111 or higher your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is prevented
If you try to schedule anOS update of managed devices through aManagement Server theupgrade is also prevented
If you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x before youupgrade to Fireware v1111x or higher or your Firebox will be reset to a default state
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
Fireware andWSM v1213 Operating System Compatibility
Release Notes 5
Fireware and WSM v1213 Operating System CompatibilityLast revised 12 December 2017
WSMFirewareComponent
MicrosoftWindows788110
(32-bitamp64-bit)
MicrosoftWindowsServer2012amp2012R2(64-bit)
MicrosoftWindowsServer2016(64-bit)
MacOSXmacOSv1010
v1011v1012ampv1013
Android6x
7x amp8x
iOSv8 v9v10 ampv11
WatchGuard SystemManager
WatchGuard Servers
For information onWatchGuardDimension see the Dimension ReleaseNotes
Single Sign-On Agent(Includes Event LogMonitor)1
Single Sign-On Client
Single Sign-On ExchangeMonitor2
Terminal Services Agent3
Mobile VPN with IPSec 4 4
Mobile VPN with SSL
Notes about Microsoft Windows supportl Windows 8x support does not includeWindows RT
The following browsers are supported for both FirewareWebUI andWebCenter (Javascript required)l IE 11 and laterl Microsoft Edgel Firefox v55l Safari 10l Safari iOS 10l Chrome v60
1The Server Core installation option is supported forWindows Server 20162Microsoft Exchange Server 2007 and 2010 are supported Microsoft Exchange Server 2013 is supported if youinstall Windows Server 2012 or 2012 R2 and NET Framework 353Terminal Services support with manual or Single Sign-On authentication operates in aMicrosoft TerminalServices or Citrix XenApp 45 50 60 65 76 or 712 environment4Native (Cisco) IPSec client andOpenVPN are supported for all recent versions of Mac OS and iOS To useTheWatchGuardMobile VPN with IPSec client with OS 1013 youmust upgrade to the v300 client release
Authentication SupportThis table gives you a quick view of the types of authentication servers supported by key features of FirewareUsing an authentication server gives you the ability to configure user and group-based firewall and VPN policiesin your Firebox or XTM device configuration With each type of third-party authentication server supported youcan specify a backup server IP address for failover
Fully supported by WatchGuard Not yet supported but tested with success by WatchGuardcustomers
Fireware andWSM v1213 Operating System Compatibility
6 WatchGuard Technologies Inc
Fireware andWSM v1213 Operating System Compatibility
Release Notes 7
ActiveDirectory
1 LDAPRADIUS
2SecurID
2
Firebox(Firebox-DB)
LocalAuthentication
Mobile VPN with IPSecShrew Soft 3 ndash
Mobile VPN withIPSecWatchGuard client (NCP)
Mobile VPN with IPSec for iOS andMacOS X native VPN client
Mobile VPN with IPSec for Androiddevices
ndash
Mobile VPN with SSL forWindows 4 4
Mobile VPN with SSL for Mac
Mobile VPN with SSL for iOS andAndroid devices
Mobile VPN with L2TP 6 ndash ndash
Built-in AuthenticationWeb Page onPort 4100
Single Sign-On Support (with or withoutclient software)
ndash ndash ndash
Terminal Services ManualAuthentication
Terminal Services Authentication withSingle Sign-On
5 ndash ndash ndash ndash
Citrix Manual Authentication
Citrix Manual Authentication with SingleSign-On
5 ndash ndash ndash ndash
1 Active Directory support includes both single domain and multi-domain support unless otherwise noted2 RADIUS and SecurID support includes support for both one-time passphrases and challengeresponse
authentication integrated with RADIUS In many cases SecurID can also be used with other RADIUSimplementations including Vasco
3 The Shrew Soft client does not support two-factor authentication4 Fireware supports RADIUS Filter ID 11 for group authentication5 Both single and multiple domain Active Directory configurations are supported For information about the
supported Operating System compatibility for the WatchGuard TO Agent and SSO Agent see the currentFireware and WSM Operating System Compatibility table
6 Active Directory authentication methods are supported only through a RADIUS server
System RequirementsIf you have WatchGuard SystemManager client software onlyinstalled
If you install WatchGuard SystemManager and WatchGuard Serversoftware
Minimum CPU Intel Core or Xeon
2GHz
Intel Core or Xeon
2GHz
MinimumMemory 1GB 2GB
Minimum AvailableDisk Space
250MB 1GB
MinimumRecommendedScreen Resolution
1024x768 1024x768
FireboxV System RequirementsWith support for installation in both a VMware and a Hyper-V environment aWatchGuard FireboxV virtualmachine can run on a VMware ESXi 55 60 or 65 host or onWindows Server 2012 R2 or 2016 or Hyper-VServer 2012 R2 or 2016
The hardware requirements for FireboxV are the same as for the hypervisor environment it runs in
Each FireboxV virtual machine requires 5 GB of disk space CPU andmemory requirements vary by model
FireboxV Model vCPUs (maximum) Memory (recommended)
Small 2 2048MB
Medium 4 4096MB
Large 8 4096MB
Extra Large 16 4096MB
System requirements for XTMv are included in Fireware Help
Fireware andWSM v1213 Operating System Compatibility
8 WatchGuard Technologies Inc
Downloading Software
Release Notes 9
Downloading SoftwareYou can download software from theWatchGuard Software Downloads Center
There are several software files available for download with this release See the descriptions below so youknow what software packages you will need for your upgrade
WatchGuard System ManagerWith this software package you can install WSM and theWatchGuard Server Center software
WSM12_1_3exemdashUse this file to install WSM v1213 or to upgradeWatchGuard SystemManagerfrom an earlier version toWSM v1213
Fireware OSIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from the FirewareWebUI System gt Upgrade OS page
If you prefer to upgrade from Policy Manager or from an earlier version of Fireware you can use download theFireware OS image for your Firebox or XTM device Use the exe file if you want to install or upgrade theOSusingWSM Use the zip file if you want to install or upgrade theOS manually using FirewareWebUI Use theova or vhd file to deploy a new XTMv device
If you havehellip Select from these Fireware OS packages
Firebox M5600 Firebox_OS_M4600_M5600_12_1_3exefirebox_M4600_M5600_12_1_3zip
Firebox M4600 Firebox_OS_M4600_M5600_12_1_3exefirebox_M4600_M5600_12_1_3zip
Firebox M670 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M570 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M500 Firebox_OS_M400_M500_12_1_3exefirebox_M400_M500_12_1_3zip
Firebox M470 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M440 Firebox_OS_M440_12_1_3exefirebox_M440_12_1_3zip
Firebox M400 Firebox_OS_M400_M500_12_1_3exefirebox_M400_M500_12_1_3zip
Firebox M370 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M300 Firebox_OS_M200_M300_12_1_3exefirebox_M200_M300_12_1_3zip
Firebox M200 Firebox_OS_M200_M300_12_1_3exefirebox_M200_M300_12_1_3zip
Firebox T70 Firebox_OS_T70_12_1_3exefirebox_T70_12_1_3zip
Firebox T55 Firebox_OS_T55_12_1_3exefirebox_T55_12_1_3zip
Firebox T50 Firebox_OS_T30_T50_12_1_3exefirebox_T30_T50_12_1_3zip
Firebox T35 Firebox_OS_T35_12_1_3exefirebox_T35_12_1_3zip
Firebox T30 Firebox_OS_T30_T50_12_1_3exefirebox_T30_T50_12_1_3zip
Firebox T15 Firebox_OS_T15_12_1_3exefirebox_T15_12_1_3zip
Firebox T10 Firebox_OS_T10_12_1_3exefirebox_T10_12_1_3zip
Downloading Software
10 WatchGuard Technologies Inc
Downloading Software
Release Notes 11
If you havehellip Select from these Fireware OS packages
FireboxVAll editions for VMware
FireboxV_12_1_3ovaXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
FireboxVAll editions for Hyper-V
FireboxV_12_1_3_vhdzipXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
Firebox Cloud FireboxCloud_12_1_3zip
XTM 2500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 2050 XTM_OS_XTM2050_12_1_3exextm_xtm2050_12_1_3zip
XTM 1500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 1050 XTM_OS_XTM1050_12_1_3exextm_xtm1050_12_1_3zip
XTM 800 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 8Series XTM_OS_XTM8_12_1_3exextm_xtm8_12_1_3zip
XTM 5Series Models515 525 535 and 545only
XTM_OS_XTM5_12_1_3exextm_xtm5_12_1_3zip
XTM 330 XTM_OS_XTM330_12_1_3exextm_xtm330_12_1_3zip
XTM 33 XTM_OS_XTM3_12_1_3exextm_xtm3_12_1_3zip
XTM 2526 XTM_OS_XTM2A6_12_1_3exextm_xtm2a6_12_1_3zip
XTMvAll editions for VMware
xtmv_12_1_3ovaXTM_OS_xtmv_12_1_3exextm_xtmv_12_1_3zip
XTMvAll editions for Hyper-V
xtmv_12_1_3_vhdzipXTM_OS_XTMv_12_1_3exextm_xtmv_12_1_3zip
Single Sign-On SoftwareThese files are available for Single Sign-On There are no updates with the v1213 release
l WG-Authentication-Gateway_12_0exe (SSOAgent software - required for Single Sign-On andincludes optional Event LogMonitor for clientless SSO)
l WG-Authentication-Client_11122msi (SSOClient software forWindows)l WG-SSOCLIENT-MAC_12_0dmg (SSOClient software for Mac OS X)l SSOExchangeMonitor_x86_12_0exe (ExchangeMonitor for 32-bit operating systems)l SSOExchangeMonitor_x64_12_0exe (ExchangeMonitor for 64-bit operating systems)
For information about how to install and set up Single Sign-On see the product documentation
Terminal Services Authentication SoftwareThis file is not updated with the Fireware v1213 release
l TO_AGENT_SETUP_11_12exe (This installer includes both 32-bit and 64-bit file support)
Mobile VPN with SSL Client for Windows and MacThere are two files available for download if you useMobile VPN with SSL
l WG-MVPN-SSL_12_0exe (Client software forWindows)l WG-MVPN-SSL_12_0dmg (Client software for Mac)
Mobile VPN with IPSec client for Windows and MacThere are several available files to download
Shrew Soft Client
l Shrew Soft Client 222 for Windows - No client license required
WatchGuard IPSec Mobile VPN Clients
The current WatchGuard IPSec Mobile VPN Client forWindows version is 1213
l WatchGuard IPSec Mobile VPN Client for Windows (32-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
l WatchGuard IPSec Mobile VPN Client for Windows (64-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
The current macOS client version is 300
l WatchGuard IPSec Mobile VPN Client for macOS powered by NCP - There is a license requiredfor this premium client with a 30-day free trial available with download
WatchGuard Mobile VPN License Server
l WatchGuard Mobile VPN License Server (MVLS) v20 powered by NCP- Click here for moreinformation about MVLS If you have a VPN bundle ID for macOS it must be updated on the licenseserver to support the new macOS 300 client To update your bundle ID contact WatchGuard CustomerSupport Make sure to have your existing bundle ID available to expedite the update
Downloading Software
12 WatchGuard Technologies Inc
Upgrade Notes
Release Notes 13
Upgrade Notes
SSLTLS Settings Precedence and InheritanceFour Firebox features use SSLTLS for secure communication and share the sameOpenVPN serverManagement Tunnel over SSL on hub devices BOVPN over TLS in Server mode Mobile VPN with SSL andthe Access Portal These features also share some settings When you enablemore than one of thesefeatures settings for some features have a higher precedence than settings for other features Shared settingsare not configurable for the features with lower precedence For more information see this topic in FirewareHelp
Modem Configurations Converted to External Interfaces with Failover EnabledIf your Firebox was configured for modem failover when you upgrade your Firebox to Fireware v121 or higherthemodem configuration is automatically converted to an external interface with modem failover enabled If allother external interfaces become unavailable traffic automatically fails over to themodem interface Modeminterfaces can also participate in multi-WAN on all devices except the Firebox T10 Firebox T15 and XTM 2Series devices that do not have the Pro upgrade
HTTPS Proxy Content Inspection with Fireware v121With Fireware 121 we updated the HTTPS proxy action to include a Content Inspection Exceptions list whichincludes domains for services such as Dropbox Skype andMicrosoft Office that are known to be incompatiblewith content inspection The HTTPS proxy does not perform content inspection for domains with enabledexceptions on the Content Inspection Exceptions list
When you upgrade your Firebox to Fireware v121 or higher the Content Inspection Exceptions list isautomatically enabled in all HTTPS proxy actions that have content inspection enabled After the upgrade werecommend that you review the Content Inspection Exceptions list in your configured HTTPS proxy actionsand disable the exception for any domain you do not want the HTTPS proxy to allow without content inspectionFor more information seeWhich applications are on the default exception list in an HTTPS proxy action in theKnowledge Base
Gateway AV Engine Upgrade with Fireware v120With Fireware v120 we updated the engine used by Gateway AV to a new engine from BitDefender As aresult any Firebox that upgrades from Fireware v11x version to v120 or later must download a new signatureset which can take 7-10minutes for the first update It can take an additional 5-7minutes to synchronize aFireCluster We recommend that you upgrade to Fireware v12x at a quiet time on your network After the initialupdate signature updates are incremental andmuch faster than in previous versions
While the new signature set is being downloaded network users could experience issues related to GatewayAV scan failures for several minutes after the update and inbound emails sent through the SMTP proxy couldbe locked
XTMv Upgrade NotesYou cannot upgrade an XTMv device to FireboxV For Fireware v1111 and higher the XTMv device is a 64-bitvirtual machine You cannot upgrade an XTMv device from Fireware v1110x or lower to Fireware v1111 orhigher Instead youmust use the OVA file to deploy a new 64-bit Fireware v1111x or v12x XTMv VM andthen use Policy Manager to move the existing configuration from the 32-bit XTMv VM to the 64-bit XTMv VMFor more information about how tomove the configuration or deploy a new XTMv VM see Fireware Help Whenyour XTMv instance has been updated to v1111 or higher you can then use the usual upgrade procedure asdetailed in the next section
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
If your Firebox is a T10 XTM 25 or XTM 26 device with OS version 121 or older youmightnot be able to perform a backup before you upgrade the Firebox This occurs because thememory use by Fireware v121 or older does not leave enoughmemory free to successfullycomplete the upgrade process on these devices For these devices we recommend you savea copy of the xml configuration file with a distinctive name as described here Save theConfiguration File
If you need to downgrade a Firebox without a backup file after you complete the upgrade toFireware v12x we recommend you Downgrade withWebUI This process deletes theconfiguration file but does not remove the device feature keys and certificates After youdowngrade the Firebox you can use Policy Manager to Save the Configuration File to theFireboxIf your Firebox has Fireware v1211 or later the Firebox will temporarily disable somesecurity services to free up enoughmemory to successfully perform a backup To learnmoresee Backup and Restore for XTM 25 XTM 26 and Firebox T10
Important Information about the upgrade process
l We recommend you use FirewareWebUI to upgrade to Fireware v12x You can also use PolicyManager if you prefer
l We strongly recommend that you save a local copy of your Firebox configuration and create a Fireboxbackup image before you upgrade
l If you useWatchGuard SystemManager (WSM) make sure yourWSM version is equal to or higherthan the version of Fireware OS installed on your Firebox and the version of WSM installed on yourManagement Server Also make sure to upgradeWSM before you upgrade the version of Fireware OSon your Firebox
Upgrade to Fireware v1213
14 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 15
If you want to upgrade a Firebox T10 XTM 2Series 33 330 or 5 Series device werecommend that you reboot your Firebox before you upgrade This clears your devicememoryand can prevent many problems commonly associated with upgrades in those devices
Back Up Your WatchGuard ServersIt is not usually necessary to uninstall your previous v11x or v12x server or client software when you upgradetoWSM v12x You can install the v12x server and client software on top of your existing installation toupgrade yourWatchGuard software components We do however strongly recommend that you back up yourWatchGuard Servers (for example yourWatchGuardManagement Server) to a safe location before youupgrade You will need these backup files if you ever want to downgrade
You cannot restore aWatchGuard Server backup file created withWatchGuard SystemManager v12x to to a v11x installation Make sure to retain your older server backup fileswhen you upgrade to v120 or later in case you want to downgrade in the future
To back up your Management Server configuration from the computer where you installed theManagementServer
1 FromWatchGuard Server Center select BackupRestore Management ServerThe WatchGuard Server Center BackupRestore Wizard starts
2 Click NextThe Select an action screen appears
3 Select Back up settings4 Click Next
The Specify a backup file screen appears5 Click Browse to select a location for the backup file Make sure you save the configuration file to a
location you can access later to restore the configuration6 Click Next
The WatchGuard Server Center BackupRestore Wizard is complete screen appears7 Click Finish to exit the wizard
Upgrade to Fireware v1213 fromWeb UIIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from theSystem gt Upgrade OS page If your Firebox is running v119x or earlier use thesesteps to upgrade
1 Before you begin save a local copy of your configuration file2 Go toSystem gt Backup Image or use the USB Backup feature to back up your current device image3 On your management computer launch the OS software file you downloaded from theWatchGuard
Software Downloads pageIf you use theWindows-based installer on a computer with aWindows 64-bit operating system thisinstallation extracts an upgrade file called [product series]_[product code]sysa-dl to the defaultlocation of CProgram Files(x86)Common FilesWatchGuardresourcesFirewareXTM1213[model]or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Connect to your Firebox with theWebUI and select System gt Upgrade OS5 Browse to the location of the [product series]_[product code]sysa-dl from Step 2 and click Upgrade
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v121 3installer twice (once to remove v1213 software and again to install v1213)
Upgrade to Fireware v1213
16 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 17
Upgrade to Fireware v1213 fromWSMPolicy Manager1 Before you begin save a local copy of your configuration file2 Select File gt Backup or use the USB Backup feature to back up your current device image3 On amanagement computer running aWindows 64-bit operating system launch the OS executable file
you downloaded from theWatchGuard Portal This installation extracts an upgrade file called [Firebox orxtm series]_[product code]sysa-dl to the default location of CProgram Files(x86)CommonfilesWatchGuardresourcesFirewareXTM1213[model] or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Install and openWatchGuard SystemManager v1213 Connect to your Firebox and launch PolicyManager
5 From Policy Manager select File gt Upgrade When prompted browse to and select the [productseries]_[product code]sysa-dl file from Step 2
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v1213installer twice (once to remove v1213 software and again to install v1213)
If you like tomake updates to your Firebox configuration from a saved configuration file makesure you open the configuration from the Firebox and save it to a new file after you upgradeThis is to make sure that you do not overwrite any configuration changes that weremade aspart of the upgrade
Other Upgrade IssuesThere is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Fireware v12x is not supported on XTM 5Series devices models 505 510 520 or 530
Before you upgrade to Fireware v12x your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is preventedIf you try to schedule anOS update of managed devices through aManagement Server theupgrade is also preventedIf you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x orv1110x before you upgrade to Fireware v12x or your Firebox will be reset to a default state
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
18 WatchGuard Technologies Inc
Update AP Devices
Release Notes 19
Update AP Devices
OnApril 12 2018 WatchGuard released AP firmware versions 12915 for the AP100 AP102and AP200 and 20010 for the AP300 to address security vulnerabilities We highlyrecommend you install these AP firmware updates For more detailed information on thesevulnerabilities see AP100AP102AP200 Chained Vulnerabilities In addition to addressingthese vulnerabilities the AP firmware updates disable the AP local web UI As these APmodels can only bemanaged with the Gateway Wireless Controller the AP local web UI is nolonger supported
Beginning with Fireware v11124 AP firmware is no longer bundled with Fireware OS All AP device firmwareis managed by the Gateway Wireless Controller on your Firebox TheGateway Wireless Controllerautomatically checks for new AP firmware updates and enables you to download the firmware directly fromWatchGuard servers
Important Upgrade StepsIf you have not previously upgraded to Fireware 1201 or higher and the latest AP firmware youmust performthese steps
1 Make sure all your APs are online You can check AP status from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager selecttheGateway Wireless Controller tab
2 Make sure you are not using insecure default AP passphrases such as wgwap orwatchguard Yourcurrent AP passphrasemust be secure and at least 8 characters in length You can change your APpassphrase inNetwork gt Gateway Wireless Controller gt Settings
If you do not have a secure passphrase correctly configured before the upgrade you will losethemanagement connection with your deployed APs If this occurs youmust physicallyreset the APs to factory default settings to be able tomanage the APs from GatewayWireless Controller
Depending on the version of Fireware you are upgrading from youmay need tomark APs as trusted after theupgrade to Fireware v1201 or higher You canmark APs as trusted from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager select theGateway Wireless Controller tab
AP Firmware UpgradeThe current AP firmware versions for each AP devicemodel are
AP Device Model Current Firmware Version
AP100 AP102 AP200 12915
AP300 20010
AP120 AP320 AP322 AP325AP420
850-646
Tomanage AP firmware and download the latest AP firmware to your Firebox
n From FirewareWebUI select Dashboard gt Gateway Wireless Controller From theSummary tabclick Manage Firmware
n From Firebox SystemManager select theGateway Wireless Controller tab then click ManageFirmware
Note that you cannot upgrade an AP120 AP320 AP322 or AP420 to 830-657 or higher unless your Firebox isrunning Fireware v11124 or higher If your Firebox does not run v11124 or higher you will not see an optionto upgrade to AP firmware v830-657 or higher
If you have enabled automatic AP device firmware updates in Gateway Wireless Controller your AP devicesare automatically updated betweenmidnight and 400am local time
Tomanually update firmware on your AP devices
1 On theAccess Points tab select one or more AP devices2 From theActions drop-down list click Upgrade3 Click Yes to confirm that you want to upgrade the AP device
Update AP Devices
20 WatchGuard Technologies Inc
Upgrade your FireCluster to Fireware v1213
Release Notes 21
Upgrade your FireCluster to Fireware v1213You can upgrade Fireware OS for a FireCluster from Policy Manager or FirewareWebUI To upgrade aFireCluster from Fireware v1110x or lower we recommend you use Policy Manager
As part of the upgrade process each cluster member reboots and rejoins the cluster Because the clustercannot do load balancing while a cluster member reboot is in progress we recommend you upgrade anactiveactive cluster at a time when the network traffic is lightest
For information on how to upgrade your FireCluster see this Help topic
There is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Before you upgrade to Fireware v1111 or higher your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is prevented
If you try to schedule anOS update of managed devices through aManagement Server theupgrade is also prevented
If you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x before youupgrade to Fireware v1111x or higher or your Firebox will be reset to a default state
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
1The Server Core installation option is supported forWindows Server 20162Microsoft Exchange Server 2007 and 2010 are supported Microsoft Exchange Server 2013 is supported if youinstall Windows Server 2012 or 2012 R2 and NET Framework 353Terminal Services support with manual or Single Sign-On authentication operates in aMicrosoft TerminalServices or Citrix XenApp 45 50 60 65 76 or 712 environment4Native (Cisco) IPSec client andOpenVPN are supported for all recent versions of Mac OS and iOS To useTheWatchGuardMobile VPN with IPSec client with OS 1013 youmust upgrade to the v300 client release
Authentication SupportThis table gives you a quick view of the types of authentication servers supported by key features of FirewareUsing an authentication server gives you the ability to configure user and group-based firewall and VPN policiesin your Firebox or XTM device configuration With each type of third-party authentication server supported youcan specify a backup server IP address for failover
Fully supported by WatchGuard Not yet supported but tested with success by WatchGuardcustomers
Fireware andWSM v1213 Operating System Compatibility
6 WatchGuard Technologies Inc
Fireware andWSM v1213 Operating System Compatibility
Release Notes 7
ActiveDirectory
1 LDAPRADIUS
2SecurID
2
Firebox(Firebox-DB)
LocalAuthentication
Mobile VPN with IPSecShrew Soft 3 ndash
Mobile VPN withIPSecWatchGuard client (NCP)
Mobile VPN with IPSec for iOS andMacOS X native VPN client
Mobile VPN with IPSec for Androiddevices
ndash
Mobile VPN with SSL forWindows 4 4
Mobile VPN with SSL for Mac
Mobile VPN with SSL for iOS andAndroid devices
Mobile VPN with L2TP 6 ndash ndash
Built-in AuthenticationWeb Page onPort 4100
Single Sign-On Support (with or withoutclient software)
ndash ndash ndash
Terminal Services ManualAuthentication
Terminal Services Authentication withSingle Sign-On
5 ndash ndash ndash ndash
Citrix Manual Authentication
Citrix Manual Authentication with SingleSign-On
5 ndash ndash ndash ndash
1 Active Directory support includes both single domain and multi-domain support unless otherwise noted2 RADIUS and SecurID support includes support for both one-time passphrases and challengeresponse
authentication integrated with RADIUS In many cases SecurID can also be used with other RADIUSimplementations including Vasco
3 The Shrew Soft client does not support two-factor authentication4 Fireware supports RADIUS Filter ID 11 for group authentication5 Both single and multiple domain Active Directory configurations are supported For information about the
supported Operating System compatibility for the WatchGuard TO Agent and SSO Agent see the currentFireware and WSM Operating System Compatibility table
6 Active Directory authentication methods are supported only through a RADIUS server
System RequirementsIf you have WatchGuard SystemManager client software onlyinstalled
If you install WatchGuard SystemManager and WatchGuard Serversoftware
Minimum CPU Intel Core or Xeon
2GHz
Intel Core or Xeon
2GHz
MinimumMemory 1GB 2GB
Minimum AvailableDisk Space
250MB 1GB
MinimumRecommendedScreen Resolution
1024x768 1024x768
FireboxV System RequirementsWith support for installation in both a VMware and a Hyper-V environment aWatchGuard FireboxV virtualmachine can run on a VMware ESXi 55 60 or 65 host or onWindows Server 2012 R2 or 2016 or Hyper-VServer 2012 R2 or 2016
The hardware requirements for FireboxV are the same as for the hypervisor environment it runs in
Each FireboxV virtual machine requires 5 GB of disk space CPU andmemory requirements vary by model
FireboxV Model vCPUs (maximum) Memory (recommended)
Small 2 2048MB
Medium 4 4096MB
Large 8 4096MB
Extra Large 16 4096MB
System requirements for XTMv are included in Fireware Help
Fireware andWSM v1213 Operating System Compatibility
8 WatchGuard Technologies Inc
Downloading Software
Release Notes 9
Downloading SoftwareYou can download software from theWatchGuard Software Downloads Center
There are several software files available for download with this release See the descriptions below so youknow what software packages you will need for your upgrade
WatchGuard System ManagerWith this software package you can install WSM and theWatchGuard Server Center software
WSM12_1_3exemdashUse this file to install WSM v1213 or to upgradeWatchGuard SystemManagerfrom an earlier version toWSM v1213
Fireware OSIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from the FirewareWebUI System gt Upgrade OS page
If you prefer to upgrade from Policy Manager or from an earlier version of Fireware you can use download theFireware OS image for your Firebox or XTM device Use the exe file if you want to install or upgrade theOSusingWSM Use the zip file if you want to install or upgrade theOS manually using FirewareWebUI Use theova or vhd file to deploy a new XTMv device
If you havehellip Select from these Fireware OS packages
Firebox M5600 Firebox_OS_M4600_M5600_12_1_3exefirebox_M4600_M5600_12_1_3zip
Firebox M4600 Firebox_OS_M4600_M5600_12_1_3exefirebox_M4600_M5600_12_1_3zip
Firebox M670 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M570 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M500 Firebox_OS_M400_M500_12_1_3exefirebox_M400_M500_12_1_3zip
Firebox M470 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M440 Firebox_OS_M440_12_1_3exefirebox_M440_12_1_3zip
Firebox M400 Firebox_OS_M400_M500_12_1_3exefirebox_M400_M500_12_1_3zip
Firebox M370 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M300 Firebox_OS_M200_M300_12_1_3exefirebox_M200_M300_12_1_3zip
Firebox M200 Firebox_OS_M200_M300_12_1_3exefirebox_M200_M300_12_1_3zip
Firebox T70 Firebox_OS_T70_12_1_3exefirebox_T70_12_1_3zip
Firebox T55 Firebox_OS_T55_12_1_3exefirebox_T55_12_1_3zip
Firebox T50 Firebox_OS_T30_T50_12_1_3exefirebox_T30_T50_12_1_3zip
Firebox T35 Firebox_OS_T35_12_1_3exefirebox_T35_12_1_3zip
Firebox T30 Firebox_OS_T30_T50_12_1_3exefirebox_T30_T50_12_1_3zip
Firebox T15 Firebox_OS_T15_12_1_3exefirebox_T15_12_1_3zip
Firebox T10 Firebox_OS_T10_12_1_3exefirebox_T10_12_1_3zip
Downloading Software
10 WatchGuard Technologies Inc
Downloading Software
Release Notes 11
If you havehellip Select from these Fireware OS packages
FireboxVAll editions for VMware
FireboxV_12_1_3ovaXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
FireboxVAll editions for Hyper-V
FireboxV_12_1_3_vhdzipXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
Firebox Cloud FireboxCloud_12_1_3zip
XTM 2500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 2050 XTM_OS_XTM2050_12_1_3exextm_xtm2050_12_1_3zip
XTM 1500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 1050 XTM_OS_XTM1050_12_1_3exextm_xtm1050_12_1_3zip
XTM 800 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 8Series XTM_OS_XTM8_12_1_3exextm_xtm8_12_1_3zip
XTM 5Series Models515 525 535 and 545only
XTM_OS_XTM5_12_1_3exextm_xtm5_12_1_3zip
XTM 330 XTM_OS_XTM330_12_1_3exextm_xtm330_12_1_3zip
XTM 33 XTM_OS_XTM3_12_1_3exextm_xtm3_12_1_3zip
XTM 2526 XTM_OS_XTM2A6_12_1_3exextm_xtm2a6_12_1_3zip
XTMvAll editions for VMware
xtmv_12_1_3ovaXTM_OS_xtmv_12_1_3exextm_xtmv_12_1_3zip
XTMvAll editions for Hyper-V
xtmv_12_1_3_vhdzipXTM_OS_XTMv_12_1_3exextm_xtmv_12_1_3zip
Single Sign-On SoftwareThese files are available for Single Sign-On There are no updates with the v1213 release
l WG-Authentication-Gateway_12_0exe (SSOAgent software - required for Single Sign-On andincludes optional Event LogMonitor for clientless SSO)
l WG-Authentication-Client_11122msi (SSOClient software forWindows)l WG-SSOCLIENT-MAC_12_0dmg (SSOClient software for Mac OS X)l SSOExchangeMonitor_x86_12_0exe (ExchangeMonitor for 32-bit operating systems)l SSOExchangeMonitor_x64_12_0exe (ExchangeMonitor for 64-bit operating systems)
For information about how to install and set up Single Sign-On see the product documentation
Terminal Services Authentication SoftwareThis file is not updated with the Fireware v1213 release
l TO_AGENT_SETUP_11_12exe (This installer includes both 32-bit and 64-bit file support)
Mobile VPN with SSL Client for Windows and MacThere are two files available for download if you useMobile VPN with SSL
l WG-MVPN-SSL_12_0exe (Client software forWindows)l WG-MVPN-SSL_12_0dmg (Client software for Mac)
Mobile VPN with IPSec client for Windows and MacThere are several available files to download
Shrew Soft Client
l Shrew Soft Client 222 for Windows - No client license required
WatchGuard IPSec Mobile VPN Clients
The current WatchGuard IPSec Mobile VPN Client forWindows version is 1213
l WatchGuard IPSec Mobile VPN Client for Windows (32-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
l WatchGuard IPSec Mobile VPN Client for Windows (64-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
The current macOS client version is 300
l WatchGuard IPSec Mobile VPN Client for macOS powered by NCP - There is a license requiredfor this premium client with a 30-day free trial available with download
WatchGuard Mobile VPN License Server
l WatchGuard Mobile VPN License Server (MVLS) v20 powered by NCP- Click here for moreinformation about MVLS If you have a VPN bundle ID for macOS it must be updated on the licenseserver to support the new macOS 300 client To update your bundle ID contact WatchGuard CustomerSupport Make sure to have your existing bundle ID available to expedite the update
Downloading Software
12 WatchGuard Technologies Inc
Upgrade Notes
Release Notes 13
Upgrade Notes
SSLTLS Settings Precedence and InheritanceFour Firebox features use SSLTLS for secure communication and share the sameOpenVPN serverManagement Tunnel over SSL on hub devices BOVPN over TLS in Server mode Mobile VPN with SSL andthe Access Portal These features also share some settings When you enablemore than one of thesefeatures settings for some features have a higher precedence than settings for other features Shared settingsare not configurable for the features with lower precedence For more information see this topic in FirewareHelp
Modem Configurations Converted to External Interfaces with Failover EnabledIf your Firebox was configured for modem failover when you upgrade your Firebox to Fireware v121 or higherthemodem configuration is automatically converted to an external interface with modem failover enabled If allother external interfaces become unavailable traffic automatically fails over to themodem interface Modeminterfaces can also participate in multi-WAN on all devices except the Firebox T10 Firebox T15 and XTM 2Series devices that do not have the Pro upgrade
HTTPS Proxy Content Inspection with Fireware v121With Fireware 121 we updated the HTTPS proxy action to include a Content Inspection Exceptions list whichincludes domains for services such as Dropbox Skype andMicrosoft Office that are known to be incompatiblewith content inspection The HTTPS proxy does not perform content inspection for domains with enabledexceptions on the Content Inspection Exceptions list
When you upgrade your Firebox to Fireware v121 or higher the Content Inspection Exceptions list isautomatically enabled in all HTTPS proxy actions that have content inspection enabled After the upgrade werecommend that you review the Content Inspection Exceptions list in your configured HTTPS proxy actionsand disable the exception for any domain you do not want the HTTPS proxy to allow without content inspectionFor more information seeWhich applications are on the default exception list in an HTTPS proxy action in theKnowledge Base
Gateway AV Engine Upgrade with Fireware v120With Fireware v120 we updated the engine used by Gateway AV to a new engine from BitDefender As aresult any Firebox that upgrades from Fireware v11x version to v120 or later must download a new signatureset which can take 7-10minutes for the first update It can take an additional 5-7minutes to synchronize aFireCluster We recommend that you upgrade to Fireware v12x at a quiet time on your network After the initialupdate signature updates are incremental andmuch faster than in previous versions
While the new signature set is being downloaded network users could experience issues related to GatewayAV scan failures for several minutes after the update and inbound emails sent through the SMTP proxy couldbe locked
XTMv Upgrade NotesYou cannot upgrade an XTMv device to FireboxV For Fireware v1111 and higher the XTMv device is a 64-bitvirtual machine You cannot upgrade an XTMv device from Fireware v1110x or lower to Fireware v1111 orhigher Instead youmust use the OVA file to deploy a new 64-bit Fireware v1111x or v12x XTMv VM andthen use Policy Manager to move the existing configuration from the 32-bit XTMv VM to the 64-bit XTMv VMFor more information about how tomove the configuration or deploy a new XTMv VM see Fireware Help Whenyour XTMv instance has been updated to v1111 or higher you can then use the usual upgrade procedure asdetailed in the next section
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
If your Firebox is a T10 XTM 25 or XTM 26 device with OS version 121 or older youmightnot be able to perform a backup before you upgrade the Firebox This occurs because thememory use by Fireware v121 or older does not leave enoughmemory free to successfullycomplete the upgrade process on these devices For these devices we recommend you savea copy of the xml configuration file with a distinctive name as described here Save theConfiguration File
If you need to downgrade a Firebox without a backup file after you complete the upgrade toFireware v12x we recommend you Downgrade withWebUI This process deletes theconfiguration file but does not remove the device feature keys and certificates After youdowngrade the Firebox you can use Policy Manager to Save the Configuration File to theFireboxIf your Firebox has Fireware v1211 or later the Firebox will temporarily disable somesecurity services to free up enoughmemory to successfully perform a backup To learnmoresee Backup and Restore for XTM 25 XTM 26 and Firebox T10
Important Information about the upgrade process
l We recommend you use FirewareWebUI to upgrade to Fireware v12x You can also use PolicyManager if you prefer
l We strongly recommend that you save a local copy of your Firebox configuration and create a Fireboxbackup image before you upgrade
l If you useWatchGuard SystemManager (WSM) make sure yourWSM version is equal to or higherthan the version of Fireware OS installed on your Firebox and the version of WSM installed on yourManagement Server Also make sure to upgradeWSM before you upgrade the version of Fireware OSon your Firebox
Upgrade to Fireware v1213
14 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 15
If you want to upgrade a Firebox T10 XTM 2Series 33 330 or 5 Series device werecommend that you reboot your Firebox before you upgrade This clears your devicememoryand can prevent many problems commonly associated with upgrades in those devices
Back Up Your WatchGuard ServersIt is not usually necessary to uninstall your previous v11x or v12x server or client software when you upgradetoWSM v12x You can install the v12x server and client software on top of your existing installation toupgrade yourWatchGuard software components We do however strongly recommend that you back up yourWatchGuard Servers (for example yourWatchGuardManagement Server) to a safe location before youupgrade You will need these backup files if you ever want to downgrade
You cannot restore aWatchGuard Server backup file created withWatchGuard SystemManager v12x to to a v11x installation Make sure to retain your older server backup fileswhen you upgrade to v120 or later in case you want to downgrade in the future
To back up your Management Server configuration from the computer where you installed theManagementServer
1 FromWatchGuard Server Center select BackupRestore Management ServerThe WatchGuard Server Center BackupRestore Wizard starts
2 Click NextThe Select an action screen appears
3 Select Back up settings4 Click Next
The Specify a backup file screen appears5 Click Browse to select a location for the backup file Make sure you save the configuration file to a
location you can access later to restore the configuration6 Click Next
The WatchGuard Server Center BackupRestore Wizard is complete screen appears7 Click Finish to exit the wizard
Upgrade to Fireware v1213 fromWeb UIIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from theSystem gt Upgrade OS page If your Firebox is running v119x or earlier use thesesteps to upgrade
1 Before you begin save a local copy of your configuration file2 Go toSystem gt Backup Image or use the USB Backup feature to back up your current device image3 On your management computer launch the OS software file you downloaded from theWatchGuard
Software Downloads pageIf you use theWindows-based installer on a computer with aWindows 64-bit operating system thisinstallation extracts an upgrade file called [product series]_[product code]sysa-dl to the defaultlocation of CProgram Files(x86)Common FilesWatchGuardresourcesFirewareXTM1213[model]or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Connect to your Firebox with theWebUI and select System gt Upgrade OS5 Browse to the location of the [product series]_[product code]sysa-dl from Step 2 and click Upgrade
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v121 3installer twice (once to remove v1213 software and again to install v1213)
Upgrade to Fireware v1213
16 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 17
Upgrade to Fireware v1213 fromWSMPolicy Manager1 Before you begin save a local copy of your configuration file2 Select File gt Backup or use the USB Backup feature to back up your current device image3 On amanagement computer running aWindows 64-bit operating system launch the OS executable file
you downloaded from theWatchGuard Portal This installation extracts an upgrade file called [Firebox orxtm series]_[product code]sysa-dl to the default location of CProgram Files(x86)CommonfilesWatchGuardresourcesFirewareXTM1213[model] or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Install and openWatchGuard SystemManager v1213 Connect to your Firebox and launch PolicyManager
5 From Policy Manager select File gt Upgrade When prompted browse to and select the [productseries]_[product code]sysa-dl file from Step 2
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v1213installer twice (once to remove v1213 software and again to install v1213)
If you like tomake updates to your Firebox configuration from a saved configuration file makesure you open the configuration from the Firebox and save it to a new file after you upgradeThis is to make sure that you do not overwrite any configuration changes that weremade aspart of the upgrade
Other Upgrade IssuesThere is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Fireware v12x is not supported on XTM 5Series devices models 505 510 520 or 530
Before you upgrade to Fireware v12x your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is preventedIf you try to schedule anOS update of managed devices through aManagement Server theupgrade is also preventedIf you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x orv1110x before you upgrade to Fireware v12x or your Firebox will be reset to a default state
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
18 WatchGuard Technologies Inc
Update AP Devices
Release Notes 19
Update AP Devices
OnApril 12 2018 WatchGuard released AP firmware versions 12915 for the AP100 AP102and AP200 and 20010 for the AP300 to address security vulnerabilities We highlyrecommend you install these AP firmware updates For more detailed information on thesevulnerabilities see AP100AP102AP200 Chained Vulnerabilities In addition to addressingthese vulnerabilities the AP firmware updates disable the AP local web UI As these APmodels can only bemanaged with the Gateway Wireless Controller the AP local web UI is nolonger supported
Beginning with Fireware v11124 AP firmware is no longer bundled with Fireware OS All AP device firmwareis managed by the Gateway Wireless Controller on your Firebox TheGateway Wireless Controllerautomatically checks for new AP firmware updates and enables you to download the firmware directly fromWatchGuard servers
Important Upgrade StepsIf you have not previously upgraded to Fireware 1201 or higher and the latest AP firmware youmust performthese steps
1 Make sure all your APs are online You can check AP status from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager selecttheGateway Wireless Controller tab
2 Make sure you are not using insecure default AP passphrases such as wgwap orwatchguard Yourcurrent AP passphrasemust be secure and at least 8 characters in length You can change your APpassphrase inNetwork gt Gateway Wireless Controller gt Settings
If you do not have a secure passphrase correctly configured before the upgrade you will losethemanagement connection with your deployed APs If this occurs youmust physicallyreset the APs to factory default settings to be able tomanage the APs from GatewayWireless Controller
Depending on the version of Fireware you are upgrading from youmay need tomark APs as trusted after theupgrade to Fireware v1201 or higher You canmark APs as trusted from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager select theGateway Wireless Controller tab
AP Firmware UpgradeThe current AP firmware versions for each AP devicemodel are
AP Device Model Current Firmware Version
AP100 AP102 AP200 12915
AP300 20010
AP120 AP320 AP322 AP325AP420
850-646
Tomanage AP firmware and download the latest AP firmware to your Firebox
n From FirewareWebUI select Dashboard gt Gateway Wireless Controller From theSummary tabclick Manage Firmware
n From Firebox SystemManager select theGateway Wireless Controller tab then click ManageFirmware
Note that you cannot upgrade an AP120 AP320 AP322 or AP420 to 830-657 or higher unless your Firebox isrunning Fireware v11124 or higher If your Firebox does not run v11124 or higher you will not see an optionto upgrade to AP firmware v830-657 or higher
If you have enabled automatic AP device firmware updates in Gateway Wireless Controller your AP devicesare automatically updated betweenmidnight and 400am local time
Tomanually update firmware on your AP devices
1 On theAccess Points tab select one or more AP devices2 From theActions drop-down list click Upgrade3 Click Yes to confirm that you want to upgrade the AP device
Update AP Devices
20 WatchGuard Technologies Inc
Upgrade your FireCluster to Fireware v1213
Release Notes 21
Upgrade your FireCluster to Fireware v1213You can upgrade Fireware OS for a FireCluster from Policy Manager or FirewareWebUI To upgrade aFireCluster from Fireware v1110x or lower we recommend you use Policy Manager
As part of the upgrade process each cluster member reboots and rejoins the cluster Because the clustercannot do load balancing while a cluster member reboot is in progress we recommend you upgrade anactiveactive cluster at a time when the network traffic is lightest
For information on how to upgrade your FireCluster see this Help topic
There is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Before you upgrade to Fireware v1111 or higher your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is prevented
If you try to schedule anOS update of managed devices through aManagement Server theupgrade is also prevented
If you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x before youupgrade to Fireware v1111x or higher or your Firebox will be reset to a default state
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
Fireware andWSM v1213 Operating System Compatibility
Release Notes 7
ActiveDirectory
1 LDAPRADIUS
2SecurID
2
Firebox(Firebox-DB)
LocalAuthentication
Mobile VPN with IPSecShrew Soft 3 ndash
Mobile VPN withIPSecWatchGuard client (NCP)
Mobile VPN with IPSec for iOS andMacOS X native VPN client
Mobile VPN with IPSec for Androiddevices
ndash
Mobile VPN with SSL forWindows 4 4
Mobile VPN with SSL for Mac
Mobile VPN with SSL for iOS andAndroid devices
Mobile VPN with L2TP 6 ndash ndash
Built-in AuthenticationWeb Page onPort 4100
Single Sign-On Support (with or withoutclient software)
ndash ndash ndash
Terminal Services ManualAuthentication
Terminal Services Authentication withSingle Sign-On
5 ndash ndash ndash ndash
Citrix Manual Authentication
Citrix Manual Authentication with SingleSign-On
5 ndash ndash ndash ndash
1 Active Directory support includes both single domain and multi-domain support unless otherwise noted2 RADIUS and SecurID support includes support for both one-time passphrases and challengeresponse
authentication integrated with RADIUS In many cases SecurID can also be used with other RADIUSimplementations including Vasco
3 The Shrew Soft client does not support two-factor authentication4 Fireware supports RADIUS Filter ID 11 for group authentication5 Both single and multiple domain Active Directory configurations are supported For information about the
supported Operating System compatibility for the WatchGuard TO Agent and SSO Agent see the currentFireware and WSM Operating System Compatibility table
6 Active Directory authentication methods are supported only through a RADIUS server
System RequirementsIf you have WatchGuard SystemManager client software onlyinstalled
If you install WatchGuard SystemManager and WatchGuard Serversoftware
Minimum CPU Intel Core or Xeon
2GHz
Intel Core or Xeon
2GHz
MinimumMemory 1GB 2GB
Minimum AvailableDisk Space
250MB 1GB
MinimumRecommendedScreen Resolution
1024x768 1024x768
FireboxV System RequirementsWith support for installation in both a VMware and a Hyper-V environment aWatchGuard FireboxV virtualmachine can run on a VMware ESXi 55 60 or 65 host or onWindows Server 2012 R2 or 2016 or Hyper-VServer 2012 R2 or 2016
The hardware requirements for FireboxV are the same as for the hypervisor environment it runs in
Each FireboxV virtual machine requires 5 GB of disk space CPU andmemory requirements vary by model
FireboxV Model vCPUs (maximum) Memory (recommended)
Small 2 2048MB
Medium 4 4096MB
Large 8 4096MB
Extra Large 16 4096MB
System requirements for XTMv are included in Fireware Help
Fireware andWSM v1213 Operating System Compatibility
8 WatchGuard Technologies Inc
Downloading Software
Release Notes 9
Downloading SoftwareYou can download software from theWatchGuard Software Downloads Center
There are several software files available for download with this release See the descriptions below so youknow what software packages you will need for your upgrade
WatchGuard System ManagerWith this software package you can install WSM and theWatchGuard Server Center software
WSM12_1_3exemdashUse this file to install WSM v1213 or to upgradeWatchGuard SystemManagerfrom an earlier version toWSM v1213
Fireware OSIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from the FirewareWebUI System gt Upgrade OS page
If you prefer to upgrade from Policy Manager or from an earlier version of Fireware you can use download theFireware OS image for your Firebox or XTM device Use the exe file if you want to install or upgrade theOSusingWSM Use the zip file if you want to install or upgrade theOS manually using FirewareWebUI Use theova or vhd file to deploy a new XTMv device
If you havehellip Select from these Fireware OS packages
Firebox M5600 Firebox_OS_M4600_M5600_12_1_3exefirebox_M4600_M5600_12_1_3zip
Firebox M4600 Firebox_OS_M4600_M5600_12_1_3exefirebox_M4600_M5600_12_1_3zip
Firebox M670 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M570 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M500 Firebox_OS_M400_M500_12_1_3exefirebox_M400_M500_12_1_3zip
Firebox M470 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M440 Firebox_OS_M440_12_1_3exefirebox_M440_12_1_3zip
Firebox M400 Firebox_OS_M400_M500_12_1_3exefirebox_M400_M500_12_1_3zip
Firebox M370 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M300 Firebox_OS_M200_M300_12_1_3exefirebox_M200_M300_12_1_3zip
Firebox M200 Firebox_OS_M200_M300_12_1_3exefirebox_M200_M300_12_1_3zip
Firebox T70 Firebox_OS_T70_12_1_3exefirebox_T70_12_1_3zip
Firebox T55 Firebox_OS_T55_12_1_3exefirebox_T55_12_1_3zip
Firebox T50 Firebox_OS_T30_T50_12_1_3exefirebox_T30_T50_12_1_3zip
Firebox T35 Firebox_OS_T35_12_1_3exefirebox_T35_12_1_3zip
Firebox T30 Firebox_OS_T30_T50_12_1_3exefirebox_T30_T50_12_1_3zip
Firebox T15 Firebox_OS_T15_12_1_3exefirebox_T15_12_1_3zip
Firebox T10 Firebox_OS_T10_12_1_3exefirebox_T10_12_1_3zip
Downloading Software
10 WatchGuard Technologies Inc
Downloading Software
Release Notes 11
If you havehellip Select from these Fireware OS packages
FireboxVAll editions for VMware
FireboxV_12_1_3ovaXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
FireboxVAll editions for Hyper-V
FireboxV_12_1_3_vhdzipXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
Firebox Cloud FireboxCloud_12_1_3zip
XTM 2500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 2050 XTM_OS_XTM2050_12_1_3exextm_xtm2050_12_1_3zip
XTM 1500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 1050 XTM_OS_XTM1050_12_1_3exextm_xtm1050_12_1_3zip
XTM 800 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 8Series XTM_OS_XTM8_12_1_3exextm_xtm8_12_1_3zip
XTM 5Series Models515 525 535 and 545only
XTM_OS_XTM5_12_1_3exextm_xtm5_12_1_3zip
XTM 330 XTM_OS_XTM330_12_1_3exextm_xtm330_12_1_3zip
XTM 33 XTM_OS_XTM3_12_1_3exextm_xtm3_12_1_3zip
XTM 2526 XTM_OS_XTM2A6_12_1_3exextm_xtm2a6_12_1_3zip
XTMvAll editions for VMware
xtmv_12_1_3ovaXTM_OS_xtmv_12_1_3exextm_xtmv_12_1_3zip
XTMvAll editions for Hyper-V
xtmv_12_1_3_vhdzipXTM_OS_XTMv_12_1_3exextm_xtmv_12_1_3zip
Single Sign-On SoftwareThese files are available for Single Sign-On There are no updates with the v1213 release
l WG-Authentication-Gateway_12_0exe (SSOAgent software - required for Single Sign-On andincludes optional Event LogMonitor for clientless SSO)
l WG-Authentication-Client_11122msi (SSOClient software forWindows)l WG-SSOCLIENT-MAC_12_0dmg (SSOClient software for Mac OS X)l SSOExchangeMonitor_x86_12_0exe (ExchangeMonitor for 32-bit operating systems)l SSOExchangeMonitor_x64_12_0exe (ExchangeMonitor for 64-bit operating systems)
For information about how to install and set up Single Sign-On see the product documentation
Terminal Services Authentication SoftwareThis file is not updated with the Fireware v1213 release
l TO_AGENT_SETUP_11_12exe (This installer includes both 32-bit and 64-bit file support)
Mobile VPN with SSL Client for Windows and MacThere are two files available for download if you useMobile VPN with SSL
l WG-MVPN-SSL_12_0exe (Client software forWindows)l WG-MVPN-SSL_12_0dmg (Client software for Mac)
Mobile VPN with IPSec client for Windows and MacThere are several available files to download
Shrew Soft Client
l Shrew Soft Client 222 for Windows - No client license required
WatchGuard IPSec Mobile VPN Clients
The current WatchGuard IPSec Mobile VPN Client forWindows version is 1213
l WatchGuard IPSec Mobile VPN Client for Windows (32-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
l WatchGuard IPSec Mobile VPN Client for Windows (64-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
The current macOS client version is 300
l WatchGuard IPSec Mobile VPN Client for macOS powered by NCP - There is a license requiredfor this premium client with a 30-day free trial available with download
WatchGuard Mobile VPN License Server
l WatchGuard Mobile VPN License Server (MVLS) v20 powered by NCP- Click here for moreinformation about MVLS If you have a VPN bundle ID for macOS it must be updated on the licenseserver to support the new macOS 300 client To update your bundle ID contact WatchGuard CustomerSupport Make sure to have your existing bundle ID available to expedite the update
Downloading Software
12 WatchGuard Technologies Inc
Upgrade Notes
Release Notes 13
Upgrade Notes
SSLTLS Settings Precedence and InheritanceFour Firebox features use SSLTLS for secure communication and share the sameOpenVPN serverManagement Tunnel over SSL on hub devices BOVPN over TLS in Server mode Mobile VPN with SSL andthe Access Portal These features also share some settings When you enablemore than one of thesefeatures settings for some features have a higher precedence than settings for other features Shared settingsare not configurable for the features with lower precedence For more information see this topic in FirewareHelp
Modem Configurations Converted to External Interfaces with Failover EnabledIf your Firebox was configured for modem failover when you upgrade your Firebox to Fireware v121 or higherthemodem configuration is automatically converted to an external interface with modem failover enabled If allother external interfaces become unavailable traffic automatically fails over to themodem interface Modeminterfaces can also participate in multi-WAN on all devices except the Firebox T10 Firebox T15 and XTM 2Series devices that do not have the Pro upgrade
HTTPS Proxy Content Inspection with Fireware v121With Fireware 121 we updated the HTTPS proxy action to include a Content Inspection Exceptions list whichincludes domains for services such as Dropbox Skype andMicrosoft Office that are known to be incompatiblewith content inspection The HTTPS proxy does not perform content inspection for domains with enabledexceptions on the Content Inspection Exceptions list
When you upgrade your Firebox to Fireware v121 or higher the Content Inspection Exceptions list isautomatically enabled in all HTTPS proxy actions that have content inspection enabled After the upgrade werecommend that you review the Content Inspection Exceptions list in your configured HTTPS proxy actionsand disable the exception for any domain you do not want the HTTPS proxy to allow without content inspectionFor more information seeWhich applications are on the default exception list in an HTTPS proxy action in theKnowledge Base
Gateway AV Engine Upgrade with Fireware v120With Fireware v120 we updated the engine used by Gateway AV to a new engine from BitDefender As aresult any Firebox that upgrades from Fireware v11x version to v120 or later must download a new signatureset which can take 7-10minutes for the first update It can take an additional 5-7minutes to synchronize aFireCluster We recommend that you upgrade to Fireware v12x at a quiet time on your network After the initialupdate signature updates are incremental andmuch faster than in previous versions
While the new signature set is being downloaded network users could experience issues related to GatewayAV scan failures for several minutes after the update and inbound emails sent through the SMTP proxy couldbe locked
XTMv Upgrade NotesYou cannot upgrade an XTMv device to FireboxV For Fireware v1111 and higher the XTMv device is a 64-bitvirtual machine You cannot upgrade an XTMv device from Fireware v1110x or lower to Fireware v1111 orhigher Instead youmust use the OVA file to deploy a new 64-bit Fireware v1111x or v12x XTMv VM andthen use Policy Manager to move the existing configuration from the 32-bit XTMv VM to the 64-bit XTMv VMFor more information about how tomove the configuration or deploy a new XTMv VM see Fireware Help Whenyour XTMv instance has been updated to v1111 or higher you can then use the usual upgrade procedure asdetailed in the next section
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
If your Firebox is a T10 XTM 25 or XTM 26 device with OS version 121 or older youmightnot be able to perform a backup before you upgrade the Firebox This occurs because thememory use by Fireware v121 or older does not leave enoughmemory free to successfullycomplete the upgrade process on these devices For these devices we recommend you savea copy of the xml configuration file with a distinctive name as described here Save theConfiguration File
If you need to downgrade a Firebox without a backup file after you complete the upgrade toFireware v12x we recommend you Downgrade withWebUI This process deletes theconfiguration file but does not remove the device feature keys and certificates After youdowngrade the Firebox you can use Policy Manager to Save the Configuration File to theFireboxIf your Firebox has Fireware v1211 or later the Firebox will temporarily disable somesecurity services to free up enoughmemory to successfully perform a backup To learnmoresee Backup and Restore for XTM 25 XTM 26 and Firebox T10
Important Information about the upgrade process
l We recommend you use FirewareWebUI to upgrade to Fireware v12x You can also use PolicyManager if you prefer
l We strongly recommend that you save a local copy of your Firebox configuration and create a Fireboxbackup image before you upgrade
l If you useWatchGuard SystemManager (WSM) make sure yourWSM version is equal to or higherthan the version of Fireware OS installed on your Firebox and the version of WSM installed on yourManagement Server Also make sure to upgradeWSM before you upgrade the version of Fireware OSon your Firebox
Upgrade to Fireware v1213
14 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 15
If you want to upgrade a Firebox T10 XTM 2Series 33 330 or 5 Series device werecommend that you reboot your Firebox before you upgrade This clears your devicememoryand can prevent many problems commonly associated with upgrades in those devices
Back Up Your WatchGuard ServersIt is not usually necessary to uninstall your previous v11x or v12x server or client software when you upgradetoWSM v12x You can install the v12x server and client software on top of your existing installation toupgrade yourWatchGuard software components We do however strongly recommend that you back up yourWatchGuard Servers (for example yourWatchGuardManagement Server) to a safe location before youupgrade You will need these backup files if you ever want to downgrade
You cannot restore aWatchGuard Server backup file created withWatchGuard SystemManager v12x to to a v11x installation Make sure to retain your older server backup fileswhen you upgrade to v120 or later in case you want to downgrade in the future
To back up your Management Server configuration from the computer where you installed theManagementServer
1 FromWatchGuard Server Center select BackupRestore Management ServerThe WatchGuard Server Center BackupRestore Wizard starts
2 Click NextThe Select an action screen appears
3 Select Back up settings4 Click Next
The Specify a backup file screen appears5 Click Browse to select a location for the backup file Make sure you save the configuration file to a
location you can access later to restore the configuration6 Click Next
The WatchGuard Server Center BackupRestore Wizard is complete screen appears7 Click Finish to exit the wizard
Upgrade to Fireware v1213 fromWeb UIIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from theSystem gt Upgrade OS page If your Firebox is running v119x or earlier use thesesteps to upgrade
1 Before you begin save a local copy of your configuration file2 Go toSystem gt Backup Image or use the USB Backup feature to back up your current device image3 On your management computer launch the OS software file you downloaded from theWatchGuard
Software Downloads pageIf you use theWindows-based installer on a computer with aWindows 64-bit operating system thisinstallation extracts an upgrade file called [product series]_[product code]sysa-dl to the defaultlocation of CProgram Files(x86)Common FilesWatchGuardresourcesFirewareXTM1213[model]or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Connect to your Firebox with theWebUI and select System gt Upgrade OS5 Browse to the location of the [product series]_[product code]sysa-dl from Step 2 and click Upgrade
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v121 3installer twice (once to remove v1213 software and again to install v1213)
Upgrade to Fireware v1213
16 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 17
Upgrade to Fireware v1213 fromWSMPolicy Manager1 Before you begin save a local copy of your configuration file2 Select File gt Backup or use the USB Backup feature to back up your current device image3 On amanagement computer running aWindows 64-bit operating system launch the OS executable file
you downloaded from theWatchGuard Portal This installation extracts an upgrade file called [Firebox orxtm series]_[product code]sysa-dl to the default location of CProgram Files(x86)CommonfilesWatchGuardresourcesFirewareXTM1213[model] or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Install and openWatchGuard SystemManager v1213 Connect to your Firebox and launch PolicyManager
5 From Policy Manager select File gt Upgrade When prompted browse to and select the [productseries]_[product code]sysa-dl file from Step 2
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v1213installer twice (once to remove v1213 software and again to install v1213)
If you like tomake updates to your Firebox configuration from a saved configuration file makesure you open the configuration from the Firebox and save it to a new file after you upgradeThis is to make sure that you do not overwrite any configuration changes that weremade aspart of the upgrade
Other Upgrade IssuesThere is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Fireware v12x is not supported on XTM 5Series devices models 505 510 520 or 530
Before you upgrade to Fireware v12x your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is preventedIf you try to schedule anOS update of managed devices through aManagement Server theupgrade is also preventedIf you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x orv1110x before you upgrade to Fireware v12x or your Firebox will be reset to a default state
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
18 WatchGuard Technologies Inc
Update AP Devices
Release Notes 19
Update AP Devices
OnApril 12 2018 WatchGuard released AP firmware versions 12915 for the AP100 AP102and AP200 and 20010 for the AP300 to address security vulnerabilities We highlyrecommend you install these AP firmware updates For more detailed information on thesevulnerabilities see AP100AP102AP200 Chained Vulnerabilities In addition to addressingthese vulnerabilities the AP firmware updates disable the AP local web UI As these APmodels can only bemanaged with the Gateway Wireless Controller the AP local web UI is nolonger supported
Beginning with Fireware v11124 AP firmware is no longer bundled with Fireware OS All AP device firmwareis managed by the Gateway Wireless Controller on your Firebox TheGateway Wireless Controllerautomatically checks for new AP firmware updates and enables you to download the firmware directly fromWatchGuard servers
Important Upgrade StepsIf you have not previously upgraded to Fireware 1201 or higher and the latest AP firmware youmust performthese steps
1 Make sure all your APs are online You can check AP status from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager selecttheGateway Wireless Controller tab
2 Make sure you are not using insecure default AP passphrases such as wgwap orwatchguard Yourcurrent AP passphrasemust be secure and at least 8 characters in length You can change your APpassphrase inNetwork gt Gateway Wireless Controller gt Settings
If you do not have a secure passphrase correctly configured before the upgrade you will losethemanagement connection with your deployed APs If this occurs youmust physicallyreset the APs to factory default settings to be able tomanage the APs from GatewayWireless Controller
Depending on the version of Fireware you are upgrading from youmay need tomark APs as trusted after theupgrade to Fireware v1201 or higher You canmark APs as trusted from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager select theGateway Wireless Controller tab
AP Firmware UpgradeThe current AP firmware versions for each AP devicemodel are
AP Device Model Current Firmware Version
AP100 AP102 AP200 12915
AP300 20010
AP120 AP320 AP322 AP325AP420
850-646
Tomanage AP firmware and download the latest AP firmware to your Firebox
n From FirewareWebUI select Dashboard gt Gateway Wireless Controller From theSummary tabclick Manage Firmware
n From Firebox SystemManager select theGateway Wireless Controller tab then click ManageFirmware
Note that you cannot upgrade an AP120 AP320 AP322 or AP420 to 830-657 or higher unless your Firebox isrunning Fireware v11124 or higher If your Firebox does not run v11124 or higher you will not see an optionto upgrade to AP firmware v830-657 or higher
If you have enabled automatic AP device firmware updates in Gateway Wireless Controller your AP devicesare automatically updated betweenmidnight and 400am local time
Tomanually update firmware on your AP devices
1 On theAccess Points tab select one or more AP devices2 From theActions drop-down list click Upgrade3 Click Yes to confirm that you want to upgrade the AP device
Update AP Devices
20 WatchGuard Technologies Inc
Upgrade your FireCluster to Fireware v1213
Release Notes 21
Upgrade your FireCluster to Fireware v1213You can upgrade Fireware OS for a FireCluster from Policy Manager or FirewareWebUI To upgrade aFireCluster from Fireware v1110x or lower we recommend you use Policy Manager
As part of the upgrade process each cluster member reboots and rejoins the cluster Because the clustercannot do load balancing while a cluster member reboot is in progress we recommend you upgrade anactiveactive cluster at a time when the network traffic is lightest
For information on how to upgrade your FireCluster see this Help topic
There is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Before you upgrade to Fireware v1111 or higher your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is prevented
If you try to schedule anOS update of managed devices through aManagement Server theupgrade is also prevented
If you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x before youupgrade to Fireware v1111x or higher or your Firebox will be reset to a default state
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
1 Active Directory support includes both single domain and multi-domain support unless otherwise noted2 RADIUS and SecurID support includes support for both one-time passphrases and challengeresponse
authentication integrated with RADIUS In many cases SecurID can also be used with other RADIUSimplementations including Vasco
3 The Shrew Soft client does not support two-factor authentication4 Fireware supports RADIUS Filter ID 11 for group authentication5 Both single and multiple domain Active Directory configurations are supported For information about the
supported Operating System compatibility for the WatchGuard TO Agent and SSO Agent see the currentFireware and WSM Operating System Compatibility table
6 Active Directory authentication methods are supported only through a RADIUS server
System RequirementsIf you have WatchGuard SystemManager client software onlyinstalled
If you install WatchGuard SystemManager and WatchGuard Serversoftware
Minimum CPU Intel Core or Xeon
2GHz
Intel Core or Xeon
2GHz
MinimumMemory 1GB 2GB
Minimum AvailableDisk Space
250MB 1GB
MinimumRecommendedScreen Resolution
1024x768 1024x768
FireboxV System RequirementsWith support for installation in both a VMware and a Hyper-V environment aWatchGuard FireboxV virtualmachine can run on a VMware ESXi 55 60 or 65 host or onWindows Server 2012 R2 or 2016 or Hyper-VServer 2012 R2 or 2016
The hardware requirements for FireboxV are the same as for the hypervisor environment it runs in
Each FireboxV virtual machine requires 5 GB of disk space CPU andmemory requirements vary by model
FireboxV Model vCPUs (maximum) Memory (recommended)
Small 2 2048MB
Medium 4 4096MB
Large 8 4096MB
Extra Large 16 4096MB
System requirements for XTMv are included in Fireware Help
Fireware andWSM v1213 Operating System Compatibility
8 WatchGuard Technologies Inc
Downloading Software
Release Notes 9
Downloading SoftwareYou can download software from theWatchGuard Software Downloads Center
There are several software files available for download with this release See the descriptions below so youknow what software packages you will need for your upgrade
WatchGuard System ManagerWith this software package you can install WSM and theWatchGuard Server Center software
WSM12_1_3exemdashUse this file to install WSM v1213 or to upgradeWatchGuard SystemManagerfrom an earlier version toWSM v1213
Fireware OSIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from the FirewareWebUI System gt Upgrade OS page
If you prefer to upgrade from Policy Manager or from an earlier version of Fireware you can use download theFireware OS image for your Firebox or XTM device Use the exe file if you want to install or upgrade theOSusingWSM Use the zip file if you want to install or upgrade theOS manually using FirewareWebUI Use theova or vhd file to deploy a new XTMv device
If you havehellip Select from these Fireware OS packages
Firebox M5600 Firebox_OS_M4600_M5600_12_1_3exefirebox_M4600_M5600_12_1_3zip
Firebox M4600 Firebox_OS_M4600_M5600_12_1_3exefirebox_M4600_M5600_12_1_3zip
Firebox M670 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M570 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M500 Firebox_OS_M400_M500_12_1_3exefirebox_M400_M500_12_1_3zip
Firebox M470 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M440 Firebox_OS_M440_12_1_3exefirebox_M440_12_1_3zip
Firebox M400 Firebox_OS_M400_M500_12_1_3exefirebox_M400_M500_12_1_3zip
Firebox M370 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M300 Firebox_OS_M200_M300_12_1_3exefirebox_M200_M300_12_1_3zip
Firebox M200 Firebox_OS_M200_M300_12_1_3exefirebox_M200_M300_12_1_3zip
Firebox T70 Firebox_OS_T70_12_1_3exefirebox_T70_12_1_3zip
Firebox T55 Firebox_OS_T55_12_1_3exefirebox_T55_12_1_3zip
Firebox T50 Firebox_OS_T30_T50_12_1_3exefirebox_T30_T50_12_1_3zip
Firebox T35 Firebox_OS_T35_12_1_3exefirebox_T35_12_1_3zip
Firebox T30 Firebox_OS_T30_T50_12_1_3exefirebox_T30_T50_12_1_3zip
Firebox T15 Firebox_OS_T15_12_1_3exefirebox_T15_12_1_3zip
Firebox T10 Firebox_OS_T10_12_1_3exefirebox_T10_12_1_3zip
Downloading Software
10 WatchGuard Technologies Inc
Downloading Software
Release Notes 11
If you havehellip Select from these Fireware OS packages
FireboxVAll editions for VMware
FireboxV_12_1_3ovaXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
FireboxVAll editions for Hyper-V
FireboxV_12_1_3_vhdzipXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
Firebox Cloud FireboxCloud_12_1_3zip
XTM 2500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 2050 XTM_OS_XTM2050_12_1_3exextm_xtm2050_12_1_3zip
XTM 1500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 1050 XTM_OS_XTM1050_12_1_3exextm_xtm1050_12_1_3zip
XTM 800 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 8Series XTM_OS_XTM8_12_1_3exextm_xtm8_12_1_3zip
XTM 5Series Models515 525 535 and 545only
XTM_OS_XTM5_12_1_3exextm_xtm5_12_1_3zip
XTM 330 XTM_OS_XTM330_12_1_3exextm_xtm330_12_1_3zip
XTM 33 XTM_OS_XTM3_12_1_3exextm_xtm3_12_1_3zip
XTM 2526 XTM_OS_XTM2A6_12_1_3exextm_xtm2a6_12_1_3zip
XTMvAll editions for VMware
xtmv_12_1_3ovaXTM_OS_xtmv_12_1_3exextm_xtmv_12_1_3zip
XTMvAll editions for Hyper-V
xtmv_12_1_3_vhdzipXTM_OS_XTMv_12_1_3exextm_xtmv_12_1_3zip
Single Sign-On SoftwareThese files are available for Single Sign-On There are no updates with the v1213 release
l WG-Authentication-Gateway_12_0exe (SSOAgent software - required for Single Sign-On andincludes optional Event LogMonitor for clientless SSO)
l WG-Authentication-Client_11122msi (SSOClient software forWindows)l WG-SSOCLIENT-MAC_12_0dmg (SSOClient software for Mac OS X)l SSOExchangeMonitor_x86_12_0exe (ExchangeMonitor for 32-bit operating systems)l SSOExchangeMonitor_x64_12_0exe (ExchangeMonitor for 64-bit operating systems)
For information about how to install and set up Single Sign-On see the product documentation
Terminal Services Authentication SoftwareThis file is not updated with the Fireware v1213 release
l TO_AGENT_SETUP_11_12exe (This installer includes both 32-bit and 64-bit file support)
Mobile VPN with SSL Client for Windows and MacThere are two files available for download if you useMobile VPN with SSL
l WG-MVPN-SSL_12_0exe (Client software forWindows)l WG-MVPN-SSL_12_0dmg (Client software for Mac)
Mobile VPN with IPSec client for Windows and MacThere are several available files to download
Shrew Soft Client
l Shrew Soft Client 222 for Windows - No client license required
WatchGuard IPSec Mobile VPN Clients
The current WatchGuard IPSec Mobile VPN Client forWindows version is 1213
l WatchGuard IPSec Mobile VPN Client for Windows (32-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
l WatchGuard IPSec Mobile VPN Client for Windows (64-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
The current macOS client version is 300
l WatchGuard IPSec Mobile VPN Client for macOS powered by NCP - There is a license requiredfor this premium client with a 30-day free trial available with download
WatchGuard Mobile VPN License Server
l WatchGuard Mobile VPN License Server (MVLS) v20 powered by NCP- Click here for moreinformation about MVLS If you have a VPN bundle ID for macOS it must be updated on the licenseserver to support the new macOS 300 client To update your bundle ID contact WatchGuard CustomerSupport Make sure to have your existing bundle ID available to expedite the update
Downloading Software
12 WatchGuard Technologies Inc
Upgrade Notes
Release Notes 13
Upgrade Notes
SSLTLS Settings Precedence and InheritanceFour Firebox features use SSLTLS for secure communication and share the sameOpenVPN serverManagement Tunnel over SSL on hub devices BOVPN over TLS in Server mode Mobile VPN with SSL andthe Access Portal These features also share some settings When you enablemore than one of thesefeatures settings for some features have a higher precedence than settings for other features Shared settingsare not configurable for the features with lower precedence For more information see this topic in FirewareHelp
Modem Configurations Converted to External Interfaces with Failover EnabledIf your Firebox was configured for modem failover when you upgrade your Firebox to Fireware v121 or higherthemodem configuration is automatically converted to an external interface with modem failover enabled If allother external interfaces become unavailable traffic automatically fails over to themodem interface Modeminterfaces can also participate in multi-WAN on all devices except the Firebox T10 Firebox T15 and XTM 2Series devices that do not have the Pro upgrade
HTTPS Proxy Content Inspection with Fireware v121With Fireware 121 we updated the HTTPS proxy action to include a Content Inspection Exceptions list whichincludes domains for services such as Dropbox Skype andMicrosoft Office that are known to be incompatiblewith content inspection The HTTPS proxy does not perform content inspection for domains with enabledexceptions on the Content Inspection Exceptions list
When you upgrade your Firebox to Fireware v121 or higher the Content Inspection Exceptions list isautomatically enabled in all HTTPS proxy actions that have content inspection enabled After the upgrade werecommend that you review the Content Inspection Exceptions list in your configured HTTPS proxy actionsand disable the exception for any domain you do not want the HTTPS proxy to allow without content inspectionFor more information seeWhich applications are on the default exception list in an HTTPS proxy action in theKnowledge Base
Gateway AV Engine Upgrade with Fireware v120With Fireware v120 we updated the engine used by Gateway AV to a new engine from BitDefender As aresult any Firebox that upgrades from Fireware v11x version to v120 or later must download a new signatureset which can take 7-10minutes for the first update It can take an additional 5-7minutes to synchronize aFireCluster We recommend that you upgrade to Fireware v12x at a quiet time on your network After the initialupdate signature updates are incremental andmuch faster than in previous versions
While the new signature set is being downloaded network users could experience issues related to GatewayAV scan failures for several minutes after the update and inbound emails sent through the SMTP proxy couldbe locked
XTMv Upgrade NotesYou cannot upgrade an XTMv device to FireboxV For Fireware v1111 and higher the XTMv device is a 64-bitvirtual machine You cannot upgrade an XTMv device from Fireware v1110x or lower to Fireware v1111 orhigher Instead youmust use the OVA file to deploy a new 64-bit Fireware v1111x or v12x XTMv VM andthen use Policy Manager to move the existing configuration from the 32-bit XTMv VM to the 64-bit XTMv VMFor more information about how tomove the configuration or deploy a new XTMv VM see Fireware Help Whenyour XTMv instance has been updated to v1111 or higher you can then use the usual upgrade procedure asdetailed in the next section
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
If your Firebox is a T10 XTM 25 or XTM 26 device with OS version 121 or older youmightnot be able to perform a backup before you upgrade the Firebox This occurs because thememory use by Fireware v121 or older does not leave enoughmemory free to successfullycomplete the upgrade process on these devices For these devices we recommend you savea copy of the xml configuration file with a distinctive name as described here Save theConfiguration File
If you need to downgrade a Firebox without a backup file after you complete the upgrade toFireware v12x we recommend you Downgrade withWebUI This process deletes theconfiguration file but does not remove the device feature keys and certificates After youdowngrade the Firebox you can use Policy Manager to Save the Configuration File to theFireboxIf your Firebox has Fireware v1211 or later the Firebox will temporarily disable somesecurity services to free up enoughmemory to successfully perform a backup To learnmoresee Backup and Restore for XTM 25 XTM 26 and Firebox T10
Important Information about the upgrade process
l We recommend you use FirewareWebUI to upgrade to Fireware v12x You can also use PolicyManager if you prefer
l We strongly recommend that you save a local copy of your Firebox configuration and create a Fireboxbackup image before you upgrade
l If you useWatchGuard SystemManager (WSM) make sure yourWSM version is equal to or higherthan the version of Fireware OS installed on your Firebox and the version of WSM installed on yourManagement Server Also make sure to upgradeWSM before you upgrade the version of Fireware OSon your Firebox
Upgrade to Fireware v1213
14 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 15
If you want to upgrade a Firebox T10 XTM 2Series 33 330 or 5 Series device werecommend that you reboot your Firebox before you upgrade This clears your devicememoryand can prevent many problems commonly associated with upgrades in those devices
Back Up Your WatchGuard ServersIt is not usually necessary to uninstall your previous v11x or v12x server or client software when you upgradetoWSM v12x You can install the v12x server and client software on top of your existing installation toupgrade yourWatchGuard software components We do however strongly recommend that you back up yourWatchGuard Servers (for example yourWatchGuardManagement Server) to a safe location before youupgrade You will need these backup files if you ever want to downgrade
You cannot restore aWatchGuard Server backup file created withWatchGuard SystemManager v12x to to a v11x installation Make sure to retain your older server backup fileswhen you upgrade to v120 or later in case you want to downgrade in the future
To back up your Management Server configuration from the computer where you installed theManagementServer
1 FromWatchGuard Server Center select BackupRestore Management ServerThe WatchGuard Server Center BackupRestore Wizard starts
2 Click NextThe Select an action screen appears
3 Select Back up settings4 Click Next
The Specify a backup file screen appears5 Click Browse to select a location for the backup file Make sure you save the configuration file to a
location you can access later to restore the configuration6 Click Next
The WatchGuard Server Center BackupRestore Wizard is complete screen appears7 Click Finish to exit the wizard
Upgrade to Fireware v1213 fromWeb UIIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from theSystem gt Upgrade OS page If your Firebox is running v119x or earlier use thesesteps to upgrade
1 Before you begin save a local copy of your configuration file2 Go toSystem gt Backup Image or use the USB Backup feature to back up your current device image3 On your management computer launch the OS software file you downloaded from theWatchGuard
Software Downloads pageIf you use theWindows-based installer on a computer with aWindows 64-bit operating system thisinstallation extracts an upgrade file called [product series]_[product code]sysa-dl to the defaultlocation of CProgram Files(x86)Common FilesWatchGuardresourcesFirewareXTM1213[model]or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Connect to your Firebox with theWebUI and select System gt Upgrade OS5 Browse to the location of the [product series]_[product code]sysa-dl from Step 2 and click Upgrade
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v121 3installer twice (once to remove v1213 software and again to install v1213)
Upgrade to Fireware v1213
16 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 17
Upgrade to Fireware v1213 fromWSMPolicy Manager1 Before you begin save a local copy of your configuration file2 Select File gt Backup or use the USB Backup feature to back up your current device image3 On amanagement computer running aWindows 64-bit operating system launch the OS executable file
you downloaded from theWatchGuard Portal This installation extracts an upgrade file called [Firebox orxtm series]_[product code]sysa-dl to the default location of CProgram Files(x86)CommonfilesWatchGuardresourcesFirewareXTM1213[model] or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Install and openWatchGuard SystemManager v1213 Connect to your Firebox and launch PolicyManager
5 From Policy Manager select File gt Upgrade When prompted browse to and select the [productseries]_[product code]sysa-dl file from Step 2
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v1213installer twice (once to remove v1213 software and again to install v1213)
If you like tomake updates to your Firebox configuration from a saved configuration file makesure you open the configuration from the Firebox and save it to a new file after you upgradeThis is to make sure that you do not overwrite any configuration changes that weremade aspart of the upgrade
Other Upgrade IssuesThere is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Fireware v12x is not supported on XTM 5Series devices models 505 510 520 or 530
Before you upgrade to Fireware v12x your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is preventedIf you try to schedule anOS update of managed devices through aManagement Server theupgrade is also preventedIf you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x orv1110x before you upgrade to Fireware v12x or your Firebox will be reset to a default state
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
18 WatchGuard Technologies Inc
Update AP Devices
Release Notes 19
Update AP Devices
OnApril 12 2018 WatchGuard released AP firmware versions 12915 for the AP100 AP102and AP200 and 20010 for the AP300 to address security vulnerabilities We highlyrecommend you install these AP firmware updates For more detailed information on thesevulnerabilities see AP100AP102AP200 Chained Vulnerabilities In addition to addressingthese vulnerabilities the AP firmware updates disable the AP local web UI As these APmodels can only bemanaged with the Gateway Wireless Controller the AP local web UI is nolonger supported
Beginning with Fireware v11124 AP firmware is no longer bundled with Fireware OS All AP device firmwareis managed by the Gateway Wireless Controller on your Firebox TheGateway Wireless Controllerautomatically checks for new AP firmware updates and enables you to download the firmware directly fromWatchGuard servers
Important Upgrade StepsIf you have not previously upgraded to Fireware 1201 or higher and the latest AP firmware youmust performthese steps
1 Make sure all your APs are online You can check AP status from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager selecttheGateway Wireless Controller tab
2 Make sure you are not using insecure default AP passphrases such as wgwap orwatchguard Yourcurrent AP passphrasemust be secure and at least 8 characters in length You can change your APpassphrase inNetwork gt Gateway Wireless Controller gt Settings
If you do not have a secure passphrase correctly configured before the upgrade you will losethemanagement connection with your deployed APs If this occurs youmust physicallyreset the APs to factory default settings to be able tomanage the APs from GatewayWireless Controller
Depending on the version of Fireware you are upgrading from youmay need tomark APs as trusted after theupgrade to Fireware v1201 or higher You canmark APs as trusted from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager select theGateway Wireless Controller tab
AP Firmware UpgradeThe current AP firmware versions for each AP devicemodel are
AP Device Model Current Firmware Version
AP100 AP102 AP200 12915
AP300 20010
AP120 AP320 AP322 AP325AP420
850-646
Tomanage AP firmware and download the latest AP firmware to your Firebox
n From FirewareWebUI select Dashboard gt Gateway Wireless Controller From theSummary tabclick Manage Firmware
n From Firebox SystemManager select theGateway Wireless Controller tab then click ManageFirmware
Note that you cannot upgrade an AP120 AP320 AP322 or AP420 to 830-657 or higher unless your Firebox isrunning Fireware v11124 or higher If your Firebox does not run v11124 or higher you will not see an optionto upgrade to AP firmware v830-657 or higher
If you have enabled automatic AP device firmware updates in Gateway Wireless Controller your AP devicesare automatically updated betweenmidnight and 400am local time
Tomanually update firmware on your AP devices
1 On theAccess Points tab select one or more AP devices2 From theActions drop-down list click Upgrade3 Click Yes to confirm that you want to upgrade the AP device
Update AP Devices
20 WatchGuard Technologies Inc
Upgrade your FireCluster to Fireware v1213
Release Notes 21
Upgrade your FireCluster to Fireware v1213You can upgrade Fireware OS for a FireCluster from Policy Manager or FirewareWebUI To upgrade aFireCluster from Fireware v1110x or lower we recommend you use Policy Manager
As part of the upgrade process each cluster member reboots and rejoins the cluster Because the clustercannot do load balancing while a cluster member reboot is in progress we recommend you upgrade anactiveactive cluster at a time when the network traffic is lightest
For information on how to upgrade your FireCluster see this Help topic
There is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Before you upgrade to Fireware v1111 or higher your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is prevented
If you try to schedule anOS update of managed devices through aManagement Server theupgrade is also prevented
If you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x before youupgrade to Fireware v1111x or higher or your Firebox will be reset to a default state
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
Downloading Software
Release Notes 9
Downloading SoftwareYou can download software from theWatchGuard Software Downloads Center
There are several software files available for download with this release See the descriptions below so youknow what software packages you will need for your upgrade
WatchGuard System ManagerWith this software package you can install WSM and theWatchGuard Server Center software
WSM12_1_3exemdashUse this file to install WSM v1213 or to upgradeWatchGuard SystemManagerfrom an earlier version toWSM v1213
Fireware OSIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from the FirewareWebUI System gt Upgrade OS page
If you prefer to upgrade from Policy Manager or from an earlier version of Fireware you can use download theFireware OS image for your Firebox or XTM device Use the exe file if you want to install or upgrade theOSusingWSM Use the zip file if you want to install or upgrade theOS manually using FirewareWebUI Use theova or vhd file to deploy a new XTMv device
If you havehellip Select from these Fireware OS packages
Firebox M5600 Firebox_OS_M4600_M5600_12_1_3exefirebox_M4600_M5600_12_1_3zip
Firebox M4600 Firebox_OS_M4600_M5600_12_1_3exefirebox_M4600_M5600_12_1_3zip
Firebox M670 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M570 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M500 Firebox_OS_M400_M500_12_1_3exefirebox_M400_M500_12_1_3zip
Firebox M470 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M440 Firebox_OS_M440_12_1_3exefirebox_M440_12_1_3zip
Firebox M400 Firebox_OS_M400_M500_12_1_3exefirebox_M400_M500_12_1_3zip
Firebox M370 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M300 Firebox_OS_M200_M300_12_1_3exefirebox_M200_M300_12_1_3zip
Firebox M200 Firebox_OS_M200_M300_12_1_3exefirebox_M200_M300_12_1_3zip
Firebox T70 Firebox_OS_T70_12_1_3exefirebox_T70_12_1_3zip
Firebox T55 Firebox_OS_T55_12_1_3exefirebox_T55_12_1_3zip
Firebox T50 Firebox_OS_T30_T50_12_1_3exefirebox_T30_T50_12_1_3zip
Firebox T35 Firebox_OS_T35_12_1_3exefirebox_T35_12_1_3zip
Firebox T30 Firebox_OS_T30_T50_12_1_3exefirebox_T30_T50_12_1_3zip
Firebox T15 Firebox_OS_T15_12_1_3exefirebox_T15_12_1_3zip
Firebox T10 Firebox_OS_T10_12_1_3exefirebox_T10_12_1_3zip
Downloading Software
10 WatchGuard Technologies Inc
Downloading Software
Release Notes 11
If you havehellip Select from these Fireware OS packages
FireboxVAll editions for VMware
FireboxV_12_1_3ovaXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
FireboxVAll editions for Hyper-V
FireboxV_12_1_3_vhdzipXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
Firebox Cloud FireboxCloud_12_1_3zip
XTM 2500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 2050 XTM_OS_XTM2050_12_1_3exextm_xtm2050_12_1_3zip
XTM 1500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 1050 XTM_OS_XTM1050_12_1_3exextm_xtm1050_12_1_3zip
XTM 800 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 8Series XTM_OS_XTM8_12_1_3exextm_xtm8_12_1_3zip
XTM 5Series Models515 525 535 and 545only
XTM_OS_XTM5_12_1_3exextm_xtm5_12_1_3zip
XTM 330 XTM_OS_XTM330_12_1_3exextm_xtm330_12_1_3zip
XTM 33 XTM_OS_XTM3_12_1_3exextm_xtm3_12_1_3zip
XTM 2526 XTM_OS_XTM2A6_12_1_3exextm_xtm2a6_12_1_3zip
XTMvAll editions for VMware
xtmv_12_1_3ovaXTM_OS_xtmv_12_1_3exextm_xtmv_12_1_3zip
XTMvAll editions for Hyper-V
xtmv_12_1_3_vhdzipXTM_OS_XTMv_12_1_3exextm_xtmv_12_1_3zip
Single Sign-On SoftwareThese files are available for Single Sign-On There are no updates with the v1213 release
l WG-Authentication-Gateway_12_0exe (SSOAgent software - required for Single Sign-On andincludes optional Event LogMonitor for clientless SSO)
l WG-Authentication-Client_11122msi (SSOClient software forWindows)l WG-SSOCLIENT-MAC_12_0dmg (SSOClient software for Mac OS X)l SSOExchangeMonitor_x86_12_0exe (ExchangeMonitor for 32-bit operating systems)l SSOExchangeMonitor_x64_12_0exe (ExchangeMonitor for 64-bit operating systems)
For information about how to install and set up Single Sign-On see the product documentation
Terminal Services Authentication SoftwareThis file is not updated with the Fireware v1213 release
l TO_AGENT_SETUP_11_12exe (This installer includes both 32-bit and 64-bit file support)
Mobile VPN with SSL Client for Windows and MacThere are two files available for download if you useMobile VPN with SSL
l WG-MVPN-SSL_12_0exe (Client software forWindows)l WG-MVPN-SSL_12_0dmg (Client software for Mac)
Mobile VPN with IPSec client for Windows and MacThere are several available files to download
Shrew Soft Client
l Shrew Soft Client 222 for Windows - No client license required
WatchGuard IPSec Mobile VPN Clients
The current WatchGuard IPSec Mobile VPN Client forWindows version is 1213
l WatchGuard IPSec Mobile VPN Client for Windows (32-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
l WatchGuard IPSec Mobile VPN Client for Windows (64-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
The current macOS client version is 300
l WatchGuard IPSec Mobile VPN Client for macOS powered by NCP - There is a license requiredfor this premium client with a 30-day free trial available with download
WatchGuard Mobile VPN License Server
l WatchGuard Mobile VPN License Server (MVLS) v20 powered by NCP- Click here for moreinformation about MVLS If you have a VPN bundle ID for macOS it must be updated on the licenseserver to support the new macOS 300 client To update your bundle ID contact WatchGuard CustomerSupport Make sure to have your existing bundle ID available to expedite the update
Downloading Software
12 WatchGuard Technologies Inc
Upgrade Notes
Release Notes 13
Upgrade Notes
SSLTLS Settings Precedence and InheritanceFour Firebox features use SSLTLS for secure communication and share the sameOpenVPN serverManagement Tunnel over SSL on hub devices BOVPN over TLS in Server mode Mobile VPN with SSL andthe Access Portal These features also share some settings When you enablemore than one of thesefeatures settings for some features have a higher precedence than settings for other features Shared settingsare not configurable for the features with lower precedence For more information see this topic in FirewareHelp
Modem Configurations Converted to External Interfaces with Failover EnabledIf your Firebox was configured for modem failover when you upgrade your Firebox to Fireware v121 or higherthemodem configuration is automatically converted to an external interface with modem failover enabled If allother external interfaces become unavailable traffic automatically fails over to themodem interface Modeminterfaces can also participate in multi-WAN on all devices except the Firebox T10 Firebox T15 and XTM 2Series devices that do not have the Pro upgrade
HTTPS Proxy Content Inspection with Fireware v121With Fireware 121 we updated the HTTPS proxy action to include a Content Inspection Exceptions list whichincludes domains for services such as Dropbox Skype andMicrosoft Office that are known to be incompatiblewith content inspection The HTTPS proxy does not perform content inspection for domains with enabledexceptions on the Content Inspection Exceptions list
When you upgrade your Firebox to Fireware v121 or higher the Content Inspection Exceptions list isautomatically enabled in all HTTPS proxy actions that have content inspection enabled After the upgrade werecommend that you review the Content Inspection Exceptions list in your configured HTTPS proxy actionsand disable the exception for any domain you do not want the HTTPS proxy to allow without content inspectionFor more information seeWhich applications are on the default exception list in an HTTPS proxy action in theKnowledge Base
Gateway AV Engine Upgrade with Fireware v120With Fireware v120 we updated the engine used by Gateway AV to a new engine from BitDefender As aresult any Firebox that upgrades from Fireware v11x version to v120 or later must download a new signatureset which can take 7-10minutes for the first update It can take an additional 5-7minutes to synchronize aFireCluster We recommend that you upgrade to Fireware v12x at a quiet time on your network After the initialupdate signature updates are incremental andmuch faster than in previous versions
While the new signature set is being downloaded network users could experience issues related to GatewayAV scan failures for several minutes after the update and inbound emails sent through the SMTP proxy couldbe locked
XTMv Upgrade NotesYou cannot upgrade an XTMv device to FireboxV For Fireware v1111 and higher the XTMv device is a 64-bitvirtual machine You cannot upgrade an XTMv device from Fireware v1110x or lower to Fireware v1111 orhigher Instead youmust use the OVA file to deploy a new 64-bit Fireware v1111x or v12x XTMv VM andthen use Policy Manager to move the existing configuration from the 32-bit XTMv VM to the 64-bit XTMv VMFor more information about how tomove the configuration or deploy a new XTMv VM see Fireware Help Whenyour XTMv instance has been updated to v1111 or higher you can then use the usual upgrade procedure asdetailed in the next section
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
If your Firebox is a T10 XTM 25 or XTM 26 device with OS version 121 or older youmightnot be able to perform a backup before you upgrade the Firebox This occurs because thememory use by Fireware v121 or older does not leave enoughmemory free to successfullycomplete the upgrade process on these devices For these devices we recommend you savea copy of the xml configuration file with a distinctive name as described here Save theConfiguration File
If you need to downgrade a Firebox without a backup file after you complete the upgrade toFireware v12x we recommend you Downgrade withWebUI This process deletes theconfiguration file but does not remove the device feature keys and certificates After youdowngrade the Firebox you can use Policy Manager to Save the Configuration File to theFireboxIf your Firebox has Fireware v1211 or later the Firebox will temporarily disable somesecurity services to free up enoughmemory to successfully perform a backup To learnmoresee Backup and Restore for XTM 25 XTM 26 and Firebox T10
Important Information about the upgrade process
l We recommend you use FirewareWebUI to upgrade to Fireware v12x You can also use PolicyManager if you prefer
l We strongly recommend that you save a local copy of your Firebox configuration and create a Fireboxbackup image before you upgrade
l If you useWatchGuard SystemManager (WSM) make sure yourWSM version is equal to or higherthan the version of Fireware OS installed on your Firebox and the version of WSM installed on yourManagement Server Also make sure to upgradeWSM before you upgrade the version of Fireware OSon your Firebox
Upgrade to Fireware v1213
14 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 15
If you want to upgrade a Firebox T10 XTM 2Series 33 330 or 5 Series device werecommend that you reboot your Firebox before you upgrade This clears your devicememoryand can prevent many problems commonly associated with upgrades in those devices
Back Up Your WatchGuard ServersIt is not usually necessary to uninstall your previous v11x or v12x server or client software when you upgradetoWSM v12x You can install the v12x server and client software on top of your existing installation toupgrade yourWatchGuard software components We do however strongly recommend that you back up yourWatchGuard Servers (for example yourWatchGuardManagement Server) to a safe location before youupgrade You will need these backup files if you ever want to downgrade
You cannot restore aWatchGuard Server backup file created withWatchGuard SystemManager v12x to to a v11x installation Make sure to retain your older server backup fileswhen you upgrade to v120 or later in case you want to downgrade in the future
To back up your Management Server configuration from the computer where you installed theManagementServer
1 FromWatchGuard Server Center select BackupRestore Management ServerThe WatchGuard Server Center BackupRestore Wizard starts
2 Click NextThe Select an action screen appears
3 Select Back up settings4 Click Next
The Specify a backup file screen appears5 Click Browse to select a location for the backup file Make sure you save the configuration file to a
location you can access later to restore the configuration6 Click Next
The WatchGuard Server Center BackupRestore Wizard is complete screen appears7 Click Finish to exit the wizard
Upgrade to Fireware v1213 fromWeb UIIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from theSystem gt Upgrade OS page If your Firebox is running v119x or earlier use thesesteps to upgrade
1 Before you begin save a local copy of your configuration file2 Go toSystem gt Backup Image or use the USB Backup feature to back up your current device image3 On your management computer launch the OS software file you downloaded from theWatchGuard
Software Downloads pageIf you use theWindows-based installer on a computer with aWindows 64-bit operating system thisinstallation extracts an upgrade file called [product series]_[product code]sysa-dl to the defaultlocation of CProgram Files(x86)Common FilesWatchGuardresourcesFirewareXTM1213[model]or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Connect to your Firebox with theWebUI and select System gt Upgrade OS5 Browse to the location of the [product series]_[product code]sysa-dl from Step 2 and click Upgrade
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v121 3installer twice (once to remove v1213 software and again to install v1213)
Upgrade to Fireware v1213
16 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 17
Upgrade to Fireware v1213 fromWSMPolicy Manager1 Before you begin save a local copy of your configuration file2 Select File gt Backup or use the USB Backup feature to back up your current device image3 On amanagement computer running aWindows 64-bit operating system launch the OS executable file
you downloaded from theWatchGuard Portal This installation extracts an upgrade file called [Firebox orxtm series]_[product code]sysa-dl to the default location of CProgram Files(x86)CommonfilesWatchGuardresourcesFirewareXTM1213[model] or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Install and openWatchGuard SystemManager v1213 Connect to your Firebox and launch PolicyManager
5 From Policy Manager select File gt Upgrade When prompted browse to and select the [productseries]_[product code]sysa-dl file from Step 2
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v1213installer twice (once to remove v1213 software and again to install v1213)
If you like tomake updates to your Firebox configuration from a saved configuration file makesure you open the configuration from the Firebox and save it to a new file after you upgradeThis is to make sure that you do not overwrite any configuration changes that weremade aspart of the upgrade
Other Upgrade IssuesThere is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Fireware v12x is not supported on XTM 5Series devices models 505 510 520 or 530
Before you upgrade to Fireware v12x your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is preventedIf you try to schedule anOS update of managed devices through aManagement Server theupgrade is also preventedIf you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x orv1110x before you upgrade to Fireware v12x or your Firebox will be reset to a default state
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
18 WatchGuard Technologies Inc
Update AP Devices
Release Notes 19
Update AP Devices
OnApril 12 2018 WatchGuard released AP firmware versions 12915 for the AP100 AP102and AP200 and 20010 for the AP300 to address security vulnerabilities We highlyrecommend you install these AP firmware updates For more detailed information on thesevulnerabilities see AP100AP102AP200 Chained Vulnerabilities In addition to addressingthese vulnerabilities the AP firmware updates disable the AP local web UI As these APmodels can only bemanaged with the Gateway Wireless Controller the AP local web UI is nolonger supported
Beginning with Fireware v11124 AP firmware is no longer bundled with Fireware OS All AP device firmwareis managed by the Gateway Wireless Controller on your Firebox TheGateway Wireless Controllerautomatically checks for new AP firmware updates and enables you to download the firmware directly fromWatchGuard servers
Important Upgrade StepsIf you have not previously upgraded to Fireware 1201 or higher and the latest AP firmware youmust performthese steps
1 Make sure all your APs are online You can check AP status from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager selecttheGateway Wireless Controller tab
2 Make sure you are not using insecure default AP passphrases such as wgwap orwatchguard Yourcurrent AP passphrasemust be secure and at least 8 characters in length You can change your APpassphrase inNetwork gt Gateway Wireless Controller gt Settings
If you do not have a secure passphrase correctly configured before the upgrade you will losethemanagement connection with your deployed APs If this occurs youmust physicallyreset the APs to factory default settings to be able tomanage the APs from GatewayWireless Controller
Depending on the version of Fireware you are upgrading from youmay need tomark APs as trusted after theupgrade to Fireware v1201 or higher You canmark APs as trusted from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager select theGateway Wireless Controller tab
AP Firmware UpgradeThe current AP firmware versions for each AP devicemodel are
AP Device Model Current Firmware Version
AP100 AP102 AP200 12915
AP300 20010
AP120 AP320 AP322 AP325AP420
850-646
Tomanage AP firmware and download the latest AP firmware to your Firebox
n From FirewareWebUI select Dashboard gt Gateway Wireless Controller From theSummary tabclick Manage Firmware
n From Firebox SystemManager select theGateway Wireless Controller tab then click ManageFirmware
Note that you cannot upgrade an AP120 AP320 AP322 or AP420 to 830-657 or higher unless your Firebox isrunning Fireware v11124 or higher If your Firebox does not run v11124 or higher you will not see an optionto upgrade to AP firmware v830-657 or higher
If you have enabled automatic AP device firmware updates in Gateway Wireless Controller your AP devicesare automatically updated betweenmidnight and 400am local time
Tomanually update firmware on your AP devices
1 On theAccess Points tab select one or more AP devices2 From theActions drop-down list click Upgrade3 Click Yes to confirm that you want to upgrade the AP device
Update AP Devices
20 WatchGuard Technologies Inc
Upgrade your FireCluster to Fireware v1213
Release Notes 21
Upgrade your FireCluster to Fireware v1213You can upgrade Fireware OS for a FireCluster from Policy Manager or FirewareWebUI To upgrade aFireCluster from Fireware v1110x or lower we recommend you use Policy Manager
As part of the upgrade process each cluster member reboots and rejoins the cluster Because the clustercannot do load balancing while a cluster member reboot is in progress we recommend you upgrade anactiveactive cluster at a time when the network traffic is lightest
For information on how to upgrade your FireCluster see this Help topic
There is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Before you upgrade to Fireware v1111 or higher your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is prevented
If you try to schedule anOS update of managed devices through aManagement Server theupgrade is also prevented
If you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x before youupgrade to Fireware v1111x or higher or your Firebox will be reset to a default state
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
If you havehellip Select from these Fireware OS packages
Firebox M5600 Firebox_OS_M4600_M5600_12_1_3exefirebox_M4600_M5600_12_1_3zip
Firebox M4600 Firebox_OS_M4600_M5600_12_1_3exefirebox_M4600_M5600_12_1_3zip
Firebox M670 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M570 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M500 Firebox_OS_M400_M500_12_1_3exefirebox_M400_M500_12_1_3zip
Firebox M470 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M440 Firebox_OS_M440_12_1_3exefirebox_M440_12_1_3zip
Firebox M400 Firebox_OS_M400_M500_12_1_3exefirebox_M400_M500_12_1_3zip
Firebox M370 Firebox_OS_M370_M470_M570_M670_12_1_3exefirebox_M370_M470_M570_M670_12_1_3zip
Firebox M300 Firebox_OS_M200_M300_12_1_3exefirebox_M200_M300_12_1_3zip
Firebox M200 Firebox_OS_M200_M300_12_1_3exefirebox_M200_M300_12_1_3zip
Firebox T70 Firebox_OS_T70_12_1_3exefirebox_T70_12_1_3zip
Firebox T55 Firebox_OS_T55_12_1_3exefirebox_T55_12_1_3zip
Firebox T50 Firebox_OS_T30_T50_12_1_3exefirebox_T30_T50_12_1_3zip
Firebox T35 Firebox_OS_T35_12_1_3exefirebox_T35_12_1_3zip
Firebox T30 Firebox_OS_T30_T50_12_1_3exefirebox_T30_T50_12_1_3zip
Firebox T15 Firebox_OS_T15_12_1_3exefirebox_T15_12_1_3zip
Firebox T10 Firebox_OS_T10_12_1_3exefirebox_T10_12_1_3zip
Downloading Software
10 WatchGuard Technologies Inc
Downloading Software
Release Notes 11
If you havehellip Select from these Fireware OS packages
FireboxVAll editions for VMware
FireboxV_12_1_3ovaXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
FireboxVAll editions for Hyper-V
FireboxV_12_1_3_vhdzipXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
Firebox Cloud FireboxCloud_12_1_3zip
XTM 2500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 2050 XTM_OS_XTM2050_12_1_3exextm_xtm2050_12_1_3zip
XTM 1500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 1050 XTM_OS_XTM1050_12_1_3exextm_xtm1050_12_1_3zip
XTM 800 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 8Series XTM_OS_XTM8_12_1_3exextm_xtm8_12_1_3zip
XTM 5Series Models515 525 535 and 545only
XTM_OS_XTM5_12_1_3exextm_xtm5_12_1_3zip
XTM 330 XTM_OS_XTM330_12_1_3exextm_xtm330_12_1_3zip
XTM 33 XTM_OS_XTM3_12_1_3exextm_xtm3_12_1_3zip
XTM 2526 XTM_OS_XTM2A6_12_1_3exextm_xtm2a6_12_1_3zip
XTMvAll editions for VMware
xtmv_12_1_3ovaXTM_OS_xtmv_12_1_3exextm_xtmv_12_1_3zip
XTMvAll editions for Hyper-V
xtmv_12_1_3_vhdzipXTM_OS_XTMv_12_1_3exextm_xtmv_12_1_3zip
Single Sign-On SoftwareThese files are available for Single Sign-On There are no updates with the v1213 release
l WG-Authentication-Gateway_12_0exe (SSOAgent software - required for Single Sign-On andincludes optional Event LogMonitor for clientless SSO)
l WG-Authentication-Client_11122msi (SSOClient software forWindows)l WG-SSOCLIENT-MAC_12_0dmg (SSOClient software for Mac OS X)l SSOExchangeMonitor_x86_12_0exe (ExchangeMonitor for 32-bit operating systems)l SSOExchangeMonitor_x64_12_0exe (ExchangeMonitor for 64-bit operating systems)
For information about how to install and set up Single Sign-On see the product documentation
Terminal Services Authentication SoftwareThis file is not updated with the Fireware v1213 release
l TO_AGENT_SETUP_11_12exe (This installer includes both 32-bit and 64-bit file support)
Mobile VPN with SSL Client for Windows and MacThere are two files available for download if you useMobile VPN with SSL
l WG-MVPN-SSL_12_0exe (Client software forWindows)l WG-MVPN-SSL_12_0dmg (Client software for Mac)
Mobile VPN with IPSec client for Windows and MacThere are several available files to download
Shrew Soft Client
l Shrew Soft Client 222 for Windows - No client license required
WatchGuard IPSec Mobile VPN Clients
The current WatchGuard IPSec Mobile VPN Client forWindows version is 1213
l WatchGuard IPSec Mobile VPN Client for Windows (32-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
l WatchGuard IPSec Mobile VPN Client for Windows (64-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
The current macOS client version is 300
l WatchGuard IPSec Mobile VPN Client for macOS powered by NCP - There is a license requiredfor this premium client with a 30-day free trial available with download
WatchGuard Mobile VPN License Server
l WatchGuard Mobile VPN License Server (MVLS) v20 powered by NCP- Click here for moreinformation about MVLS If you have a VPN bundle ID for macOS it must be updated on the licenseserver to support the new macOS 300 client To update your bundle ID contact WatchGuard CustomerSupport Make sure to have your existing bundle ID available to expedite the update
Downloading Software
12 WatchGuard Technologies Inc
Upgrade Notes
Release Notes 13
Upgrade Notes
SSLTLS Settings Precedence and InheritanceFour Firebox features use SSLTLS for secure communication and share the sameOpenVPN serverManagement Tunnel over SSL on hub devices BOVPN over TLS in Server mode Mobile VPN with SSL andthe Access Portal These features also share some settings When you enablemore than one of thesefeatures settings for some features have a higher precedence than settings for other features Shared settingsare not configurable for the features with lower precedence For more information see this topic in FirewareHelp
Modem Configurations Converted to External Interfaces with Failover EnabledIf your Firebox was configured for modem failover when you upgrade your Firebox to Fireware v121 or higherthemodem configuration is automatically converted to an external interface with modem failover enabled If allother external interfaces become unavailable traffic automatically fails over to themodem interface Modeminterfaces can also participate in multi-WAN on all devices except the Firebox T10 Firebox T15 and XTM 2Series devices that do not have the Pro upgrade
HTTPS Proxy Content Inspection with Fireware v121With Fireware 121 we updated the HTTPS proxy action to include a Content Inspection Exceptions list whichincludes domains for services such as Dropbox Skype andMicrosoft Office that are known to be incompatiblewith content inspection The HTTPS proxy does not perform content inspection for domains with enabledexceptions on the Content Inspection Exceptions list
When you upgrade your Firebox to Fireware v121 or higher the Content Inspection Exceptions list isautomatically enabled in all HTTPS proxy actions that have content inspection enabled After the upgrade werecommend that you review the Content Inspection Exceptions list in your configured HTTPS proxy actionsand disable the exception for any domain you do not want the HTTPS proxy to allow without content inspectionFor more information seeWhich applications are on the default exception list in an HTTPS proxy action in theKnowledge Base
Gateway AV Engine Upgrade with Fireware v120With Fireware v120 we updated the engine used by Gateway AV to a new engine from BitDefender As aresult any Firebox that upgrades from Fireware v11x version to v120 or later must download a new signatureset which can take 7-10minutes for the first update It can take an additional 5-7minutes to synchronize aFireCluster We recommend that you upgrade to Fireware v12x at a quiet time on your network After the initialupdate signature updates are incremental andmuch faster than in previous versions
While the new signature set is being downloaded network users could experience issues related to GatewayAV scan failures for several minutes after the update and inbound emails sent through the SMTP proxy couldbe locked
XTMv Upgrade NotesYou cannot upgrade an XTMv device to FireboxV For Fireware v1111 and higher the XTMv device is a 64-bitvirtual machine You cannot upgrade an XTMv device from Fireware v1110x or lower to Fireware v1111 orhigher Instead youmust use the OVA file to deploy a new 64-bit Fireware v1111x or v12x XTMv VM andthen use Policy Manager to move the existing configuration from the 32-bit XTMv VM to the 64-bit XTMv VMFor more information about how tomove the configuration or deploy a new XTMv VM see Fireware Help Whenyour XTMv instance has been updated to v1111 or higher you can then use the usual upgrade procedure asdetailed in the next section
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
If your Firebox is a T10 XTM 25 or XTM 26 device with OS version 121 or older youmightnot be able to perform a backup before you upgrade the Firebox This occurs because thememory use by Fireware v121 or older does not leave enoughmemory free to successfullycomplete the upgrade process on these devices For these devices we recommend you savea copy of the xml configuration file with a distinctive name as described here Save theConfiguration File
If you need to downgrade a Firebox without a backup file after you complete the upgrade toFireware v12x we recommend you Downgrade withWebUI This process deletes theconfiguration file but does not remove the device feature keys and certificates After youdowngrade the Firebox you can use Policy Manager to Save the Configuration File to theFireboxIf your Firebox has Fireware v1211 or later the Firebox will temporarily disable somesecurity services to free up enoughmemory to successfully perform a backup To learnmoresee Backup and Restore for XTM 25 XTM 26 and Firebox T10
Important Information about the upgrade process
l We recommend you use FirewareWebUI to upgrade to Fireware v12x You can also use PolicyManager if you prefer
l We strongly recommend that you save a local copy of your Firebox configuration and create a Fireboxbackup image before you upgrade
l If you useWatchGuard SystemManager (WSM) make sure yourWSM version is equal to or higherthan the version of Fireware OS installed on your Firebox and the version of WSM installed on yourManagement Server Also make sure to upgradeWSM before you upgrade the version of Fireware OSon your Firebox
Upgrade to Fireware v1213
14 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 15
If you want to upgrade a Firebox T10 XTM 2Series 33 330 or 5 Series device werecommend that you reboot your Firebox before you upgrade This clears your devicememoryand can prevent many problems commonly associated with upgrades in those devices
Back Up Your WatchGuard ServersIt is not usually necessary to uninstall your previous v11x or v12x server or client software when you upgradetoWSM v12x You can install the v12x server and client software on top of your existing installation toupgrade yourWatchGuard software components We do however strongly recommend that you back up yourWatchGuard Servers (for example yourWatchGuardManagement Server) to a safe location before youupgrade You will need these backup files if you ever want to downgrade
You cannot restore aWatchGuard Server backup file created withWatchGuard SystemManager v12x to to a v11x installation Make sure to retain your older server backup fileswhen you upgrade to v120 or later in case you want to downgrade in the future
To back up your Management Server configuration from the computer where you installed theManagementServer
1 FromWatchGuard Server Center select BackupRestore Management ServerThe WatchGuard Server Center BackupRestore Wizard starts
2 Click NextThe Select an action screen appears
3 Select Back up settings4 Click Next
The Specify a backup file screen appears5 Click Browse to select a location for the backup file Make sure you save the configuration file to a
location you can access later to restore the configuration6 Click Next
The WatchGuard Server Center BackupRestore Wizard is complete screen appears7 Click Finish to exit the wizard
Upgrade to Fireware v1213 fromWeb UIIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from theSystem gt Upgrade OS page If your Firebox is running v119x or earlier use thesesteps to upgrade
1 Before you begin save a local copy of your configuration file2 Go toSystem gt Backup Image or use the USB Backup feature to back up your current device image3 On your management computer launch the OS software file you downloaded from theWatchGuard
Software Downloads pageIf you use theWindows-based installer on a computer with aWindows 64-bit operating system thisinstallation extracts an upgrade file called [product series]_[product code]sysa-dl to the defaultlocation of CProgram Files(x86)Common FilesWatchGuardresourcesFirewareXTM1213[model]or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Connect to your Firebox with theWebUI and select System gt Upgrade OS5 Browse to the location of the [product series]_[product code]sysa-dl from Step 2 and click Upgrade
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v121 3installer twice (once to remove v1213 software and again to install v1213)
Upgrade to Fireware v1213
16 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 17
Upgrade to Fireware v1213 fromWSMPolicy Manager1 Before you begin save a local copy of your configuration file2 Select File gt Backup or use the USB Backup feature to back up your current device image3 On amanagement computer running aWindows 64-bit operating system launch the OS executable file
you downloaded from theWatchGuard Portal This installation extracts an upgrade file called [Firebox orxtm series]_[product code]sysa-dl to the default location of CProgram Files(x86)CommonfilesWatchGuardresourcesFirewareXTM1213[model] or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Install and openWatchGuard SystemManager v1213 Connect to your Firebox and launch PolicyManager
5 From Policy Manager select File gt Upgrade When prompted browse to and select the [productseries]_[product code]sysa-dl file from Step 2
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v1213installer twice (once to remove v1213 software and again to install v1213)
If you like tomake updates to your Firebox configuration from a saved configuration file makesure you open the configuration from the Firebox and save it to a new file after you upgradeThis is to make sure that you do not overwrite any configuration changes that weremade aspart of the upgrade
Other Upgrade IssuesThere is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Fireware v12x is not supported on XTM 5Series devices models 505 510 520 or 530
Before you upgrade to Fireware v12x your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is preventedIf you try to schedule anOS update of managed devices through aManagement Server theupgrade is also preventedIf you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x orv1110x before you upgrade to Fireware v12x or your Firebox will be reset to a default state
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
18 WatchGuard Technologies Inc
Update AP Devices
Release Notes 19
Update AP Devices
OnApril 12 2018 WatchGuard released AP firmware versions 12915 for the AP100 AP102and AP200 and 20010 for the AP300 to address security vulnerabilities We highlyrecommend you install these AP firmware updates For more detailed information on thesevulnerabilities see AP100AP102AP200 Chained Vulnerabilities In addition to addressingthese vulnerabilities the AP firmware updates disable the AP local web UI As these APmodels can only bemanaged with the Gateway Wireless Controller the AP local web UI is nolonger supported
Beginning with Fireware v11124 AP firmware is no longer bundled with Fireware OS All AP device firmwareis managed by the Gateway Wireless Controller on your Firebox TheGateway Wireless Controllerautomatically checks for new AP firmware updates and enables you to download the firmware directly fromWatchGuard servers
Important Upgrade StepsIf you have not previously upgraded to Fireware 1201 or higher and the latest AP firmware youmust performthese steps
1 Make sure all your APs are online You can check AP status from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager selecttheGateway Wireless Controller tab
2 Make sure you are not using insecure default AP passphrases such as wgwap orwatchguard Yourcurrent AP passphrasemust be secure and at least 8 characters in length You can change your APpassphrase inNetwork gt Gateway Wireless Controller gt Settings
If you do not have a secure passphrase correctly configured before the upgrade you will losethemanagement connection with your deployed APs If this occurs youmust physicallyreset the APs to factory default settings to be able tomanage the APs from GatewayWireless Controller
Depending on the version of Fireware you are upgrading from youmay need tomark APs as trusted after theupgrade to Fireware v1201 or higher You canmark APs as trusted from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager select theGateway Wireless Controller tab
AP Firmware UpgradeThe current AP firmware versions for each AP devicemodel are
AP Device Model Current Firmware Version
AP100 AP102 AP200 12915
AP300 20010
AP120 AP320 AP322 AP325AP420
850-646
Tomanage AP firmware and download the latest AP firmware to your Firebox
n From FirewareWebUI select Dashboard gt Gateway Wireless Controller From theSummary tabclick Manage Firmware
n From Firebox SystemManager select theGateway Wireless Controller tab then click ManageFirmware
Note that you cannot upgrade an AP120 AP320 AP322 or AP420 to 830-657 or higher unless your Firebox isrunning Fireware v11124 or higher If your Firebox does not run v11124 or higher you will not see an optionto upgrade to AP firmware v830-657 or higher
If you have enabled automatic AP device firmware updates in Gateway Wireless Controller your AP devicesare automatically updated betweenmidnight and 400am local time
Tomanually update firmware on your AP devices
1 On theAccess Points tab select one or more AP devices2 From theActions drop-down list click Upgrade3 Click Yes to confirm that you want to upgrade the AP device
Update AP Devices
20 WatchGuard Technologies Inc
Upgrade your FireCluster to Fireware v1213
Release Notes 21
Upgrade your FireCluster to Fireware v1213You can upgrade Fireware OS for a FireCluster from Policy Manager or FirewareWebUI To upgrade aFireCluster from Fireware v1110x or lower we recommend you use Policy Manager
As part of the upgrade process each cluster member reboots and rejoins the cluster Because the clustercannot do load balancing while a cluster member reboot is in progress we recommend you upgrade anactiveactive cluster at a time when the network traffic is lightest
For information on how to upgrade your FireCluster see this Help topic
There is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Before you upgrade to Fireware v1111 or higher your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is prevented
If you try to schedule anOS update of managed devices through aManagement Server theupgrade is also prevented
If you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x before youupgrade to Fireware v1111x or higher or your Firebox will be reset to a default state
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
Downloading Software
Release Notes 11
If you havehellip Select from these Fireware OS packages
FireboxVAll editions for VMware
FireboxV_12_1_3ovaXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
FireboxVAll editions for Hyper-V
FireboxV_12_1_3_vhdzipXTM_OS_FireboxV_12_1_3exextm_FireboxV_12_1_3zip
Firebox Cloud FireboxCloud_12_1_3zip
XTM 2500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 2050 XTM_OS_XTM2050_12_1_3exextm_xtm2050_12_1_3zip
XTM 1500 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 1050 XTM_OS_XTM1050_12_1_3exextm_xtm1050_12_1_3zip
XTM 800 Series XTM_OS_XTM800_1500_2500_12_1_3exextm_xtm800_1500_2500_12_1_3zip
XTM 8Series XTM_OS_XTM8_12_1_3exextm_xtm8_12_1_3zip
XTM 5Series Models515 525 535 and 545only
XTM_OS_XTM5_12_1_3exextm_xtm5_12_1_3zip
XTM 330 XTM_OS_XTM330_12_1_3exextm_xtm330_12_1_3zip
XTM 33 XTM_OS_XTM3_12_1_3exextm_xtm3_12_1_3zip
XTM 2526 XTM_OS_XTM2A6_12_1_3exextm_xtm2a6_12_1_3zip
XTMvAll editions for VMware
xtmv_12_1_3ovaXTM_OS_xtmv_12_1_3exextm_xtmv_12_1_3zip
XTMvAll editions for Hyper-V
xtmv_12_1_3_vhdzipXTM_OS_XTMv_12_1_3exextm_xtmv_12_1_3zip
Single Sign-On SoftwareThese files are available for Single Sign-On There are no updates with the v1213 release
l WG-Authentication-Gateway_12_0exe (SSOAgent software - required for Single Sign-On andincludes optional Event LogMonitor for clientless SSO)
l WG-Authentication-Client_11122msi (SSOClient software forWindows)l WG-SSOCLIENT-MAC_12_0dmg (SSOClient software for Mac OS X)l SSOExchangeMonitor_x86_12_0exe (ExchangeMonitor for 32-bit operating systems)l SSOExchangeMonitor_x64_12_0exe (ExchangeMonitor for 64-bit operating systems)
For information about how to install and set up Single Sign-On see the product documentation
Terminal Services Authentication SoftwareThis file is not updated with the Fireware v1213 release
l TO_AGENT_SETUP_11_12exe (This installer includes both 32-bit and 64-bit file support)
Mobile VPN with SSL Client for Windows and MacThere are two files available for download if you useMobile VPN with SSL
l WG-MVPN-SSL_12_0exe (Client software forWindows)l WG-MVPN-SSL_12_0dmg (Client software for Mac)
Mobile VPN with IPSec client for Windows and MacThere are several available files to download
Shrew Soft Client
l Shrew Soft Client 222 for Windows - No client license required
WatchGuard IPSec Mobile VPN Clients
The current WatchGuard IPSec Mobile VPN Client forWindows version is 1213
l WatchGuard IPSec Mobile VPN Client for Windows (32-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
l WatchGuard IPSec Mobile VPN Client for Windows (64-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
The current macOS client version is 300
l WatchGuard IPSec Mobile VPN Client for macOS powered by NCP - There is a license requiredfor this premium client with a 30-day free trial available with download
WatchGuard Mobile VPN License Server
l WatchGuard Mobile VPN License Server (MVLS) v20 powered by NCP- Click here for moreinformation about MVLS If you have a VPN bundle ID for macOS it must be updated on the licenseserver to support the new macOS 300 client To update your bundle ID contact WatchGuard CustomerSupport Make sure to have your existing bundle ID available to expedite the update
Downloading Software
12 WatchGuard Technologies Inc
Upgrade Notes
Release Notes 13
Upgrade Notes
SSLTLS Settings Precedence and InheritanceFour Firebox features use SSLTLS for secure communication and share the sameOpenVPN serverManagement Tunnel over SSL on hub devices BOVPN over TLS in Server mode Mobile VPN with SSL andthe Access Portal These features also share some settings When you enablemore than one of thesefeatures settings for some features have a higher precedence than settings for other features Shared settingsare not configurable for the features with lower precedence For more information see this topic in FirewareHelp
Modem Configurations Converted to External Interfaces with Failover EnabledIf your Firebox was configured for modem failover when you upgrade your Firebox to Fireware v121 or higherthemodem configuration is automatically converted to an external interface with modem failover enabled If allother external interfaces become unavailable traffic automatically fails over to themodem interface Modeminterfaces can also participate in multi-WAN on all devices except the Firebox T10 Firebox T15 and XTM 2Series devices that do not have the Pro upgrade
HTTPS Proxy Content Inspection with Fireware v121With Fireware 121 we updated the HTTPS proxy action to include a Content Inspection Exceptions list whichincludes domains for services such as Dropbox Skype andMicrosoft Office that are known to be incompatiblewith content inspection The HTTPS proxy does not perform content inspection for domains with enabledexceptions on the Content Inspection Exceptions list
When you upgrade your Firebox to Fireware v121 or higher the Content Inspection Exceptions list isautomatically enabled in all HTTPS proxy actions that have content inspection enabled After the upgrade werecommend that you review the Content Inspection Exceptions list in your configured HTTPS proxy actionsand disable the exception for any domain you do not want the HTTPS proxy to allow without content inspectionFor more information seeWhich applications are on the default exception list in an HTTPS proxy action in theKnowledge Base
Gateway AV Engine Upgrade with Fireware v120With Fireware v120 we updated the engine used by Gateway AV to a new engine from BitDefender As aresult any Firebox that upgrades from Fireware v11x version to v120 or later must download a new signatureset which can take 7-10minutes for the first update It can take an additional 5-7minutes to synchronize aFireCluster We recommend that you upgrade to Fireware v12x at a quiet time on your network After the initialupdate signature updates are incremental andmuch faster than in previous versions
While the new signature set is being downloaded network users could experience issues related to GatewayAV scan failures for several minutes after the update and inbound emails sent through the SMTP proxy couldbe locked
XTMv Upgrade NotesYou cannot upgrade an XTMv device to FireboxV For Fireware v1111 and higher the XTMv device is a 64-bitvirtual machine You cannot upgrade an XTMv device from Fireware v1110x or lower to Fireware v1111 orhigher Instead youmust use the OVA file to deploy a new 64-bit Fireware v1111x or v12x XTMv VM andthen use Policy Manager to move the existing configuration from the 32-bit XTMv VM to the 64-bit XTMv VMFor more information about how tomove the configuration or deploy a new XTMv VM see Fireware Help Whenyour XTMv instance has been updated to v1111 or higher you can then use the usual upgrade procedure asdetailed in the next section
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
If your Firebox is a T10 XTM 25 or XTM 26 device with OS version 121 or older youmightnot be able to perform a backup before you upgrade the Firebox This occurs because thememory use by Fireware v121 or older does not leave enoughmemory free to successfullycomplete the upgrade process on these devices For these devices we recommend you savea copy of the xml configuration file with a distinctive name as described here Save theConfiguration File
If you need to downgrade a Firebox without a backup file after you complete the upgrade toFireware v12x we recommend you Downgrade withWebUI This process deletes theconfiguration file but does not remove the device feature keys and certificates After youdowngrade the Firebox you can use Policy Manager to Save the Configuration File to theFireboxIf your Firebox has Fireware v1211 or later the Firebox will temporarily disable somesecurity services to free up enoughmemory to successfully perform a backup To learnmoresee Backup and Restore for XTM 25 XTM 26 and Firebox T10
Important Information about the upgrade process
l We recommend you use FirewareWebUI to upgrade to Fireware v12x You can also use PolicyManager if you prefer
l We strongly recommend that you save a local copy of your Firebox configuration and create a Fireboxbackup image before you upgrade
l If you useWatchGuard SystemManager (WSM) make sure yourWSM version is equal to or higherthan the version of Fireware OS installed on your Firebox and the version of WSM installed on yourManagement Server Also make sure to upgradeWSM before you upgrade the version of Fireware OSon your Firebox
Upgrade to Fireware v1213
14 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 15
If you want to upgrade a Firebox T10 XTM 2Series 33 330 or 5 Series device werecommend that you reboot your Firebox before you upgrade This clears your devicememoryand can prevent many problems commonly associated with upgrades in those devices
Back Up Your WatchGuard ServersIt is not usually necessary to uninstall your previous v11x or v12x server or client software when you upgradetoWSM v12x You can install the v12x server and client software on top of your existing installation toupgrade yourWatchGuard software components We do however strongly recommend that you back up yourWatchGuard Servers (for example yourWatchGuardManagement Server) to a safe location before youupgrade You will need these backup files if you ever want to downgrade
You cannot restore aWatchGuard Server backup file created withWatchGuard SystemManager v12x to to a v11x installation Make sure to retain your older server backup fileswhen you upgrade to v120 or later in case you want to downgrade in the future
To back up your Management Server configuration from the computer where you installed theManagementServer
1 FromWatchGuard Server Center select BackupRestore Management ServerThe WatchGuard Server Center BackupRestore Wizard starts
2 Click NextThe Select an action screen appears
3 Select Back up settings4 Click Next
The Specify a backup file screen appears5 Click Browse to select a location for the backup file Make sure you save the configuration file to a
location you can access later to restore the configuration6 Click Next
The WatchGuard Server Center BackupRestore Wizard is complete screen appears7 Click Finish to exit the wizard
Upgrade to Fireware v1213 fromWeb UIIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from theSystem gt Upgrade OS page If your Firebox is running v119x or earlier use thesesteps to upgrade
1 Before you begin save a local copy of your configuration file2 Go toSystem gt Backup Image or use the USB Backup feature to back up your current device image3 On your management computer launch the OS software file you downloaded from theWatchGuard
Software Downloads pageIf you use theWindows-based installer on a computer with aWindows 64-bit operating system thisinstallation extracts an upgrade file called [product series]_[product code]sysa-dl to the defaultlocation of CProgram Files(x86)Common FilesWatchGuardresourcesFirewareXTM1213[model]or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Connect to your Firebox with theWebUI and select System gt Upgrade OS5 Browse to the location of the [product series]_[product code]sysa-dl from Step 2 and click Upgrade
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v121 3installer twice (once to remove v1213 software and again to install v1213)
Upgrade to Fireware v1213
16 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 17
Upgrade to Fireware v1213 fromWSMPolicy Manager1 Before you begin save a local copy of your configuration file2 Select File gt Backup or use the USB Backup feature to back up your current device image3 On amanagement computer running aWindows 64-bit operating system launch the OS executable file
you downloaded from theWatchGuard Portal This installation extracts an upgrade file called [Firebox orxtm series]_[product code]sysa-dl to the default location of CProgram Files(x86)CommonfilesWatchGuardresourcesFirewareXTM1213[model] or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Install and openWatchGuard SystemManager v1213 Connect to your Firebox and launch PolicyManager
5 From Policy Manager select File gt Upgrade When prompted browse to and select the [productseries]_[product code]sysa-dl file from Step 2
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v1213installer twice (once to remove v1213 software and again to install v1213)
If you like tomake updates to your Firebox configuration from a saved configuration file makesure you open the configuration from the Firebox and save it to a new file after you upgradeThis is to make sure that you do not overwrite any configuration changes that weremade aspart of the upgrade
Other Upgrade IssuesThere is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Fireware v12x is not supported on XTM 5Series devices models 505 510 520 or 530
Before you upgrade to Fireware v12x your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is preventedIf you try to schedule anOS update of managed devices through aManagement Server theupgrade is also preventedIf you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x orv1110x before you upgrade to Fireware v12x or your Firebox will be reset to a default state
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
18 WatchGuard Technologies Inc
Update AP Devices
Release Notes 19
Update AP Devices
OnApril 12 2018 WatchGuard released AP firmware versions 12915 for the AP100 AP102and AP200 and 20010 for the AP300 to address security vulnerabilities We highlyrecommend you install these AP firmware updates For more detailed information on thesevulnerabilities see AP100AP102AP200 Chained Vulnerabilities In addition to addressingthese vulnerabilities the AP firmware updates disable the AP local web UI As these APmodels can only bemanaged with the Gateway Wireless Controller the AP local web UI is nolonger supported
Beginning with Fireware v11124 AP firmware is no longer bundled with Fireware OS All AP device firmwareis managed by the Gateway Wireless Controller on your Firebox TheGateway Wireless Controllerautomatically checks for new AP firmware updates and enables you to download the firmware directly fromWatchGuard servers
Important Upgrade StepsIf you have not previously upgraded to Fireware 1201 or higher and the latest AP firmware youmust performthese steps
1 Make sure all your APs are online You can check AP status from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager selecttheGateway Wireless Controller tab
2 Make sure you are not using insecure default AP passphrases such as wgwap orwatchguard Yourcurrent AP passphrasemust be secure and at least 8 characters in length You can change your APpassphrase inNetwork gt Gateway Wireless Controller gt Settings
If you do not have a secure passphrase correctly configured before the upgrade you will losethemanagement connection with your deployed APs If this occurs youmust physicallyreset the APs to factory default settings to be able tomanage the APs from GatewayWireless Controller
Depending on the version of Fireware you are upgrading from youmay need tomark APs as trusted after theupgrade to Fireware v1201 or higher You canmark APs as trusted from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager select theGateway Wireless Controller tab
AP Firmware UpgradeThe current AP firmware versions for each AP devicemodel are
AP Device Model Current Firmware Version
AP100 AP102 AP200 12915
AP300 20010
AP120 AP320 AP322 AP325AP420
850-646
Tomanage AP firmware and download the latest AP firmware to your Firebox
n From FirewareWebUI select Dashboard gt Gateway Wireless Controller From theSummary tabclick Manage Firmware
n From Firebox SystemManager select theGateway Wireless Controller tab then click ManageFirmware
Note that you cannot upgrade an AP120 AP320 AP322 or AP420 to 830-657 or higher unless your Firebox isrunning Fireware v11124 or higher If your Firebox does not run v11124 or higher you will not see an optionto upgrade to AP firmware v830-657 or higher
If you have enabled automatic AP device firmware updates in Gateway Wireless Controller your AP devicesare automatically updated betweenmidnight and 400am local time
Tomanually update firmware on your AP devices
1 On theAccess Points tab select one or more AP devices2 From theActions drop-down list click Upgrade3 Click Yes to confirm that you want to upgrade the AP device
Update AP Devices
20 WatchGuard Technologies Inc
Upgrade your FireCluster to Fireware v1213
Release Notes 21
Upgrade your FireCluster to Fireware v1213You can upgrade Fireware OS for a FireCluster from Policy Manager or FirewareWebUI To upgrade aFireCluster from Fireware v1110x or lower we recommend you use Policy Manager
As part of the upgrade process each cluster member reboots and rejoins the cluster Because the clustercannot do load balancing while a cluster member reboot is in progress we recommend you upgrade anactiveactive cluster at a time when the network traffic is lightest
For information on how to upgrade your FireCluster see this Help topic
There is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Before you upgrade to Fireware v1111 or higher your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is prevented
If you try to schedule anOS update of managed devices through aManagement Server theupgrade is also prevented
If you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x before youupgrade to Fireware v1111x or higher or your Firebox will be reset to a default state
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
Single Sign-On SoftwareThese files are available for Single Sign-On There are no updates with the v1213 release
l WG-Authentication-Gateway_12_0exe (SSOAgent software - required for Single Sign-On andincludes optional Event LogMonitor for clientless SSO)
l WG-Authentication-Client_11122msi (SSOClient software forWindows)l WG-SSOCLIENT-MAC_12_0dmg (SSOClient software for Mac OS X)l SSOExchangeMonitor_x86_12_0exe (ExchangeMonitor for 32-bit operating systems)l SSOExchangeMonitor_x64_12_0exe (ExchangeMonitor for 64-bit operating systems)
For information about how to install and set up Single Sign-On see the product documentation
Terminal Services Authentication SoftwareThis file is not updated with the Fireware v1213 release
l TO_AGENT_SETUP_11_12exe (This installer includes both 32-bit and 64-bit file support)
Mobile VPN with SSL Client for Windows and MacThere are two files available for download if you useMobile VPN with SSL
l WG-MVPN-SSL_12_0exe (Client software forWindows)l WG-MVPN-SSL_12_0dmg (Client software for Mac)
Mobile VPN with IPSec client for Windows and MacThere are several available files to download
Shrew Soft Client
l Shrew Soft Client 222 for Windows - No client license required
WatchGuard IPSec Mobile VPN Clients
The current WatchGuard IPSec Mobile VPN Client forWindows version is 1213
l WatchGuard IPSec Mobile VPN Client for Windows (32-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
l WatchGuard IPSec Mobile VPN Client for Windows (64-bit) powered by NCP - There is alicense required for this premium client with a 30-day free trial available with download
The current macOS client version is 300
l WatchGuard IPSec Mobile VPN Client for macOS powered by NCP - There is a license requiredfor this premium client with a 30-day free trial available with download
WatchGuard Mobile VPN License Server
l WatchGuard Mobile VPN License Server (MVLS) v20 powered by NCP- Click here for moreinformation about MVLS If you have a VPN bundle ID for macOS it must be updated on the licenseserver to support the new macOS 300 client To update your bundle ID contact WatchGuard CustomerSupport Make sure to have your existing bundle ID available to expedite the update
Downloading Software
12 WatchGuard Technologies Inc
Upgrade Notes
Release Notes 13
Upgrade Notes
SSLTLS Settings Precedence and InheritanceFour Firebox features use SSLTLS for secure communication and share the sameOpenVPN serverManagement Tunnel over SSL on hub devices BOVPN over TLS in Server mode Mobile VPN with SSL andthe Access Portal These features also share some settings When you enablemore than one of thesefeatures settings for some features have a higher precedence than settings for other features Shared settingsare not configurable for the features with lower precedence For more information see this topic in FirewareHelp
Modem Configurations Converted to External Interfaces with Failover EnabledIf your Firebox was configured for modem failover when you upgrade your Firebox to Fireware v121 or higherthemodem configuration is automatically converted to an external interface with modem failover enabled If allother external interfaces become unavailable traffic automatically fails over to themodem interface Modeminterfaces can also participate in multi-WAN on all devices except the Firebox T10 Firebox T15 and XTM 2Series devices that do not have the Pro upgrade
HTTPS Proxy Content Inspection with Fireware v121With Fireware 121 we updated the HTTPS proxy action to include a Content Inspection Exceptions list whichincludes domains for services such as Dropbox Skype andMicrosoft Office that are known to be incompatiblewith content inspection The HTTPS proxy does not perform content inspection for domains with enabledexceptions on the Content Inspection Exceptions list
When you upgrade your Firebox to Fireware v121 or higher the Content Inspection Exceptions list isautomatically enabled in all HTTPS proxy actions that have content inspection enabled After the upgrade werecommend that you review the Content Inspection Exceptions list in your configured HTTPS proxy actionsand disable the exception for any domain you do not want the HTTPS proxy to allow without content inspectionFor more information seeWhich applications are on the default exception list in an HTTPS proxy action in theKnowledge Base
Gateway AV Engine Upgrade with Fireware v120With Fireware v120 we updated the engine used by Gateway AV to a new engine from BitDefender As aresult any Firebox that upgrades from Fireware v11x version to v120 or later must download a new signatureset which can take 7-10minutes for the first update It can take an additional 5-7minutes to synchronize aFireCluster We recommend that you upgrade to Fireware v12x at a quiet time on your network After the initialupdate signature updates are incremental andmuch faster than in previous versions
While the new signature set is being downloaded network users could experience issues related to GatewayAV scan failures for several minutes after the update and inbound emails sent through the SMTP proxy couldbe locked
XTMv Upgrade NotesYou cannot upgrade an XTMv device to FireboxV For Fireware v1111 and higher the XTMv device is a 64-bitvirtual machine You cannot upgrade an XTMv device from Fireware v1110x or lower to Fireware v1111 orhigher Instead youmust use the OVA file to deploy a new 64-bit Fireware v1111x or v12x XTMv VM andthen use Policy Manager to move the existing configuration from the 32-bit XTMv VM to the 64-bit XTMv VMFor more information about how tomove the configuration or deploy a new XTMv VM see Fireware Help Whenyour XTMv instance has been updated to v1111 or higher you can then use the usual upgrade procedure asdetailed in the next section
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
If your Firebox is a T10 XTM 25 or XTM 26 device with OS version 121 or older youmightnot be able to perform a backup before you upgrade the Firebox This occurs because thememory use by Fireware v121 or older does not leave enoughmemory free to successfullycomplete the upgrade process on these devices For these devices we recommend you savea copy of the xml configuration file with a distinctive name as described here Save theConfiguration File
If you need to downgrade a Firebox without a backup file after you complete the upgrade toFireware v12x we recommend you Downgrade withWebUI This process deletes theconfiguration file but does not remove the device feature keys and certificates After youdowngrade the Firebox you can use Policy Manager to Save the Configuration File to theFireboxIf your Firebox has Fireware v1211 or later the Firebox will temporarily disable somesecurity services to free up enoughmemory to successfully perform a backup To learnmoresee Backup and Restore for XTM 25 XTM 26 and Firebox T10
Important Information about the upgrade process
l We recommend you use FirewareWebUI to upgrade to Fireware v12x You can also use PolicyManager if you prefer
l We strongly recommend that you save a local copy of your Firebox configuration and create a Fireboxbackup image before you upgrade
l If you useWatchGuard SystemManager (WSM) make sure yourWSM version is equal to or higherthan the version of Fireware OS installed on your Firebox and the version of WSM installed on yourManagement Server Also make sure to upgradeWSM before you upgrade the version of Fireware OSon your Firebox
Upgrade to Fireware v1213
14 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 15
If you want to upgrade a Firebox T10 XTM 2Series 33 330 or 5 Series device werecommend that you reboot your Firebox before you upgrade This clears your devicememoryand can prevent many problems commonly associated with upgrades in those devices
Back Up Your WatchGuard ServersIt is not usually necessary to uninstall your previous v11x or v12x server or client software when you upgradetoWSM v12x You can install the v12x server and client software on top of your existing installation toupgrade yourWatchGuard software components We do however strongly recommend that you back up yourWatchGuard Servers (for example yourWatchGuardManagement Server) to a safe location before youupgrade You will need these backup files if you ever want to downgrade
You cannot restore aWatchGuard Server backup file created withWatchGuard SystemManager v12x to to a v11x installation Make sure to retain your older server backup fileswhen you upgrade to v120 or later in case you want to downgrade in the future
To back up your Management Server configuration from the computer where you installed theManagementServer
1 FromWatchGuard Server Center select BackupRestore Management ServerThe WatchGuard Server Center BackupRestore Wizard starts
2 Click NextThe Select an action screen appears
3 Select Back up settings4 Click Next
The Specify a backup file screen appears5 Click Browse to select a location for the backup file Make sure you save the configuration file to a
location you can access later to restore the configuration6 Click Next
The WatchGuard Server Center BackupRestore Wizard is complete screen appears7 Click Finish to exit the wizard
Upgrade to Fireware v1213 fromWeb UIIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from theSystem gt Upgrade OS page If your Firebox is running v119x or earlier use thesesteps to upgrade
1 Before you begin save a local copy of your configuration file2 Go toSystem gt Backup Image or use the USB Backup feature to back up your current device image3 On your management computer launch the OS software file you downloaded from theWatchGuard
Software Downloads pageIf you use theWindows-based installer on a computer with aWindows 64-bit operating system thisinstallation extracts an upgrade file called [product series]_[product code]sysa-dl to the defaultlocation of CProgram Files(x86)Common FilesWatchGuardresourcesFirewareXTM1213[model]or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Connect to your Firebox with theWebUI and select System gt Upgrade OS5 Browse to the location of the [product series]_[product code]sysa-dl from Step 2 and click Upgrade
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v121 3installer twice (once to remove v1213 software and again to install v1213)
Upgrade to Fireware v1213
16 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 17
Upgrade to Fireware v1213 fromWSMPolicy Manager1 Before you begin save a local copy of your configuration file2 Select File gt Backup or use the USB Backup feature to back up your current device image3 On amanagement computer running aWindows 64-bit operating system launch the OS executable file
you downloaded from theWatchGuard Portal This installation extracts an upgrade file called [Firebox orxtm series]_[product code]sysa-dl to the default location of CProgram Files(x86)CommonfilesWatchGuardresourcesFirewareXTM1213[model] or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Install and openWatchGuard SystemManager v1213 Connect to your Firebox and launch PolicyManager
5 From Policy Manager select File gt Upgrade When prompted browse to and select the [productseries]_[product code]sysa-dl file from Step 2
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v1213installer twice (once to remove v1213 software and again to install v1213)
If you like tomake updates to your Firebox configuration from a saved configuration file makesure you open the configuration from the Firebox and save it to a new file after you upgradeThis is to make sure that you do not overwrite any configuration changes that weremade aspart of the upgrade
Other Upgrade IssuesThere is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Fireware v12x is not supported on XTM 5Series devices models 505 510 520 or 530
Before you upgrade to Fireware v12x your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is preventedIf you try to schedule anOS update of managed devices through aManagement Server theupgrade is also preventedIf you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x orv1110x before you upgrade to Fireware v12x or your Firebox will be reset to a default state
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
18 WatchGuard Technologies Inc
Update AP Devices
Release Notes 19
Update AP Devices
OnApril 12 2018 WatchGuard released AP firmware versions 12915 for the AP100 AP102and AP200 and 20010 for the AP300 to address security vulnerabilities We highlyrecommend you install these AP firmware updates For more detailed information on thesevulnerabilities see AP100AP102AP200 Chained Vulnerabilities In addition to addressingthese vulnerabilities the AP firmware updates disable the AP local web UI As these APmodels can only bemanaged with the Gateway Wireless Controller the AP local web UI is nolonger supported
Beginning with Fireware v11124 AP firmware is no longer bundled with Fireware OS All AP device firmwareis managed by the Gateway Wireless Controller on your Firebox TheGateway Wireless Controllerautomatically checks for new AP firmware updates and enables you to download the firmware directly fromWatchGuard servers
Important Upgrade StepsIf you have not previously upgraded to Fireware 1201 or higher and the latest AP firmware youmust performthese steps
1 Make sure all your APs are online You can check AP status from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager selecttheGateway Wireless Controller tab
2 Make sure you are not using insecure default AP passphrases such as wgwap orwatchguard Yourcurrent AP passphrasemust be secure and at least 8 characters in length You can change your APpassphrase inNetwork gt Gateway Wireless Controller gt Settings
If you do not have a secure passphrase correctly configured before the upgrade you will losethemanagement connection with your deployed APs If this occurs youmust physicallyreset the APs to factory default settings to be able tomanage the APs from GatewayWireless Controller
Depending on the version of Fireware you are upgrading from youmay need tomark APs as trusted after theupgrade to Fireware v1201 or higher You canmark APs as trusted from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager select theGateway Wireless Controller tab
AP Firmware UpgradeThe current AP firmware versions for each AP devicemodel are
AP Device Model Current Firmware Version
AP100 AP102 AP200 12915
AP300 20010
AP120 AP320 AP322 AP325AP420
850-646
Tomanage AP firmware and download the latest AP firmware to your Firebox
n From FirewareWebUI select Dashboard gt Gateway Wireless Controller From theSummary tabclick Manage Firmware
n From Firebox SystemManager select theGateway Wireless Controller tab then click ManageFirmware
Note that you cannot upgrade an AP120 AP320 AP322 or AP420 to 830-657 or higher unless your Firebox isrunning Fireware v11124 or higher If your Firebox does not run v11124 or higher you will not see an optionto upgrade to AP firmware v830-657 or higher
If you have enabled automatic AP device firmware updates in Gateway Wireless Controller your AP devicesare automatically updated betweenmidnight and 400am local time
Tomanually update firmware on your AP devices
1 On theAccess Points tab select one or more AP devices2 From theActions drop-down list click Upgrade3 Click Yes to confirm that you want to upgrade the AP device
Update AP Devices
20 WatchGuard Technologies Inc
Upgrade your FireCluster to Fireware v1213
Release Notes 21
Upgrade your FireCluster to Fireware v1213You can upgrade Fireware OS for a FireCluster from Policy Manager or FirewareWebUI To upgrade aFireCluster from Fireware v1110x or lower we recommend you use Policy Manager
As part of the upgrade process each cluster member reboots and rejoins the cluster Because the clustercannot do load balancing while a cluster member reboot is in progress we recommend you upgrade anactiveactive cluster at a time when the network traffic is lightest
For information on how to upgrade your FireCluster see this Help topic
There is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Before you upgrade to Fireware v1111 or higher your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is prevented
If you try to schedule anOS update of managed devices through aManagement Server theupgrade is also prevented
If you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x before youupgrade to Fireware v1111x or higher or your Firebox will be reset to a default state
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
Upgrade Notes
Release Notes 13
Upgrade Notes
SSLTLS Settings Precedence and InheritanceFour Firebox features use SSLTLS for secure communication and share the sameOpenVPN serverManagement Tunnel over SSL on hub devices BOVPN over TLS in Server mode Mobile VPN with SSL andthe Access Portal These features also share some settings When you enablemore than one of thesefeatures settings for some features have a higher precedence than settings for other features Shared settingsare not configurable for the features with lower precedence For more information see this topic in FirewareHelp
Modem Configurations Converted to External Interfaces with Failover EnabledIf your Firebox was configured for modem failover when you upgrade your Firebox to Fireware v121 or higherthemodem configuration is automatically converted to an external interface with modem failover enabled If allother external interfaces become unavailable traffic automatically fails over to themodem interface Modeminterfaces can also participate in multi-WAN on all devices except the Firebox T10 Firebox T15 and XTM 2Series devices that do not have the Pro upgrade
HTTPS Proxy Content Inspection with Fireware v121With Fireware 121 we updated the HTTPS proxy action to include a Content Inspection Exceptions list whichincludes domains for services such as Dropbox Skype andMicrosoft Office that are known to be incompatiblewith content inspection The HTTPS proxy does not perform content inspection for domains with enabledexceptions on the Content Inspection Exceptions list
When you upgrade your Firebox to Fireware v121 or higher the Content Inspection Exceptions list isautomatically enabled in all HTTPS proxy actions that have content inspection enabled After the upgrade werecommend that you review the Content Inspection Exceptions list in your configured HTTPS proxy actionsand disable the exception for any domain you do not want the HTTPS proxy to allow without content inspectionFor more information seeWhich applications are on the default exception list in an HTTPS proxy action in theKnowledge Base
Gateway AV Engine Upgrade with Fireware v120With Fireware v120 we updated the engine used by Gateway AV to a new engine from BitDefender As aresult any Firebox that upgrades from Fireware v11x version to v120 or later must download a new signatureset which can take 7-10minutes for the first update It can take an additional 5-7minutes to synchronize aFireCluster We recommend that you upgrade to Fireware v12x at a quiet time on your network After the initialupdate signature updates are incremental andmuch faster than in previous versions
While the new signature set is being downloaded network users could experience issues related to GatewayAV scan failures for several minutes after the update and inbound emails sent through the SMTP proxy couldbe locked
XTMv Upgrade NotesYou cannot upgrade an XTMv device to FireboxV For Fireware v1111 and higher the XTMv device is a 64-bitvirtual machine You cannot upgrade an XTMv device from Fireware v1110x or lower to Fireware v1111 orhigher Instead youmust use the OVA file to deploy a new 64-bit Fireware v1111x or v12x XTMv VM andthen use Policy Manager to move the existing configuration from the 32-bit XTMv VM to the 64-bit XTMv VMFor more information about how tomove the configuration or deploy a new XTMv VM see Fireware Help Whenyour XTMv instance has been updated to v1111 or higher you can then use the usual upgrade procedure asdetailed in the next section
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
If your Firebox is a T10 XTM 25 or XTM 26 device with OS version 121 or older youmightnot be able to perform a backup before you upgrade the Firebox This occurs because thememory use by Fireware v121 or older does not leave enoughmemory free to successfullycomplete the upgrade process on these devices For these devices we recommend you savea copy of the xml configuration file with a distinctive name as described here Save theConfiguration File
If you need to downgrade a Firebox without a backup file after you complete the upgrade toFireware v12x we recommend you Downgrade withWebUI This process deletes theconfiguration file but does not remove the device feature keys and certificates After youdowngrade the Firebox you can use Policy Manager to Save the Configuration File to theFireboxIf your Firebox has Fireware v1211 or later the Firebox will temporarily disable somesecurity services to free up enoughmemory to successfully perform a backup To learnmoresee Backup and Restore for XTM 25 XTM 26 and Firebox T10
Important Information about the upgrade process
l We recommend you use FirewareWebUI to upgrade to Fireware v12x You can also use PolicyManager if you prefer
l We strongly recommend that you save a local copy of your Firebox configuration and create a Fireboxbackup image before you upgrade
l If you useWatchGuard SystemManager (WSM) make sure yourWSM version is equal to or higherthan the version of Fireware OS installed on your Firebox and the version of WSM installed on yourManagement Server Also make sure to upgradeWSM before you upgrade the version of Fireware OSon your Firebox
Upgrade to Fireware v1213
14 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 15
If you want to upgrade a Firebox T10 XTM 2Series 33 330 or 5 Series device werecommend that you reboot your Firebox before you upgrade This clears your devicememoryand can prevent many problems commonly associated with upgrades in those devices
Back Up Your WatchGuard ServersIt is not usually necessary to uninstall your previous v11x or v12x server or client software when you upgradetoWSM v12x You can install the v12x server and client software on top of your existing installation toupgrade yourWatchGuard software components We do however strongly recommend that you back up yourWatchGuard Servers (for example yourWatchGuardManagement Server) to a safe location before youupgrade You will need these backup files if you ever want to downgrade
You cannot restore aWatchGuard Server backup file created withWatchGuard SystemManager v12x to to a v11x installation Make sure to retain your older server backup fileswhen you upgrade to v120 or later in case you want to downgrade in the future
To back up your Management Server configuration from the computer where you installed theManagementServer
1 FromWatchGuard Server Center select BackupRestore Management ServerThe WatchGuard Server Center BackupRestore Wizard starts
2 Click NextThe Select an action screen appears
3 Select Back up settings4 Click Next
The Specify a backup file screen appears5 Click Browse to select a location for the backup file Make sure you save the configuration file to a
location you can access later to restore the configuration6 Click Next
The WatchGuard Server Center BackupRestore Wizard is complete screen appears7 Click Finish to exit the wizard
Upgrade to Fireware v1213 fromWeb UIIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from theSystem gt Upgrade OS page If your Firebox is running v119x or earlier use thesesteps to upgrade
1 Before you begin save a local copy of your configuration file2 Go toSystem gt Backup Image or use the USB Backup feature to back up your current device image3 On your management computer launch the OS software file you downloaded from theWatchGuard
Software Downloads pageIf you use theWindows-based installer on a computer with aWindows 64-bit operating system thisinstallation extracts an upgrade file called [product series]_[product code]sysa-dl to the defaultlocation of CProgram Files(x86)Common FilesWatchGuardresourcesFirewareXTM1213[model]or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Connect to your Firebox with theWebUI and select System gt Upgrade OS5 Browse to the location of the [product series]_[product code]sysa-dl from Step 2 and click Upgrade
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v121 3installer twice (once to remove v1213 software and again to install v1213)
Upgrade to Fireware v1213
16 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 17
Upgrade to Fireware v1213 fromWSMPolicy Manager1 Before you begin save a local copy of your configuration file2 Select File gt Backup or use the USB Backup feature to back up your current device image3 On amanagement computer running aWindows 64-bit operating system launch the OS executable file
you downloaded from theWatchGuard Portal This installation extracts an upgrade file called [Firebox orxtm series]_[product code]sysa-dl to the default location of CProgram Files(x86)CommonfilesWatchGuardresourcesFirewareXTM1213[model] or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Install and openWatchGuard SystemManager v1213 Connect to your Firebox and launch PolicyManager
5 From Policy Manager select File gt Upgrade When prompted browse to and select the [productseries]_[product code]sysa-dl file from Step 2
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v1213installer twice (once to remove v1213 software and again to install v1213)
If you like tomake updates to your Firebox configuration from a saved configuration file makesure you open the configuration from the Firebox and save it to a new file after you upgradeThis is to make sure that you do not overwrite any configuration changes that weremade aspart of the upgrade
Other Upgrade IssuesThere is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Fireware v12x is not supported on XTM 5Series devices models 505 510 520 or 530
Before you upgrade to Fireware v12x your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is preventedIf you try to schedule anOS update of managed devices through aManagement Server theupgrade is also preventedIf you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x orv1110x before you upgrade to Fireware v12x or your Firebox will be reset to a default state
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
18 WatchGuard Technologies Inc
Update AP Devices
Release Notes 19
Update AP Devices
OnApril 12 2018 WatchGuard released AP firmware versions 12915 for the AP100 AP102and AP200 and 20010 for the AP300 to address security vulnerabilities We highlyrecommend you install these AP firmware updates For more detailed information on thesevulnerabilities see AP100AP102AP200 Chained Vulnerabilities In addition to addressingthese vulnerabilities the AP firmware updates disable the AP local web UI As these APmodels can only bemanaged with the Gateway Wireless Controller the AP local web UI is nolonger supported
Beginning with Fireware v11124 AP firmware is no longer bundled with Fireware OS All AP device firmwareis managed by the Gateway Wireless Controller on your Firebox TheGateway Wireless Controllerautomatically checks for new AP firmware updates and enables you to download the firmware directly fromWatchGuard servers
Important Upgrade StepsIf you have not previously upgraded to Fireware 1201 or higher and the latest AP firmware youmust performthese steps
1 Make sure all your APs are online You can check AP status from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager selecttheGateway Wireless Controller tab
2 Make sure you are not using insecure default AP passphrases such as wgwap orwatchguard Yourcurrent AP passphrasemust be secure and at least 8 characters in length You can change your APpassphrase inNetwork gt Gateway Wireless Controller gt Settings
If you do not have a secure passphrase correctly configured before the upgrade you will losethemanagement connection with your deployed APs If this occurs youmust physicallyreset the APs to factory default settings to be able tomanage the APs from GatewayWireless Controller
Depending on the version of Fireware you are upgrading from youmay need tomark APs as trusted after theupgrade to Fireware v1201 or higher You canmark APs as trusted from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager select theGateway Wireless Controller tab
AP Firmware UpgradeThe current AP firmware versions for each AP devicemodel are
AP Device Model Current Firmware Version
AP100 AP102 AP200 12915
AP300 20010
AP120 AP320 AP322 AP325AP420
850-646
Tomanage AP firmware and download the latest AP firmware to your Firebox
n From FirewareWebUI select Dashboard gt Gateway Wireless Controller From theSummary tabclick Manage Firmware
n From Firebox SystemManager select theGateway Wireless Controller tab then click ManageFirmware
Note that you cannot upgrade an AP120 AP320 AP322 or AP420 to 830-657 or higher unless your Firebox isrunning Fireware v11124 or higher If your Firebox does not run v11124 or higher you will not see an optionto upgrade to AP firmware v830-657 or higher
If you have enabled automatic AP device firmware updates in Gateway Wireless Controller your AP devicesare automatically updated betweenmidnight and 400am local time
Tomanually update firmware on your AP devices
1 On theAccess Points tab select one or more AP devices2 From theActions drop-down list click Upgrade3 Click Yes to confirm that you want to upgrade the AP device
Update AP Devices
20 WatchGuard Technologies Inc
Upgrade your FireCluster to Fireware v1213
Release Notes 21
Upgrade your FireCluster to Fireware v1213You can upgrade Fireware OS for a FireCluster from Policy Manager or FirewareWebUI To upgrade aFireCluster from Fireware v1110x or lower we recommend you use Policy Manager
As part of the upgrade process each cluster member reboots and rejoins the cluster Because the clustercannot do load balancing while a cluster member reboot is in progress we recommend you upgrade anactiveactive cluster at a time when the network traffic is lightest
For information on how to upgrade your FireCluster see this Help topic
There is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Before you upgrade to Fireware v1111 or higher your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is prevented
If you try to schedule anOS update of managed devices through aManagement Server theupgrade is also prevented
If you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x before youupgrade to Fireware v1111x or higher or your Firebox will be reset to a default state
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
XTMv Upgrade NotesYou cannot upgrade an XTMv device to FireboxV For Fireware v1111 and higher the XTMv device is a 64-bitvirtual machine You cannot upgrade an XTMv device from Fireware v1110x or lower to Fireware v1111 orhigher Instead youmust use the OVA file to deploy a new 64-bit Fireware v1111x or v12x XTMv VM andthen use Policy Manager to move the existing configuration from the 32-bit XTMv VM to the 64-bit XTMv VMFor more information about how tomove the configuration or deploy a new XTMv VM see Fireware Help Whenyour XTMv instance has been updated to v1111 or higher you can then use the usual upgrade procedure asdetailed in the next section
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
If your Firebox is a T10 XTM 25 or XTM 26 device with OS version 121 or older youmightnot be able to perform a backup before you upgrade the Firebox This occurs because thememory use by Fireware v121 or older does not leave enoughmemory free to successfullycomplete the upgrade process on these devices For these devices we recommend you savea copy of the xml configuration file with a distinctive name as described here Save theConfiguration File
If you need to downgrade a Firebox without a backup file after you complete the upgrade toFireware v12x we recommend you Downgrade withWebUI This process deletes theconfiguration file but does not remove the device feature keys and certificates After youdowngrade the Firebox you can use Policy Manager to Save the Configuration File to theFireboxIf your Firebox has Fireware v1211 or later the Firebox will temporarily disable somesecurity services to free up enoughmemory to successfully perform a backup To learnmoresee Backup and Restore for XTM 25 XTM 26 and Firebox T10
Important Information about the upgrade process
l We recommend you use FirewareWebUI to upgrade to Fireware v12x You can also use PolicyManager if you prefer
l We strongly recommend that you save a local copy of your Firebox configuration and create a Fireboxbackup image before you upgrade
l If you useWatchGuard SystemManager (WSM) make sure yourWSM version is equal to or higherthan the version of Fireware OS installed on your Firebox and the version of WSM installed on yourManagement Server Also make sure to upgradeWSM before you upgrade the version of Fireware OSon your Firebox
Upgrade to Fireware v1213
14 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 15
If you want to upgrade a Firebox T10 XTM 2Series 33 330 or 5 Series device werecommend that you reboot your Firebox before you upgrade This clears your devicememoryand can prevent many problems commonly associated with upgrades in those devices
Back Up Your WatchGuard ServersIt is not usually necessary to uninstall your previous v11x or v12x server or client software when you upgradetoWSM v12x You can install the v12x server and client software on top of your existing installation toupgrade yourWatchGuard software components We do however strongly recommend that you back up yourWatchGuard Servers (for example yourWatchGuardManagement Server) to a safe location before youupgrade You will need these backup files if you ever want to downgrade
You cannot restore aWatchGuard Server backup file created withWatchGuard SystemManager v12x to to a v11x installation Make sure to retain your older server backup fileswhen you upgrade to v120 or later in case you want to downgrade in the future
To back up your Management Server configuration from the computer where you installed theManagementServer
1 FromWatchGuard Server Center select BackupRestore Management ServerThe WatchGuard Server Center BackupRestore Wizard starts
2 Click NextThe Select an action screen appears
3 Select Back up settings4 Click Next
The Specify a backup file screen appears5 Click Browse to select a location for the backup file Make sure you save the configuration file to a
location you can access later to restore the configuration6 Click Next
The WatchGuard Server Center BackupRestore Wizard is complete screen appears7 Click Finish to exit the wizard
Upgrade to Fireware v1213 fromWeb UIIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from theSystem gt Upgrade OS page If your Firebox is running v119x or earlier use thesesteps to upgrade
1 Before you begin save a local copy of your configuration file2 Go toSystem gt Backup Image or use the USB Backup feature to back up your current device image3 On your management computer launch the OS software file you downloaded from theWatchGuard
Software Downloads pageIf you use theWindows-based installer on a computer with aWindows 64-bit operating system thisinstallation extracts an upgrade file called [product series]_[product code]sysa-dl to the defaultlocation of CProgram Files(x86)Common FilesWatchGuardresourcesFirewareXTM1213[model]or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Connect to your Firebox with theWebUI and select System gt Upgrade OS5 Browse to the location of the [product series]_[product code]sysa-dl from Step 2 and click Upgrade
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v121 3installer twice (once to remove v1213 software and again to install v1213)
Upgrade to Fireware v1213
16 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 17
Upgrade to Fireware v1213 fromWSMPolicy Manager1 Before you begin save a local copy of your configuration file2 Select File gt Backup or use the USB Backup feature to back up your current device image3 On amanagement computer running aWindows 64-bit operating system launch the OS executable file
you downloaded from theWatchGuard Portal This installation extracts an upgrade file called [Firebox orxtm series]_[product code]sysa-dl to the default location of CProgram Files(x86)CommonfilesWatchGuardresourcesFirewareXTM1213[model] or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Install and openWatchGuard SystemManager v1213 Connect to your Firebox and launch PolicyManager
5 From Policy Manager select File gt Upgrade When prompted browse to and select the [productseries]_[product code]sysa-dl file from Step 2
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v1213installer twice (once to remove v1213 software and again to install v1213)
If you like tomake updates to your Firebox configuration from a saved configuration file makesure you open the configuration from the Firebox and save it to a new file after you upgradeThis is to make sure that you do not overwrite any configuration changes that weremade aspart of the upgrade
Other Upgrade IssuesThere is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Fireware v12x is not supported on XTM 5Series devices models 505 510 520 or 530
Before you upgrade to Fireware v12x your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is preventedIf you try to schedule anOS update of managed devices through aManagement Server theupgrade is also preventedIf you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x orv1110x before you upgrade to Fireware v12x or your Firebox will be reset to a default state
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
18 WatchGuard Technologies Inc
Update AP Devices
Release Notes 19
Update AP Devices
OnApril 12 2018 WatchGuard released AP firmware versions 12915 for the AP100 AP102and AP200 and 20010 for the AP300 to address security vulnerabilities We highlyrecommend you install these AP firmware updates For more detailed information on thesevulnerabilities see AP100AP102AP200 Chained Vulnerabilities In addition to addressingthese vulnerabilities the AP firmware updates disable the AP local web UI As these APmodels can only bemanaged with the Gateway Wireless Controller the AP local web UI is nolonger supported
Beginning with Fireware v11124 AP firmware is no longer bundled with Fireware OS All AP device firmwareis managed by the Gateway Wireless Controller on your Firebox TheGateway Wireless Controllerautomatically checks for new AP firmware updates and enables you to download the firmware directly fromWatchGuard servers
Important Upgrade StepsIf you have not previously upgraded to Fireware 1201 or higher and the latest AP firmware youmust performthese steps
1 Make sure all your APs are online You can check AP status from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager selecttheGateway Wireless Controller tab
2 Make sure you are not using insecure default AP passphrases such as wgwap orwatchguard Yourcurrent AP passphrasemust be secure and at least 8 characters in length You can change your APpassphrase inNetwork gt Gateway Wireless Controller gt Settings
If you do not have a secure passphrase correctly configured before the upgrade you will losethemanagement connection with your deployed APs If this occurs youmust physicallyreset the APs to factory default settings to be able tomanage the APs from GatewayWireless Controller
Depending on the version of Fireware you are upgrading from youmay need tomark APs as trusted after theupgrade to Fireware v1201 or higher You canmark APs as trusted from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager select theGateway Wireless Controller tab
AP Firmware UpgradeThe current AP firmware versions for each AP devicemodel are
AP Device Model Current Firmware Version
AP100 AP102 AP200 12915
AP300 20010
AP120 AP320 AP322 AP325AP420
850-646
Tomanage AP firmware and download the latest AP firmware to your Firebox
n From FirewareWebUI select Dashboard gt Gateway Wireless Controller From theSummary tabclick Manage Firmware
n From Firebox SystemManager select theGateway Wireless Controller tab then click ManageFirmware
Note that you cannot upgrade an AP120 AP320 AP322 or AP420 to 830-657 or higher unless your Firebox isrunning Fireware v11124 or higher If your Firebox does not run v11124 or higher you will not see an optionto upgrade to AP firmware v830-657 or higher
If you have enabled automatic AP device firmware updates in Gateway Wireless Controller your AP devicesare automatically updated betweenmidnight and 400am local time
Tomanually update firmware on your AP devices
1 On theAccess Points tab select one or more AP devices2 From theActions drop-down list click Upgrade3 Click Yes to confirm that you want to upgrade the AP device
Update AP Devices
20 WatchGuard Technologies Inc
Upgrade your FireCluster to Fireware v1213
Release Notes 21
Upgrade your FireCluster to Fireware v1213You can upgrade Fireware OS for a FireCluster from Policy Manager or FirewareWebUI To upgrade aFireCluster from Fireware v1110x or lower we recommend you use Policy Manager
As part of the upgrade process each cluster member reboots and rejoins the cluster Because the clustercannot do load balancing while a cluster member reboot is in progress we recommend you upgrade anactiveactive cluster at a time when the network traffic is lightest
For information on how to upgrade your FireCluster see this Help topic
There is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Before you upgrade to Fireware v1111 or higher your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is prevented
If you try to schedule anOS update of managed devices through aManagement Server theupgrade is also prevented
If you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x before youupgrade to Fireware v1111x or higher or your Firebox will be reset to a default state
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
Upgrade to Fireware v1213
Release Notes 15
If you want to upgrade a Firebox T10 XTM 2Series 33 330 or 5 Series device werecommend that you reboot your Firebox before you upgrade This clears your devicememoryand can prevent many problems commonly associated with upgrades in those devices
Back Up Your WatchGuard ServersIt is not usually necessary to uninstall your previous v11x or v12x server or client software when you upgradetoWSM v12x You can install the v12x server and client software on top of your existing installation toupgrade yourWatchGuard software components We do however strongly recommend that you back up yourWatchGuard Servers (for example yourWatchGuardManagement Server) to a safe location before youupgrade You will need these backup files if you ever want to downgrade
You cannot restore aWatchGuard Server backup file created withWatchGuard SystemManager v12x to to a v11x installation Make sure to retain your older server backup fileswhen you upgrade to v120 or later in case you want to downgrade in the future
To back up your Management Server configuration from the computer where you installed theManagementServer
1 FromWatchGuard Server Center select BackupRestore Management ServerThe WatchGuard Server Center BackupRestore Wizard starts
2 Click NextThe Select an action screen appears
3 Select Back up settings4 Click Next
The Specify a backup file screen appears5 Click Browse to select a location for the backup file Make sure you save the configuration file to a
location you can access later to restore the configuration6 Click Next
The WatchGuard Server Center BackupRestore Wizard is complete screen appears7 Click Finish to exit the wizard
Upgrade to Fireware v1213 fromWeb UIIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from theSystem gt Upgrade OS page If your Firebox is running v119x or earlier use thesesteps to upgrade
1 Before you begin save a local copy of your configuration file2 Go toSystem gt Backup Image or use the USB Backup feature to back up your current device image3 On your management computer launch the OS software file you downloaded from theWatchGuard
Software Downloads pageIf you use theWindows-based installer on a computer with aWindows 64-bit operating system thisinstallation extracts an upgrade file called [product series]_[product code]sysa-dl to the defaultlocation of CProgram Files(x86)Common FilesWatchGuardresourcesFirewareXTM1213[model]or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Connect to your Firebox with theWebUI and select System gt Upgrade OS5 Browse to the location of the [product series]_[product code]sysa-dl from Step 2 and click Upgrade
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v121 3installer twice (once to remove v1213 software and again to install v1213)
Upgrade to Fireware v1213
16 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 17
Upgrade to Fireware v1213 fromWSMPolicy Manager1 Before you begin save a local copy of your configuration file2 Select File gt Backup or use the USB Backup feature to back up your current device image3 On amanagement computer running aWindows 64-bit operating system launch the OS executable file
you downloaded from theWatchGuard Portal This installation extracts an upgrade file called [Firebox orxtm series]_[product code]sysa-dl to the default location of CProgram Files(x86)CommonfilesWatchGuardresourcesFirewareXTM1213[model] or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Install and openWatchGuard SystemManager v1213 Connect to your Firebox and launch PolicyManager
5 From Policy Manager select File gt Upgrade When prompted browse to and select the [productseries]_[product code]sysa-dl file from Step 2
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v1213installer twice (once to remove v1213 software and again to install v1213)
If you like tomake updates to your Firebox configuration from a saved configuration file makesure you open the configuration from the Firebox and save it to a new file after you upgradeThis is to make sure that you do not overwrite any configuration changes that weremade aspart of the upgrade
Other Upgrade IssuesThere is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Fireware v12x is not supported on XTM 5Series devices models 505 510 520 or 530
Before you upgrade to Fireware v12x your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is preventedIf you try to schedule anOS update of managed devices through aManagement Server theupgrade is also preventedIf you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x orv1110x before you upgrade to Fireware v12x or your Firebox will be reset to a default state
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
18 WatchGuard Technologies Inc
Update AP Devices
Release Notes 19
Update AP Devices
OnApril 12 2018 WatchGuard released AP firmware versions 12915 for the AP100 AP102and AP200 and 20010 for the AP300 to address security vulnerabilities We highlyrecommend you install these AP firmware updates For more detailed information on thesevulnerabilities see AP100AP102AP200 Chained Vulnerabilities In addition to addressingthese vulnerabilities the AP firmware updates disable the AP local web UI As these APmodels can only bemanaged with the Gateway Wireless Controller the AP local web UI is nolonger supported
Beginning with Fireware v11124 AP firmware is no longer bundled with Fireware OS All AP device firmwareis managed by the Gateway Wireless Controller on your Firebox TheGateway Wireless Controllerautomatically checks for new AP firmware updates and enables you to download the firmware directly fromWatchGuard servers
Important Upgrade StepsIf you have not previously upgraded to Fireware 1201 or higher and the latest AP firmware youmust performthese steps
1 Make sure all your APs are online You can check AP status from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager selecttheGateway Wireless Controller tab
2 Make sure you are not using insecure default AP passphrases such as wgwap orwatchguard Yourcurrent AP passphrasemust be secure and at least 8 characters in length You can change your APpassphrase inNetwork gt Gateway Wireless Controller gt Settings
If you do not have a secure passphrase correctly configured before the upgrade you will losethemanagement connection with your deployed APs If this occurs youmust physicallyreset the APs to factory default settings to be able tomanage the APs from GatewayWireless Controller
Depending on the version of Fireware you are upgrading from youmay need tomark APs as trusted after theupgrade to Fireware v1201 or higher You canmark APs as trusted from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager select theGateway Wireless Controller tab
AP Firmware UpgradeThe current AP firmware versions for each AP devicemodel are
AP Device Model Current Firmware Version
AP100 AP102 AP200 12915
AP300 20010
AP120 AP320 AP322 AP325AP420
850-646
Tomanage AP firmware and download the latest AP firmware to your Firebox
n From FirewareWebUI select Dashboard gt Gateway Wireless Controller From theSummary tabclick Manage Firmware
n From Firebox SystemManager select theGateway Wireless Controller tab then click ManageFirmware
Note that you cannot upgrade an AP120 AP320 AP322 or AP420 to 830-657 or higher unless your Firebox isrunning Fireware v11124 or higher If your Firebox does not run v11124 or higher you will not see an optionto upgrade to AP firmware v830-657 or higher
If you have enabled automatic AP device firmware updates in Gateway Wireless Controller your AP devicesare automatically updated betweenmidnight and 400am local time
Tomanually update firmware on your AP devices
1 On theAccess Points tab select one or more AP devices2 From theActions drop-down list click Upgrade3 Click Yes to confirm that you want to upgrade the AP device
Update AP Devices
20 WatchGuard Technologies Inc
Upgrade your FireCluster to Fireware v1213
Release Notes 21
Upgrade your FireCluster to Fireware v1213You can upgrade Fireware OS for a FireCluster from Policy Manager or FirewareWebUI To upgrade aFireCluster from Fireware v1110x or lower we recommend you use Policy Manager
As part of the upgrade process each cluster member reboots and rejoins the cluster Because the clustercannot do load balancing while a cluster member reboot is in progress we recommend you upgrade anactiveactive cluster at a time when the network traffic is lightest
For information on how to upgrade your FireCluster see this Help topic
There is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Before you upgrade to Fireware v1111 or higher your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is prevented
If you try to schedule anOS update of managed devices through aManagement Server theupgrade is also prevented
If you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x before youupgrade to Fireware v1111x or higher or your Firebox will be reset to a default state
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
Back Up Your WatchGuard ServersIt is not usually necessary to uninstall your previous v11x or v12x server or client software when you upgradetoWSM v12x You can install the v12x server and client software on top of your existing installation toupgrade yourWatchGuard software components We do however strongly recommend that you back up yourWatchGuard Servers (for example yourWatchGuardManagement Server) to a safe location before youupgrade You will need these backup files if you ever want to downgrade
You cannot restore aWatchGuard Server backup file created withWatchGuard SystemManager v12x to to a v11x installation Make sure to retain your older server backup fileswhen you upgrade to v120 or later in case you want to downgrade in the future
To back up your Management Server configuration from the computer where you installed theManagementServer
1 FromWatchGuard Server Center select BackupRestore Management ServerThe WatchGuard Server Center BackupRestore Wizard starts
2 Click NextThe Select an action screen appears
3 Select Back up settings4 Click Next
The Specify a backup file screen appears5 Click Browse to select a location for the backup file Make sure you save the configuration file to a
location you can access later to restore the configuration6 Click Next
The WatchGuard Server Center BackupRestore Wizard is complete screen appears7 Click Finish to exit the wizard
Upgrade to Fireware v1213 fromWeb UIIf your Firebox is running Fireware v1110 or later you can upgrade the Fireware OS on your Fireboxautomatically from theSystem gt Upgrade OS page If your Firebox is running v119x or earlier use thesesteps to upgrade
1 Before you begin save a local copy of your configuration file2 Go toSystem gt Backup Image or use the USB Backup feature to back up your current device image3 On your management computer launch the OS software file you downloaded from theWatchGuard
Software Downloads pageIf you use theWindows-based installer on a computer with aWindows 64-bit operating system thisinstallation extracts an upgrade file called [product series]_[product code]sysa-dl to the defaultlocation of CProgram Files(x86)Common FilesWatchGuardresourcesFirewareXTM1213[model]or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Connect to your Firebox with theWebUI and select System gt Upgrade OS5 Browse to the location of the [product series]_[product code]sysa-dl from Step 2 and click Upgrade
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v121 3installer twice (once to remove v1213 software and again to install v1213)
Upgrade to Fireware v1213
16 WatchGuard Technologies Inc
Upgrade to Fireware v1213
Release Notes 17
Upgrade to Fireware v1213 fromWSMPolicy Manager1 Before you begin save a local copy of your configuration file2 Select File gt Backup or use the USB Backup feature to back up your current device image3 On amanagement computer running aWindows 64-bit operating system launch the OS executable file
you downloaded from theWatchGuard Portal This installation extracts an upgrade file called [Firebox orxtm series]_[product code]sysa-dl to the default location of CProgram Files(x86)CommonfilesWatchGuardresourcesFirewareXTM1213[model] or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Install and openWatchGuard SystemManager v1213 Connect to your Firebox and launch PolicyManager
5 From Policy Manager select File gt Upgrade When prompted browse to and select the [productseries]_[product code]sysa-dl file from Step 2
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v1213installer twice (once to remove v1213 software and again to install v1213)
If you like tomake updates to your Firebox configuration from a saved configuration file makesure you open the configuration from the Firebox and save it to a new file after you upgradeThis is to make sure that you do not overwrite any configuration changes that weremade aspart of the upgrade
Other Upgrade IssuesThere is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Fireware v12x is not supported on XTM 5Series devices models 505 510 520 or 530
Before you upgrade to Fireware v12x your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is preventedIf you try to schedule anOS update of managed devices through aManagement Server theupgrade is also preventedIf you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x orv1110x before you upgrade to Fireware v12x or your Firebox will be reset to a default state
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
18 WatchGuard Technologies Inc
Update AP Devices
Release Notes 19
Update AP Devices
OnApril 12 2018 WatchGuard released AP firmware versions 12915 for the AP100 AP102and AP200 and 20010 for the AP300 to address security vulnerabilities We highlyrecommend you install these AP firmware updates For more detailed information on thesevulnerabilities see AP100AP102AP200 Chained Vulnerabilities In addition to addressingthese vulnerabilities the AP firmware updates disable the AP local web UI As these APmodels can only bemanaged with the Gateway Wireless Controller the AP local web UI is nolonger supported
Beginning with Fireware v11124 AP firmware is no longer bundled with Fireware OS All AP device firmwareis managed by the Gateway Wireless Controller on your Firebox TheGateway Wireless Controllerautomatically checks for new AP firmware updates and enables you to download the firmware directly fromWatchGuard servers
Important Upgrade StepsIf you have not previously upgraded to Fireware 1201 or higher and the latest AP firmware youmust performthese steps
1 Make sure all your APs are online You can check AP status from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager selecttheGateway Wireless Controller tab
2 Make sure you are not using insecure default AP passphrases such as wgwap orwatchguard Yourcurrent AP passphrasemust be secure and at least 8 characters in length You can change your APpassphrase inNetwork gt Gateway Wireless Controller gt Settings
If you do not have a secure passphrase correctly configured before the upgrade you will losethemanagement connection with your deployed APs If this occurs youmust physicallyreset the APs to factory default settings to be able tomanage the APs from GatewayWireless Controller
Depending on the version of Fireware you are upgrading from youmay need tomark APs as trusted after theupgrade to Fireware v1201 or higher You canmark APs as trusted from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager select theGateway Wireless Controller tab
AP Firmware UpgradeThe current AP firmware versions for each AP devicemodel are
AP Device Model Current Firmware Version
AP100 AP102 AP200 12915
AP300 20010
AP120 AP320 AP322 AP325AP420
850-646
Tomanage AP firmware and download the latest AP firmware to your Firebox
n From FirewareWebUI select Dashboard gt Gateway Wireless Controller From theSummary tabclick Manage Firmware
n From Firebox SystemManager select theGateway Wireless Controller tab then click ManageFirmware
Note that you cannot upgrade an AP120 AP320 AP322 or AP420 to 830-657 or higher unless your Firebox isrunning Fireware v11124 or higher If your Firebox does not run v11124 or higher you will not see an optionto upgrade to AP firmware v830-657 or higher
If you have enabled automatic AP device firmware updates in Gateway Wireless Controller your AP devicesare automatically updated betweenmidnight and 400am local time
Tomanually update firmware on your AP devices
1 On theAccess Points tab select one or more AP devices2 From theActions drop-down list click Upgrade3 Click Yes to confirm that you want to upgrade the AP device
Update AP Devices
20 WatchGuard Technologies Inc
Upgrade your FireCluster to Fireware v1213
Release Notes 21
Upgrade your FireCluster to Fireware v1213You can upgrade Fireware OS for a FireCluster from Policy Manager or FirewareWebUI To upgrade aFireCluster from Fireware v1110x or lower we recommend you use Policy Manager
As part of the upgrade process each cluster member reboots and rejoins the cluster Because the clustercannot do load balancing while a cluster member reboot is in progress we recommend you upgrade anactiveactive cluster at a time when the network traffic is lightest
For information on how to upgrade your FireCluster see this Help topic
There is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Before you upgrade to Fireware v1111 or higher your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is prevented
If you try to schedule anOS update of managed devices through aManagement Server theupgrade is also prevented
If you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x before youupgrade to Fireware v1111x or higher or your Firebox will be reset to a default state
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
Upgrade to Fireware v1213
Release Notes 17
Upgrade to Fireware v1213 fromWSMPolicy Manager1 Before you begin save a local copy of your configuration file2 Select File gt Backup or use the USB Backup feature to back up your current device image3 On amanagement computer running aWindows 64-bit operating system launch the OS executable file
you downloaded from theWatchGuard Portal This installation extracts an upgrade file called [Firebox orxtm series]_[product code]sysa-dl to the default location of CProgram Files(x86)CommonfilesWatchGuardresourcesFirewareXTM1213[model] or [model][product_code]On a computer with aWindows 32-bit operating system the path is CProgram FilesCommonFilesWatchGuardresourcesFirewareXTM1213
4 Install and openWatchGuard SystemManager v1213 Connect to your Firebox and launch PolicyManager
5 From Policy Manager select File gt Upgrade When prompted browse to and select the [productseries]_[product code]sysa-dl file from Step 2
If you have installed a beta release of Fireware v1213 on your computer youmust run the Fireware v1213installer twice (once to remove v1213 software and again to install v1213)
If you like tomake updates to your Firebox configuration from a saved configuration file makesure you open the configuration from the Firebox and save it to a new file after you upgradeThis is to make sure that you do not overwrite any configuration changes that weremade aspart of the upgrade
Other Upgrade IssuesThere is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Fireware v12x is not supported on XTM 5Series devices models 505 510 520 or 530
Before you upgrade to Fireware v12x your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is preventedIf you try to schedule anOS update of managed devices through aManagement Server theupgrade is also preventedIf you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x orv1110x before you upgrade to Fireware v12x or your Firebox will be reset to a default state
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
18 WatchGuard Technologies Inc
Update AP Devices
Release Notes 19
Update AP Devices
OnApril 12 2018 WatchGuard released AP firmware versions 12915 for the AP100 AP102and AP200 and 20010 for the AP300 to address security vulnerabilities We highlyrecommend you install these AP firmware updates For more detailed information on thesevulnerabilities see AP100AP102AP200 Chained Vulnerabilities In addition to addressingthese vulnerabilities the AP firmware updates disable the AP local web UI As these APmodels can only bemanaged with the Gateway Wireless Controller the AP local web UI is nolonger supported
Beginning with Fireware v11124 AP firmware is no longer bundled with Fireware OS All AP device firmwareis managed by the Gateway Wireless Controller on your Firebox TheGateway Wireless Controllerautomatically checks for new AP firmware updates and enables you to download the firmware directly fromWatchGuard servers
Important Upgrade StepsIf you have not previously upgraded to Fireware 1201 or higher and the latest AP firmware youmust performthese steps
1 Make sure all your APs are online You can check AP status from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager selecttheGateway Wireless Controller tab
2 Make sure you are not using insecure default AP passphrases such as wgwap orwatchguard Yourcurrent AP passphrasemust be secure and at least 8 characters in length You can change your APpassphrase inNetwork gt Gateway Wireless Controller gt Settings
If you do not have a secure passphrase correctly configured before the upgrade you will losethemanagement connection with your deployed APs If this occurs youmust physicallyreset the APs to factory default settings to be able tomanage the APs from GatewayWireless Controller
Depending on the version of Fireware you are upgrading from youmay need tomark APs as trusted after theupgrade to Fireware v1201 or higher You canmark APs as trusted from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager select theGateway Wireless Controller tab
AP Firmware UpgradeThe current AP firmware versions for each AP devicemodel are
AP Device Model Current Firmware Version
AP100 AP102 AP200 12915
AP300 20010
AP120 AP320 AP322 AP325AP420
850-646
Tomanage AP firmware and download the latest AP firmware to your Firebox
n From FirewareWebUI select Dashboard gt Gateway Wireless Controller From theSummary tabclick Manage Firmware
n From Firebox SystemManager select theGateway Wireless Controller tab then click ManageFirmware
Note that you cannot upgrade an AP120 AP320 AP322 or AP420 to 830-657 or higher unless your Firebox isrunning Fireware v11124 or higher If your Firebox does not run v11124 or higher you will not see an optionto upgrade to AP firmware v830-657 or higher
If you have enabled automatic AP device firmware updates in Gateway Wireless Controller your AP devicesare automatically updated betweenmidnight and 400am local time
Tomanually update firmware on your AP devices
1 On theAccess Points tab select one or more AP devices2 From theActions drop-down list click Upgrade3 Click Yes to confirm that you want to upgrade the AP device
Update AP Devices
20 WatchGuard Technologies Inc
Upgrade your FireCluster to Fireware v1213
Release Notes 21
Upgrade your FireCluster to Fireware v1213You can upgrade Fireware OS for a FireCluster from Policy Manager or FirewareWebUI To upgrade aFireCluster from Fireware v1110x or lower we recommend you use Policy Manager
As part of the upgrade process each cluster member reboots and rejoins the cluster Because the clustercannot do load balancing while a cluster member reboot is in progress we recommend you upgrade anactiveactive cluster at a time when the network traffic is lightest
For information on how to upgrade your FireCluster see this Help topic
There is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Before you upgrade to Fireware v1111 or higher your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is prevented
If you try to schedule anOS update of managed devices through aManagement Server theupgrade is also prevented
If you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x before youupgrade to Fireware v1111x or higher or your Firebox will be reset to a default state
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
WatchGuard updated the certificate used to sign the ova files with the release of Firewarev1111 When you deploy the OVF template a certificate error may appear in the OVF templatedetails This error occurs when the host machine is missing an intermediate certificate fromSymantic (Symantec Class 3 SHA256 Code Signing CA) and theWindows CryptoAPI wasunable to download it To resolve this error you can download and install the certificate fromSymantec
Upgrade to Fireware v1213
18 WatchGuard Technologies Inc
Update AP Devices
Release Notes 19
Update AP Devices
OnApril 12 2018 WatchGuard released AP firmware versions 12915 for the AP100 AP102and AP200 and 20010 for the AP300 to address security vulnerabilities We highlyrecommend you install these AP firmware updates For more detailed information on thesevulnerabilities see AP100AP102AP200 Chained Vulnerabilities In addition to addressingthese vulnerabilities the AP firmware updates disable the AP local web UI As these APmodels can only bemanaged with the Gateway Wireless Controller the AP local web UI is nolonger supported
Beginning with Fireware v11124 AP firmware is no longer bundled with Fireware OS All AP device firmwareis managed by the Gateway Wireless Controller on your Firebox TheGateway Wireless Controllerautomatically checks for new AP firmware updates and enables you to download the firmware directly fromWatchGuard servers
Important Upgrade StepsIf you have not previously upgraded to Fireware 1201 or higher and the latest AP firmware youmust performthese steps
1 Make sure all your APs are online You can check AP status from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager selecttheGateway Wireless Controller tab
2 Make sure you are not using insecure default AP passphrases such as wgwap orwatchguard Yourcurrent AP passphrasemust be secure and at least 8 characters in length You can change your APpassphrase inNetwork gt Gateway Wireless Controller gt Settings
If you do not have a secure passphrase correctly configured before the upgrade you will losethemanagement connection with your deployed APs If this occurs youmust physicallyreset the APs to factory default settings to be able tomanage the APs from GatewayWireless Controller
Depending on the version of Fireware you are upgrading from youmay need tomark APs as trusted after theupgrade to Fireware v1201 or higher You canmark APs as trusted from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager select theGateway Wireless Controller tab
AP Firmware UpgradeThe current AP firmware versions for each AP devicemodel are
AP Device Model Current Firmware Version
AP100 AP102 AP200 12915
AP300 20010
AP120 AP320 AP322 AP325AP420
850-646
Tomanage AP firmware and download the latest AP firmware to your Firebox
n From FirewareWebUI select Dashboard gt Gateway Wireless Controller From theSummary tabclick Manage Firmware
n From Firebox SystemManager select theGateway Wireless Controller tab then click ManageFirmware
Note that you cannot upgrade an AP120 AP320 AP322 or AP420 to 830-657 or higher unless your Firebox isrunning Fireware v11124 or higher If your Firebox does not run v11124 or higher you will not see an optionto upgrade to AP firmware v830-657 or higher
If you have enabled automatic AP device firmware updates in Gateway Wireless Controller your AP devicesare automatically updated betweenmidnight and 400am local time
Tomanually update firmware on your AP devices
1 On theAccess Points tab select one or more AP devices2 From theActions drop-down list click Upgrade3 Click Yes to confirm that you want to upgrade the AP device
Update AP Devices
20 WatchGuard Technologies Inc
Upgrade your FireCluster to Fireware v1213
Release Notes 21
Upgrade your FireCluster to Fireware v1213You can upgrade Fireware OS for a FireCluster from Policy Manager or FirewareWebUI To upgrade aFireCluster from Fireware v1110x or lower we recommend you use Policy Manager
As part of the upgrade process each cluster member reboots and rejoins the cluster Because the clustercannot do load balancing while a cluster member reboot is in progress we recommend you upgrade anactiveactive cluster at a time when the network traffic is lightest
For information on how to upgrade your FireCluster see this Help topic
There is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Before you upgrade to Fireware v1111 or higher your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is prevented
If you try to schedule anOS update of managed devices through aManagement Server theupgrade is also prevented
If you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x before youupgrade to Fireware v1111x or higher or your Firebox will be reset to a default state
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
Update AP Devices
Release Notes 19
Update AP Devices
OnApril 12 2018 WatchGuard released AP firmware versions 12915 for the AP100 AP102and AP200 and 20010 for the AP300 to address security vulnerabilities We highlyrecommend you install these AP firmware updates For more detailed information on thesevulnerabilities see AP100AP102AP200 Chained Vulnerabilities In addition to addressingthese vulnerabilities the AP firmware updates disable the AP local web UI As these APmodels can only bemanaged with the Gateway Wireless Controller the AP local web UI is nolonger supported
Beginning with Fireware v11124 AP firmware is no longer bundled with Fireware OS All AP device firmwareis managed by the Gateway Wireless Controller on your Firebox TheGateway Wireless Controllerautomatically checks for new AP firmware updates and enables you to download the firmware directly fromWatchGuard servers
Important Upgrade StepsIf you have not previously upgraded to Fireware 1201 or higher and the latest AP firmware youmust performthese steps
1 Make sure all your APs are online You can check AP status from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager selecttheGateway Wireless Controller tab
2 Make sure you are not using insecure default AP passphrases such as wgwap orwatchguard Yourcurrent AP passphrasemust be secure and at least 8 characters in length You can change your APpassphrase inNetwork gt Gateway Wireless Controller gt Settings
If you do not have a secure passphrase correctly configured before the upgrade you will losethemanagement connection with your deployed APs If this occurs youmust physicallyreset the APs to factory default settings to be able tomanage the APs from GatewayWireless Controller
Depending on the version of Fireware you are upgrading from youmay need tomark APs as trusted after theupgrade to Fireware v1201 or higher You canmark APs as trusted from FirewareWebUI inDashboardgt Gateway Wireless Controller on theAccess Points tab or from Firebox SystemManager select theGateway Wireless Controller tab
AP Firmware UpgradeThe current AP firmware versions for each AP devicemodel are
AP Device Model Current Firmware Version
AP100 AP102 AP200 12915
AP300 20010
AP120 AP320 AP322 AP325AP420
850-646
Tomanage AP firmware and download the latest AP firmware to your Firebox
n From FirewareWebUI select Dashboard gt Gateway Wireless Controller From theSummary tabclick Manage Firmware
n From Firebox SystemManager select theGateway Wireless Controller tab then click ManageFirmware
Note that you cannot upgrade an AP120 AP320 AP322 or AP420 to 830-657 or higher unless your Firebox isrunning Fireware v11124 or higher If your Firebox does not run v11124 or higher you will not see an optionto upgrade to AP firmware v830-657 or higher
If you have enabled automatic AP device firmware updates in Gateway Wireless Controller your AP devicesare automatically updated betweenmidnight and 400am local time
Tomanually update firmware on your AP devices
1 On theAccess Points tab select one or more AP devices2 From theActions drop-down list click Upgrade3 Click Yes to confirm that you want to upgrade the AP device
Update AP Devices
20 WatchGuard Technologies Inc
Upgrade your FireCluster to Fireware v1213
Release Notes 21
Upgrade your FireCluster to Fireware v1213You can upgrade Fireware OS for a FireCluster from Policy Manager or FirewareWebUI To upgrade aFireCluster from Fireware v1110x or lower we recommend you use Policy Manager
As part of the upgrade process each cluster member reboots and rejoins the cluster Because the clustercannot do load balancing while a cluster member reboot is in progress we recommend you upgrade anactiveactive cluster at a time when the network traffic is lightest
For information on how to upgrade your FireCluster see this Help topic
There is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Before you upgrade to Fireware v1111 or higher your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is prevented
If you try to schedule anOS update of managed devices through aManagement Server theupgrade is also prevented
If you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x before youupgrade to Fireware v1111x or higher or your Firebox will be reset to a default state
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
AP Firmware UpgradeThe current AP firmware versions for each AP devicemodel are
AP Device Model Current Firmware Version
AP100 AP102 AP200 12915
AP300 20010
AP120 AP320 AP322 AP325AP420
850-646
Tomanage AP firmware and download the latest AP firmware to your Firebox
n From FirewareWebUI select Dashboard gt Gateway Wireless Controller From theSummary tabclick Manage Firmware
n From Firebox SystemManager select theGateway Wireless Controller tab then click ManageFirmware
Note that you cannot upgrade an AP120 AP320 AP322 or AP420 to 830-657 or higher unless your Firebox isrunning Fireware v11124 or higher If your Firebox does not run v11124 or higher you will not see an optionto upgrade to AP firmware v830-657 or higher
If you have enabled automatic AP device firmware updates in Gateway Wireless Controller your AP devicesare automatically updated betweenmidnight and 400am local time
Tomanually update firmware on your AP devices
1 On theAccess Points tab select one or more AP devices2 From theActions drop-down list click Upgrade3 Click Yes to confirm that you want to upgrade the AP device
Update AP Devices
20 WatchGuard Technologies Inc
Upgrade your FireCluster to Fireware v1213
Release Notes 21
Upgrade your FireCluster to Fireware v1213You can upgrade Fireware OS for a FireCluster from Policy Manager or FirewareWebUI To upgrade aFireCluster from Fireware v1110x or lower we recommend you use Policy Manager
As part of the upgrade process each cluster member reboots and rejoins the cluster Because the clustercannot do load balancing while a cluster member reboot is in progress we recommend you upgrade anactiveactive cluster at a time when the network traffic is lightest
For information on how to upgrade your FireCluster see this Help topic
There is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Before you upgrade to Fireware v1111 or higher your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is prevented
If you try to schedule anOS update of managed devices through aManagement Server theupgrade is also prevented
If you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x before youupgrade to Fireware v1111x or higher or your Firebox will be reset to a default state
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
Upgrade your FireCluster to Fireware v1213
Release Notes 21
Upgrade your FireCluster to Fireware v1213You can upgrade Fireware OS for a FireCluster from Policy Manager or FirewareWebUI To upgrade aFireCluster from Fireware v1110x or lower we recommend you use Policy Manager
As part of the upgrade process each cluster member reboots and rejoins the cluster Because the clustercannot do load balancing while a cluster member reboot is in progress we recommend you upgrade anactiveactive cluster at a time when the network traffic is lightest
For information on how to upgrade your FireCluster see this Help topic
There is an upgrade issue that affects some Firebox M400M500 andM440 devices Pleasereview this knowledge base article carefully before you upgrade
Before you upgrade to Fireware v1111 or higher your Firebox must be running- Fireware XTM v1175- Fireware XTM v1184- Fireware XTM v119 or higher
If you try to upgrade from Policy Manager and your Firebox is running an unsupported versionthe upgrade is prevented
If you try to schedule anOS update of managed devices through aManagement Server theupgrade is also prevented
If you use the FirewareWebUI to upgrade your device you see a warning but it is possible tocontinue so youmust make sure your Firebox is running v1175 v1184 or v119x before youupgrade to Fireware v1111x or higher or your Firebox will be reset to a default state
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
Downgrade Instructions
Downgrade from WSM v1213 to earlier WSM v12x or v11xIf you want to revert from v1213 to an earlier version of WSM youmust uninstall WSM v1213When youuninstall chooseYeswhen the uninstaller asks if you want to delete server configuration and data files Afterthe server configuration and data files are deleted youmust restore the data and server configuration files youbacked up before you upgraded toWSM v1213
Next install the same version of WSM that you used before you upgraded toWSM v1213 The installershould detect your existing server configuration and try to restart your servers from the Finish dialog box If youuse aWatchGuardManagement Server useWatchGuard Server Center to restore the backupManagementServer configuration you created before you first upgraded toWSM v1213 Verify that all WatchGuard serversare running
Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
If you use the FirewareWebUI or CLI to downgrade from Fireware v1213 to an earlierversion the downgrade process resets the network and security settings on your device totheir factory-default settings The downgrade process does not change the devicepassphrases and does not remove the feature keys and certificates
If you want to downgrade from Fireware v1213 to an earlier version of Fireware the recommendedmethod isto use a backup image that you created before the upgrade to Fireware v1213 With a backup image you caneither
l Restore the full backup image you created when you upgraded to Fireware v1213 to complete thedowngrade or
l Use the USB backup file you created before the upgrade as your auto-restore image and then boot intorecovery mode with the USB drive plugged in to your device This is not an option for XTMv users
See Fireware Help for more information about these downgrade procedures and information about how todowngrade if you do not have a backup image
Downgrade RestrictionsSee this Knowledge Base article for a list of downgrade restrictions
When you downgrade the Fireware OS on your Firebox or XTM device the firmware on anypaired AP devices is not automatically downgraded We recommend that you reset the APdevice to its factory-default settings tomake sure that it can bemanaged by the older version ofFireware OS
Downgrade Instructions
22 WatchGuard Technologies Inc
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
Enhancements and Resolved Issues in Fireware 1213
Release Notes 23
Enhancements and Resolved Issues in Fireware 1213
Generall This release removes weak ciphers that do not support forward secrecy from the Firebox web server
[FBX-10752]l Web pages served by the Firebox now include security headers outlined in the OWASP Secure HeadersProject in HTTP responses [FBX-9691]
l This release resolves a vulnerability that made possible a SAML assertion replay attack against theAccess Portal [FBX-9731]
l This release corrects the Japanese localization of FireCluster upgrade error messages in FirewareWebUI [FBX-10941]
l Firebox SystemManager no longer reports an error when you view the Front Panel of a Firebox Cloudinstance [FBX-10910]
l Firebox SystemManager no longer frequently disconnects when you connect to a Firebox with an olderversion of Fireware [FBX-11814]
l This release resolves an issue that prevented certificate sync when the Firebox first joins a FireCluster[FBX-11449]
l This release resolves an issue that caused all authenticated sessions to terminate after configurationchanges aremade to authentication server settings with FirewareWebUI [FBX-11263]
Integrationsl This release resolves an issue that resulted in Autotask creating unintended duplicate configurations
[FBX-11533]l FirewareWebUI no longer allows invalid configuration options that cause AutoTask to fail [FBX-11771]
Networkingl This release resolves an issue that caused the Firebox to stop replying to DHCP requests [FBX-9213
FBX-10643]l This release resolves an issue that caused DHCP relay to stop working after a Firebox reboot [FBX-
11464]l This release resolves an issue that caused the removal of the default route after PPPoE interface re-negotiation [FBX-11668]
l The Huawei E3372modem now works correctly [FBX-10888]l This release resolves an issue with theWebUI that prevented changing the Link Monitor settings onT10T15 when using aModem as external interface [FBX-11040 FBX-10535]
l The Enable Link-Monitor check box no longer re-selects itself after you disable it [FBX-10214]l Policy Manager now correctly allows configuration of Multi-Wan for T15 Fireboxes with Fireware Pro
[FBX-11500]
Centralized Managementl Management Server now correctly restricts configuration options for active Directory based on RBACrole[FBX=9167]
VPNl Mobile VPN with SSL download page no longer fails to load for two-factor authentication users [FBX-
10085]
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
l This release resolves an issue that caused theMobile VPN with SSL process to crash when FIPS isenabled on Firebox [FBX-2558]
l BOVPN over TLS clients can now connect to a remote VPN server with its primary server configured asa domain name [FBX-11556]
l This release resolves a kernel crash that occurs whenMobile VPN with SSL traffic is sent through aVirtual Interface (VIF) [FBX-11800]
l This release adds enhancements to BOVPN Dead Peer Detection when the Firebox is located behind aNAT device [FBX-11192]
l This release adds several IPSec BOVPN stability improvements for Fireboxes in a NAT environment[FBX-11188]
l This release resolves an issue that causes Managed BranchOffice VPN tunnels to restart when the theManagement server changes the Firebox configuration [FBX-11400]
l SLVPN Management tunnels can now use the symbol as the first character of the password [FBX-11271]
l This release resolves an issue that caused packet loss through BranchOffice VPN onM4600 andM5600 with large amounts of traffic [FBX-11584]
Proxies and Servicesl This release reduces load on the Firebox processor caused by excessive proxy logmessages[FBX-
10691]l The HTTP proxy no longer fails to get theMD5 hash during a file upload when the file exceeds theGateway AV scan limit[FBX-11577]
l This release improves IPS and Application Control scanning when Content inspection is enabled onT15 T30 and XTM330 platforms[FBX-11354]
l IMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connectionshandled by the TCP-UDP proxy [FBX-10586]
l This release resolves an issue that caused somewebsites to fail to load in the Chrome browser forconnections through the HTTPS proxy with TCP MTU probing enabled [FBX-11280]
l A FireCluster member without a DNSWatch license will now correctly register to the DNSWatchservice when it becomes Master [FBX-10180]
l This release resolves an issue that prevented HostWatch from correctly displaying data related to SIPand H323 proxies [FBX-10238]
l This release includes several improvements in Proxy memory usage [FBX-11465 FBX-9256 FBX-10886]
l This release resolves amemory leak that occurred when the IMAP proxy was enabled [FBX-11255]l This release resolves an issue that preventedmail from downloading through the IMAP proxy with logmessages that included ldquofail to parse fetch argument listrdquo [FBX-10782]
l The status of Content Inspection is now included in IMAP proxy logmessages when viewed from theFirewareWebUI[FBX-10822]
l Logmessages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy[FBX-10125]
Wirelessl Gateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot duringthe upgrade process [FBX-11081]
l This release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled[FBX-9760]
Enhancements and Resolved Issues in Fireware 1213
24 WatchGuard Technologies Inc
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
Known Issues and Limitations
Release Notes 25
Known Issues and LimitationsKnown issues for Fireware v1213 and its management applications including workarounds where availablecan be found on the Technical Search gt Knowledge Base tab To see known issues for a specific release fromtheProduct amp Version filters you can expand the Fireware version list and select the check box for thatversion
Using the CLIThe Fireware CLI (Command Line Interface) is fully supported for v12x releases For information on how tostart and use the CLI see theCommand Line ReferenceGuide You can download the latest CLI guide fromthe documentation web site forWatchGuard Firebox XTM amp Dimension
Technical AssistanceFor technical assistance contact WatchGuard Technical Support by telephone or log in to theWatchGuardPortal on theWeb at httpswwwwatchguardcomwgrd-supportoverview When you contact TechnicalSupport youmust supply your registered Product Serial Number or Partner ID
Phone Number
US End Users 8772323531
International End Users +1 2066130456
AuthorizedWatchGuard Resellers 2065218375
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-
Technical Assistance
Release Notes 26
- Fireware v1213 Release Notes
- Introduction
- Before You Begin
- Localization
-
- Fireware Web UI
- WatchGuard System Manager
- Dimension WebCenter Quarantine Web UI and Wireless Hotspot
- Documentation
-
- Important Information about Firebox Certificates
-
- CLI Commands to Regenerate Default Firebox Certificates
-
- Fireware and WSM v1213 Operating System Compatibility
-
- Authentication Support
- System Requirements
- FireboxV System Requirements
-
- Downloading Software
-
- WatchGuard System Manager
- Fireware OS
- Single Sign-On Software
- Terminal Services Authentication Software
- Mobile VPN with SSL Client for Windows and Mac
- Mobile VPN with IPSec client for Windows and Mac
-
- Upgrade Notes
-
- SSLTLS Settings Precedence and Inheritance
- Modem Configurations Converted to External Interfaces with Failover Enabled
- HTTPS Proxy Content Inspection with Fireware v121
- Gateway AV Engine Upgrade with Fireware v120
- XTMv Upgrade Notes
-
- Upgrade to Fireware v1213
-
- Back Up Your WatchGuard Servers
- Upgrade to Fireware v1213 from Web UI
- Upgrade to Fireware v1213 from WSMPolicy Manager
-
- Update AP Devices
-
- Important Upgrade Steps
- AP Firmware Upgrade
-
- Upgrade your FireCluster to Fireware v1213
- Downgrade Instructions
-
- Downgrade from WSM v1213 to earlier WSM v12x or v11x
- Downgrade from Fireware v1213 to earlier Fireware v12x or v11x
- Downgrade Restrictions
-
- Enhancements and Resolved Issues in Fireware 1213
-
- General
- Integrations
- Networking
- Centralized Management
- VPN
- Proxies and Services
- Wireless
-
- Known Issues and Limitations
- Using the CLI
- Technical Assistance
-