Fireware XTM v11.6.3 Release Notes

Fireware XTM v11.6.3 Release Notes
Fireware XTM v11.6.3 Release Notes
Supported Devices
XTMv, XTM 2, 3, 5, and 8 Series
XTM 1050, XTM 2050
358414 for the XTM 2050 (re-released 12/19/2012)
Fireware XTM OS Build
357868 for all other XTM models
WatchGuard System Manager
Build
358385 (re-released 12/19/2012)
Revision Date
31 December 2012
Introduction
Note Fireware XTM v11.6.3 was originally released on December 12, 2012. On December
19, 2012, we released an update to the Fireware XTM software for the XTM 2050, and
an update to WatchGuard System Manager (WSM) for all platforms to resolve an issue
related to the XTM 2050. If you have already downloaded WSM v11.6.3, you do not
need to download new WSM software unless you manage an XTM 2050 device.
WatchGuard is pleased to announce the release of Fireware XTM v11.6.3 and WatchGuard System Manager
v11.6.3.You can install Fireware XTM OS v11.6.3 on any WatchGuard XTM device, including 2 Series, 3
Series, 5 Series, 8 Series, XTM 1050 and 2050 devices, and with any edition of XTMv. This release introduces
support for two new features:
RapidDeploy
With RapidDeploy, network administrators of distributed enterprises can activate and deploy XTM devices in
remote locations without the need to preconfigure the devices before they are shipped out -- saving time and
money. You can find more information about RapidDeploy in the v11.6.3 Help, including a link to the new
WatchGuard Deployment Center web UI you can use to activate, deploy, and track your XTM RapidDeploy
devices.
Automatic Feature Key Synchronization
When automatic feature key synchronization is enabled, any XTM device can automatically download the
latest feature key from the WatchGuard web site when any feature in the feature key is expired or about to
expire. It is not enabled by default.
In addition to these new features, this release includes a large number of bug fixes. You can find a description
of these bug fixes in the Resolved Issues section.
For more information about the feature enhancements included in Fireware XTM v11.6.3, you can:
Before You Begin
l
Review the PowerPoint overview: What's New in Fireware XTM v11.6.3.
l
Review the help topic What's New in This Release to find links directly to the product documentation for
these new features.
Before You Begin
Before you install this release, make sure that you have:
l
l
l
A WatchGuard XTM 2 Series, 3 Series, 5 Series, 8 Series, XTM 1050, or XTM 2050 device, or XTMv
(any edition).
The required hardware and software components as shown below. If you use WatchGuard System
Manager (WSM), make sure your WSM version is equal to or higher than the version of Fireware XTM
OS installed on your XTM device and the version of WSM installed on your Management Server.
Feature key for your XTM device — If you upgrade your XTM device from an earlier version of Fireware
XTM OS, you can use your existing feature key. If you use XTMv, your feature key must be generated
with the serial number you received when you purchased XTMv.
Note that you can install and use WatchGuard System Manager v11.6.3 and all WSM server components with
devices running earlier versions of Fireware XTM v11. In this case, we recommend that you use the product
documentation that matches your Fireware XTM OS version.
If you have a new XTM physical device, make sure you use the instructions in the XTM Quick Start Guide that
shipped with your device. If this is a new XTMv installation, make sure you carefully review the XTMv Setup
Guide for important installation and setup instructions.
Documentation for this product is available on the WatchGuard web site at
www.watchguard.com/help/documentation.
Localization
This release includes localized Fireware XTM v11.6.1 management user interfaces (WSM application suite and
Web UI) and product help. Content new to the Fireware XTM and WSM v11.6.3 release remains in English.
Supported languages are:
l
Chinese (Simplified, PRC)
l
French (France)
l
Japanese
l
Spanish (Latin American)
Note In addition to these languages, we offer localized Web UI support for Korean and
Traditional Chinese. Only the Web UI itself has been localized. WSM, and all help files
and user documentation, remain in English for these two languages.
Note that most data input must still be made using standard ASCII characters. You can use non-ASCII
characters in some areas of the UI, including:
2
l
Proxy deny message
l
Wireless hotspot title, terms and conditions, and message
l
WatchGuard Server Center users, groups, and role names
WatchGuard Technologies, Inc.
Localization
Any data returned from the device operating system (e.g. log data) is displayed in English only. Additionally, all
items in the Web UI System Status menu and any software components provided by third-party companies
remain in English.
Fireware XTM Web UI
The Web UI will launch in the language you have set in your web browser by default. The name of the currently
selected language is shown at the top of each page. To change to a different language, click the language name
that appears. A drop-down list of languages appears and you can select the language you want to use.
WatchGuard System Manager
When you install WSM, you can choose what language packs you want to install. The language displayed in
WSM will match the language you select in your Microsoft Windows environment. For example, if you use
Windows XP and want to use WSM in Japanese, go to Control Panel > Regional and Language Options and
select Japanese from the language list.
Log and Report Manager, CA Manager, Quarantine Web UI, and Wireless Hotspot
These web pages automatically display in whatever language preference you have set in your web browser.
Release Notes
3
Fireware XTM and WSM v11.6.3 Operating System Compatibility
Fireware XTM and WSM v11.6.3 Operating System
Compatibility
Revised June 2012
WSM/
FirewareXTMComponent
Microsoft Microsoft Microsoft Microsoft
Microsoft
Windows Windows Windows Windows MacOSX Android
Windows
Vista
7
Server
Server
v10.5,v10.6, 4.x and
XPSP2
(32-bit&
(32-bit&
2008&
& v10.7
higher
2003
(32-bit)
64-bit)
64-bit)
2008R2*
(32-bit)
WatchGuard System
Manager Application
Fireware XTM Web UI
Supported Browsers:
IE 7 and 8, Firefox 3.x & above
Log and Report Manager
Web UI
Supported browsers: Firefox
3.5 & above, IE8 & above,
Safari 5.0 & above, Chrome 10
& above. Javascript required.
WatchGuard Servers
Single Sign-On Agent
Software
(Includes Event Log
Monitor)
Single Sign-On Client
Software
Terminal Services Agent
Software**
Mobile VPN with IPSec
Client Software
***
Native
(Cisco)
IPSec
client is
supported
Mobile VPN with SSL
Client Software
* Microsoft Windows Server 2008 32-bit and 64-bit support; Windows Server 2008 R2 64-bit support.
* * Terminal Services support with manual or Single Sign-On authentication operates in a Microsoft Terminal
Services or Citrix XenApp 4.5, 5.0, 6.0 and 6.5 environment.
*** Microsoft Windows Server 2003 SP2 required.
4
WatchGuard Technologies, Inc.
Fireware XTM and WSM v11.6.3 Operating System Compatibility
Authentication Support
This table gives you a quick view of the types of authentication servers supported by key features of Fireware
XTM. Using an authentication server gives you the ability to configure user and group-based firewall and VPN
policies in your XTM device configuration. With each type of third-party authentication server supported, you
can specify a backup server IP address for failover.
— Fully supported by WatchGuard
— Not yet supported, but tested with success by WatchGuard customers
Firebox
Active
Directory1
LDAP
RADIUS SecurID
2
Mobile VPN with IPSec/Shrew Soft
2
3
(Firebox-DB)
Local
Authentication
–
Mobile VPN with IPSec for iPhone/iPad iOS
and Mac OS X
Mobile VPN with IPSec for Android devices
–
Mobile VPN with SSL for Windows
4
4
Mobile VPN with SSL for Mac
Mobile VPN with PPTP
5
–
–
N/A
Built-in Authentication Web Page on Port
4100
Windows Single Sign-On Support
(with or without client software)
–
–
–
–
–
–
–
–
Terminal Services Manual Authentication
Terminal Services Authentication with
Single Sign-On
6
Citrix Manual Authentication
1. Active Directory support includes both single domain and multi-domain support, unless otherwise noted.
2. RADIUS and SecurID support includes support for both one-time passphrases and challenge/response
authentication integrated with RADIUS. In many cases, SecurID can also be used with other RADIUS
implementations, including Vasco.
3. The Shrew Soft client does not support two-factor authentication.
4. Fireware XTM supports RADIUS Filter ID 11 for group authentication.
5. PIN + Tokencode mode is supported. Next Tokencode mode and SMS OneTimePasswords are not
supported.
6. Only single domain Active Directory configurations are supported.
Release Notes
5
Fireware XTM and WSM v11.6.3 Operating System Compatibility
7. For information about the supported Operating System compatibility for the WatchGuard TO Agent and
SSO Agent, see the current Fireware XTM and WSM Operating System Compatibility table.
XTMv System Requirements
To install an XTMv virtual device, you must have a VMware ESXi 4.1 or 5.0 host installed on any server
hardware supported by the ESXi version you use. You must also install the VMware vSphere Client 4.1 or 5.0
on a supported Windows computer. If you prefer, you can use vCenter Server instead of the vSphere client.
The hardware requirements for XTMv are the same as the hardware requirements for VMware ESXi. For
information about VMware hardware compatibility, see the VMware Compatibility Guide at
http://www.vmware.com/resources/compatibility/search.php.
Each XTMv virtual machine requires 3 GB of disk space.
Recommended Resource Allocation Settings
Small Office Medium Office Large Office Datacenter
6
Virtual CPUs 1
2
4
8 or more
Memory
2 GB
4 GB
4 GB or more
1 GB
WatchGuard Technologies, Inc.
Downloading Software
Downloading Software
1. Log in to the WatchGuard Portal and select the Articles & Software tab.
2. From the Search section, clear the Articles and Known Issues check boxes and search for available
Software Downloads. Select the XTM device for which you want to download software.
There are several software files available for download. See the descriptions below so you know what software
packages you will need for your upgrade.
WatchGuard System Manager
All users can now download the WatchGuard System Manager software. With this software package you can
install WSM and the WatchGuard Server Center software:
WSM11.6.3s.exe — Use this file to upgrade WatchGuard System Manager from v11.x to WSM v11.6.3.
Fireware XTM OS
Select the correct Fireware XTM OS image for your XTM device. Use the .exe file if you want to install or
upgrade the OS using WSM. Use the .zip file if you want to install or upgrade the OS using the Fireware XTM
Web UI. Use the .ova file to deploy a new XTMv device.
If you have….
Select from these Fireware XTM OS packages
XTM 2050
XTM_OS_XTM2050_11.6.3.exe
xtm_xtm2050_11.6.3.zip
XTM 1050
XTM_OS_XTM1050_11.6.3.exe
xtm_xtm1050_11.6.3.zip
XTM 8 Series
XTM_OS_XTM8_11.6.3.exe
xtm_xtm8_11.6.3.zip
XTM 5 Series
XTM_OS_XTM5_11.6.3.exe
xtm_xtm5_11.6.3.zip
XTM 330
XTM_OS_XTM330_11.6.3.exe
xtm_xtm330_11.6.3.zip
XTM 33
XTM_OS_XTM33_11.6.3.exe
xtm_xtm33_11.6.3.zip
XTM 2 Series
Models
21, 22, 23
XTM_OS_XTM2_11.6.3.exe
xtm_xtm2_11.6.3.zip
XTM 2 Series
Models 25, 26
XTM_OS_XTM2A6_11.6.3.exe
xtm_xtm2a6_11.6.3.zip
XTMv
All editions
xtmv_11.6.3.ova
xtmv_11.6.3.exe
xtmv_11.6.3.zip
Release Notes
7
Downloading Software
Single Sign-On Software
There are two files available for download if you use Single Sign-On.
l
WG-Authentication-Gateway_11_6.exe (SSO Agent software - required for Single Sign-On and
l
includes optional Event Log Monitor for clientless SSO)
WG-Authentication-Client_11_6.ms i (SSO Client software - optional)
For information about how to install and set up Single Sign-On, see the product documentation.
Terminal Services Authentication Software
l
TO_AGENT_32_11_6.exe (32-bit support)
l
TO_AGENT_64_11_6.exe (64-bit support)
Mobile VPN with SSL Client for Windows and Mac
There are two files available for download if you use Mobile VPN with SSL:
l
WG-MVPN-SSL_11_6.exe (Client software for Windows)
l
WG-MVPN-SSL_11_6.dmg (Client software for Mac)
Mobile VPN with IPSec client for Windows
You can download the Shrew Soft VPN client for Windows from our web site. For more information about the
Shrew Soft VPN client, see the help or visit the Shrew Soft, Inc. web site.
8
WatchGuard Technologies, Inc.
Upgrade from Fireware XTM v11.x to v11.6.3
Upgrade from Fireware XTM v11.x to v11.6.3
Before you upgrade from Fireware XTM v11.x to Fireware XTM v11.6.3, download and save the Fireware XTM
OS file that matches the WatchGuard device you want to upgrade. You can find all available software on the
WatchGuard Portal, Articles & Software tab. You can use Policy Manager or the Web UI to complete the
upgrade procedure. We strongly recommend that you back up your device configuration and your WatchGuard
Management Server configuration before you upgrade. It is not possible to downgrade without these backup
files.
If you use WatchGuard System Manager (WSM), make sure your WSM version is equal to or higher than the
version of Fireware XTM OS installed on your XTM device and the version of WSM installed on your
Management Server.
Note If you are upgrading to WSM v11.6.3 from WSM v11.4.x or earlier, it is important to
back up your Log and Report Server data using the procedure described in the
Knowledge Base article Log and Report Server Changes in XTM v11.5.1. This is
necessary because the Log and Report Server database structure changed in WSM
v11.5.1. When you upgrade to WSM v11.5.1 or higher for the first time, the timestamps
of existing log and report data will be converted to UTC from the local time zone. This
Knowledge Base article gives you details on this upgrade, and important information
about the Log and Report Manager (also new in WSM v11.5.1).
Back up your WatchGuard Management Server Configuration
From the computer where you installed the Management Server:
1. From WatchGuard Server Center, select Backup/Restore Management Server.
The WatchGuard Server Center Backup/Restore Wizard starts.
2. Click Next.
The Select an action screen appears.
3. Select Back up settings.
4. Click Next.
The Specify a backup file screen appears.
5. 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 configuration.
6. Click Next.
The WatchGuard Server Center Backup/Restore Wizard is complete screen appears.
7. Click Finish to exit the wizard.
Upgrade to Fireware XTM v11.6.3 from Web UI
1. Go to System > Backup Image or use the USB Backup feature to back up your current configuration file.
2. On your management computer, launch the OS software file you downloaded from the WatchGuard
Software Downloads Center.
If you use the Windows-based installer, this installation extracts an upgrade file called [xtm series]_
[product code].sysa-dl l to the default location of C:\Program Files(x86)\Common
files\WatchGuard\resources\FirewareXTM\11.6.3\[model] or [model][product_code].
3. Connect to your XTM device with the Web UI and select System > Upgrade OS.
4. Browse to the location of the [xtm series]_[product code].sysa-dl from Step 2 and click Upgrade.
Release Notes
9
Upgrade your FireCluster to Fireware XTM v11.6.3
Upgrade to Fireware XTM v11.6.3 from WSM/Policy Manager v11.x
1. Select File > Backup or use the USB Backup feature to back up your current configuration file.
2. On your management computer, launch the OS executable file you downloaded from the WatchGuard
Portal. This installation extracts an upgrade file called [xtm series]_[product code].sysa-dl l to the
default location of C:\Program Files(x86)\Common files\WatchGuard\resources\FirewareXTM\11.6.3\
[model] or [model][product_code].
3. Install and open WatchGuard System Manager v11.6.3. Connect to your XTM device and launch Policy
Manager.
4. From Policy Manager, select File > Upgrade. When prompted, browse to and select the [xtm series]_
[product code].sysa-dl file from Step 2.
General Information for WatchGuard Server Software Upgrades
It is not necessary to uninstall your previous v11.x server or client software when you update from v11.0.1 or
higher to WSM v11.6.x. You can install the v11.6.x server and client software on top of your existing installation
to upgrade your WatchGuard software components.
Upgrade your FireCluster to Fireware XTM v11.6.3
There are two methods to upgrade Fireware XTM OS on your FireCluster. The method you use depends on the
version of Fireware XTM you currently use.
Upgrade a FireCluster from Fireware XTM v11.4.x or v11.5.x
Use these steps to upgrade a FireCluster from Fireware XTM v11.4.x or v11.5.x to Fireware XTM v11.6.x:
1.
2.
3.
4.
5.
Open the cluster configuration file in Policy Manager
Select File > Upgrade.
Type the configuration passphrase.
Type or select the location of the upgrade file.
To create a backup image, select Yes.
A list of the cluster members appears.
6. Select the check box for each device you want to upgrade.
A message appears when the upgrade for each device is complete.
When the upgrade is complete, each cluster member reboots and rejoins the cluster. If you upgrade both
devices in the cluster at the same time, the devices are upgraded one at a time. This is to make sure there is
not an interruption in network access at the time of the upgrade.
Policy Manager upgrades the backup member first and then waits for it to reboot and rejoin the cluster as a
backup. Then Policy Manager upgrades the master. Note that the master’s role will not change until it reboots
to complete the upgrade process. At that time the backup takes over as the master.
To perform the upgrade from a remote location, make sure the FireCluster interface for management IP address
is configured on the external interface, and that the management IP addresses are public and routable. For
more information, see About the Interface for Management IP Address.
10
WatchGuard Technologies, Inc.
Downgrade Instructions
Upgrade a FireCluster from Fireware XTM v11.3.x
To upgrade a FireCluster from Fireware XTM v11.3.x to Fireware XTM v11.6.x, you must perform a manual
upgrade. For manual upgrade steps, see the Knowledge Base article Upgrade Fireware XTM OS for a
FireCluster.
Downgrade Instructions
Downgrade from WSM v11.6.x to WSM v11.x
If you want to revert from v11.6.x to an earlier version of WSM, you must uninstall WSM v11.6.x. When you
uninstall, choose Yes when the uninstaller asks if you want to delete server configuration and data files. After
the server configuration and data files are deleted, you must restore the data and server configuration files you
backed up before you upgraded to WSM v11.6.x.
Next, install the same version of WSM that you used before you upgraded to WSM v11.6.x. The installer
should detect your existing server configuration and try to restart your servers from the Finish dialog box. If you
use a WatchGuard Management Server, use WatchGuard Server Center to restore the backup Management
Server configuration you created before you first upgraded to WSM v11.6.x. Verify that all WatchGuard servers
are running.
Downgrade from Fireware XTM v11.6.x to Fireware XTM v11.x
Note You cannot downgrade an XTM 2050, an XTM 330, or an XTM 33 device to a version of
Fireware XTM OS lower than v11.5.1. You cannot downgrade an XTM 5 Series model
515, 525, 535 or 545 to a version of Fireware XTM OS lower than v11.6.1. You cannot
downgrade XTMv to a version of Fireware XTM OS lower than v11.5.4.
If you want to downgrade from Fireware XTM v11.6.x to an earlier version of Fireware XTM, you either:
l
l
Restore the full backup image you created when you upgraded to Fireware XTM v11.6.x to complete the
downgrade; or
Use the USB backup file you created before the upgrade as your auto-restore image, and then boot into
recovery mode with the USB drive plugged in to your device. This is not an option for XTMv users.
To start a WatchGuard XTM 330, 5 Series, 8 Series, XTM 1050, or XTM 2050 device in recovery mode:
1. Power off the XTM device.
2. Press the up arrow on the device front panel while you turn the power on.
3. Keep the button depressed until "Recovery Mode starting" appears on the LCD display.
To start a WatchGuard XTM 2 Series or XTM 33 device in recovery mode:
1. Disconnect the power.
2. Press and hold the Reset button on the back while you connect the power to the device.
3. Keep the button depressed until the Attn light on the front turns solid orange.
Release Notes
11
Resolved Issues
Resolved Issues
The Fireware XTM v11.6.3 release resolves a number of problems found in earlier Fireware XTM v11.x
releases.
General
l
All XTM 5 Series devices now correctly display their device model in LCD display and Firebox System
Manager. [69377]
This release resolves an issue that caused some XTM 8 Series devices to lock up or reboot
unexpectedly. [69302]
A problem that caused some XTM 1050 devices to crash in some customer environments has been
fixed. [66670]
Fiber modules for XTM 1050 devices now operate correctly. [70118]
l
A problem was fixed that caused some XTM devices to crash after a configuration save. [65288]
l
Newly added or expired blocked sites no longer cause the XTM device to crash. [67994]
l
A cross-site scripting vulnerability present in the authentication page (port 4100) has been addressed in
this release. [68127]
The ATTN light on XTM 2 Series and XTM 33 devices now operates correctly during the reset process.
l
l
l
l
[67165]
l
Several XTM device crash issues have been resolved in this release. [67866, 69050, 66809, 66032]
l
Changed device passphrases are no longer written to the support.tgz file. [69764]
l
It is now possible to schedule an automated update of your device feature key. [66997]
WatchGuard System Manager
l
A Management Server login will no longer fail with the error: "Error Code: Error(1102) no lock available".
[68491]
l
l
l
When a Management Server login fails, you now see an error message to specify the reason for the
failure. [66866]
Log files for WatchGuard server are now automatically archived to prevent the files from growing too
large. [34363, 67521]
HostWatch no longer fails to display connections because of invalid XML characters. [66785]
Firebox System Manager
l
This release resolves an issue that caused Traffic Monitor to fail to display any data. [66975]
Centralized Management
l
The Management Server no longer fails to apply a v11.3.x template to fully managed v11.3.x devices.
[68447]
l
You can no longer build an (incorrect) v11.4.x formatted configuration file for Firebox X e-Series devices.
[68646]
12
l
Scheduled Tasks that are configured for the same day now process correctly. [68329]
l
Devices imported to the Management Server now display correctly. [69539]
WatchGuard Technologies, Inc.
Resolved Issues
Logging & Reporting
l
The unnecessary log message "block_dump: Select timed out" has been removed. [66635]
l
The unnecessary log message "miiGetLinkStatus" no longer shows when a network bridge is enabled.
[41811]
l
The web service file "LogService.wsdl" is now accessible for Eclipse setup. [69869]
l
Reports generated with UTF-8 encoding no longer contain corrupted characters. [66584]
Proxies and Security Services
l
This release resolves an issue with IPS and the HTTP proxy that caused NAT exhaustion in some
customer environments. [66246]
A problem that caused XTM device instability when the SIP ALG was in use has been resolved in this
release. [68312]
A problem that caused ActiveFTP to fail in some customer environments has been resolved. [65848]
l
This issue resolves an issue that caused some XTM devices to crash during heavy mail traffic. [66428]
l
XTM devices no longer try to update Gateway AV and IPS signatures when these features are not
licensed. [66415]
l
l
Authentication
l
SSO exceptions added as an IP Range now operate correctly. [68986]
l
SSO exceptions no longer incorrectly trigger when the last octet of an IP address matches a configured
exception. [68344]
Networking l
A problem that caused Policy-Based Routing to fail when the interface was not down has been resolved.
[67116]
l
This release resolves an issue that could cause an interface to fail. [68554]
l
A problems that caused some XTM devices to periodically fail to pass network traffic has been fixed.
[65179]
l
Static routes no longer fail when multi-WAN and PPPoE are both enabled. [68090]
l
l
An interfaced configured to use PPPoE no longer waits for a multi-WAN failover to occur before it
requests a new IP address. [68232]
This release resolves an issue that caused outbound traffic to fail after a multi-WAN failover. [68183]
l
Multi-WAN now works correctly on XTM 2050 devices configured with ETH16-19 as external interfaces.
[68405]
FireCluster
l
This release resolves some memory management issues that caused FireCluster instability. [68026]
l
This release resolves a crash issue that caused a FireCluster member failover in an active/passive
FireCluster. [66872]
VPN
l
Branch office VPN tunnels no longer fail when a PPPoE interface goes down. [68639]
l
This release resolves several IKE process crashes that caused failure for Mobile VPN with IPSec and
Branch Office VPN. [68118, 69625, 67961, 67881, 68237]
Release Notes
13
Resolved Issues
l
Branch office VPN tunnels no longer fail when a dynamically assigned external IP address on the XTM
device changes. [68163, 68910, 68188]
This release resolves an issue that caused branch office VPN tunnels to fail to pass traffic. [69090, 67819]
l
A large number of active branch office VPN tunnels no longer causes a CPU spike. [68886]
l
l
A memory leak that occurred when a large number of branch office VPN tunnels were active has been
fixed. [66200]
This release resolves an issue that caused branch office VPN tunnels to stop passing traffic. [67921]
l
Branch office VPN tunnel routes configured to use 1-to-1 NAT now operate correctly with Multi-WAN.
l
[67001]
l
This release resolves an issue that caused branch office VPNs to fail after a Fireware XTM OS upgrade.
[68247]
l
The IKE process now remains stable when Mobile VPN with IPSec connections that use the Safenet
client are disconnected. [66772]
XTMv
l
Network connectivity no longer fails after you upgrade the Fireware XTM OS on an XTMv installation.
[69500]
l
14
XTMv appliances with PPPoE configured no longer lose network routes after a reboot. [69492]
WatchGuard Technologies, Inc.
Known Issues and Limitations
Known Issues and Limitations
These are known issues for Fireware XTM v11.6.3 and all management applications. Where available, we
include a way to work around the issue.
General
l
When you connect a USB drive to an XTM device, the device does not automatically save a single
Support Snapshot to the USB drive. [64499]
Workaround
Use the CLI command “usb diagnostic enable” to enable the device to save a diagnostic support
snapshot to the USB drive. For details about this command, see the Command Line Interface
Reference Guide.
l
l
The "Sysb" version displayed in the Firebox System Manager Status Report will show blank for XTM
models 2 ,5, 8, and 1050 that were manufactured prior to the XTM v11.5.1 release.
ICMP flood protection works differently in 11.5.1 than in earlier versions. In v11.5.1 the XTM device
counts the combined total number of ping requests and replies, rather than just the total number of ping
requests. Since the default threshold for ICMP Flood Attack protection did not increase, the flood
protection could trigger more frequently than it did in earlier releases. [63094]
Workaround
In the Default Packet Handling settings, increase the threshold for Drop ICMP Flood Attack from
the default value of 1000 packets/second to a higher number.
l
l
l
When the level of free memory on your XTM device is lower than 20M, saving your XTM device
configuration to the device can cause network disruption. [64474]
The ETH1 interface on the XTM 830F is a fiber-optic port, so you cannot use the WSM Quick Setup
Wizard from a computer with an Ethernet interface. Use a computer with a Fiber NIC, or connect using a
switch with both Fiber and Ethernet interfaces. [59742]
To power off an XTM 5 Series device, you must press and hold the rear power switch for 4–5 seconds.
[42459]
l
l
l
l
l
l
For XTM 5 Series devices, Interface 0 does not support Auto-MDIX and does not automatically sense
cable polarity.
On XTM 2 Series devices, the load average is always displayed at 1 or higher, even when there is no
load on the device. [63898]
An XTM 2 Series device can take up to 5 minutes to reboot.
When you use the Policy Manager > File > Backup or Restore features, the process can take a long
time but does complete successfully. [35450]
You cannot downgrade an XTM 2 Series device from v11.5.1 to v11.4.1 with the Upgrade OS option in
the Web UI. [63323]
Fireware XTM does not support BGP connections through an IPSec VPN tunnel to Amazon Web
Services. VPN tunnels that do not use BGP are supported. [41534]
Release Notes
15
Known Issues and Limitations
l
The XTM Configuration Report does not contain all settings. Settings not included are:
o Secondary interface IP address [66990]
o
Configured QoS settings [66992]
o
Static MAC bindings [66993]
o
IPv6 configuration [66994]
XTMv
l
XTMv does not automatically change the self-signed certificate when its serial number changes. [66668]
Workaround
A new self-signed certificate with the correct serial number is generated if you manually delete the
certificate from Firebox System Manager > View > Certificates and then reboot the XTMv device.
l
If you import the OVA file in VMware Player (which is not officially supported in this release), you must
use the "Enter" key on your keyboard to accept the XTMv End User License Agreement (EULA). The
OK and Cancel buttons at the conclusion of the EULA do not appear in VMware Player.
WatchGuard System Manager
l
If you use Firebox System Manager to ping across a VPN tunnel, you get a message that reads “No
Buffer Space Available.” This is not a memory problem. You see this message if the VPN tunnel is not
established. Make sure the VPN tunnel is up and try again. [59339]
l
WatchGuard System Manager does not display the correct IP address for the default gateway of an
XTM device that has no External interface. [56385]
When you install WatchGuard System Manager or any server software on a computer running Microsoft
Windows XP, compatibility mode should not be enabled even if prompted by Windows, for any of the
WSM applications, including the installer. [56355]
Remote managed Firebox or XTM devices configured in Drop-in Mode may not be able to connect to a
Management Server that is behind a gateway Firebox or XTM device also configured in Drop-in Mode.
l
l
[33056]
l
If you restore a backup image to a managed client device managed by a Management Server, it is
possible that the shared secret becomes out of sync.
Workaround
Connect to the Management Server from WSM. Select the managed device and select Update
Device. Select the radio button Reset server configuration (IP address/ Hostname, shared
secret).
l
During a WSM upgrade, install, or uninstall on a 64-bit Windows systems, any running applications
detected by the WSM installer can be stopped successfully, but the installer may not recognize that
they have been stopped.[39078]
Workaround
Close the installer application. Right-click on the WatchGuard Server Center icon on your
Windows task bar and exit the WatchGuard Server Center. Make sure all detected applications
are stopped and then retry the WSM install or uninstall.
16
WatchGuard Technologies, Inc.
Known Issues and Limitations
l
When you run the WSM v11.3.x or higher installer (either the WSM client component only or any
selected WSM server components) on Microsoft SBS (Small Business Server) 2008 and 2011 on a
computer installed with a 64-bit operating system, you see a Microsoft Windows error "IssProc.x64 has
stopped working". When you close the error dialog box, the installation completes. [57133]
Web UI
l
l
l
l
l
The Fireware XTM Web UI does not support the configuration of some features. These features include:
o
FireCluster
o
Certificate export
o
You cannot turn on or off notification of BOVPN events
o
You cannot add or remove static ARP entries to the device ARP table
You cannot get the encrypted Mobile VPN with IPSec end-user configuration profile, known as the .wgx
file. The Web UI generates only a plain-text version of the end-user configuration profile, with file
extension .ini.
You cannot edit the name of a policy, use a custom address in a policy, or use Host Name (DNS lookup)
to add an IP address to a policy.
If you configure a policy in the Web UI with a status of Disabled, then open Policy Manager and make a
change to the same policy, the action assigned to the policy when it denies packets is changed to Send
TCP RST. [34118]
You cannot create read-only Mobile VPN with IPSec configuration files with the Web UI. [39176]
Command Line Interface (CLI)
l
The CLI does not support the configuration of some features:
o
You cannot add or edit a proxy action.
You cannot get the encrypted Mobile VPN with IPSec end-user configuration profile, known as the
.wgx file. The CLI generates only a plain-text version of the end-user configuration profile, with file
extension .ini.
The CLI performs minimal input validation for many commands.
o
l
l
For the XTM 2050, the output of the CLI command “show interface” does not clearly indicate the
interface number you use in the CLI to configure an interface. The “show interface” CLI command shows
the interface number as the interface label on the front of the device (A0, A2 … A7; B0, B1 … B7; C0,
C1) followed by a dash, and then the consecutive interface number (0 – 17), for all interfaces. [64147]
Workaround
Use the consecutive interface number that appears after the dash as the interface number to
configure the interface. For the B1-9 interfaces, the interface number in the CLI command should be
in the range 8-15. For the C0-1 interfaces, the interface number in the CLI command should be 16-17.
Proxies
l
l
The Policy Manager and Web UI do not provide any warning that the WebBlocker Override may not work
for HTTPS. [67208]
HTTPS DPI (Deep Packet Inspection) does not work for users who use IE 9.0 with TLS 1.1 and 1.2
enabled, but TLS 1.0 and SSL 3.0 not enabled. [65707]
Workaround
Use a different browser, or enable TLS 1.0 and SSL 3.0 in your IE 9.0 configuration.
Release Notes
17
Known Issues and Limitations
l
l
l
l
The XTM device can store only one HTTPS Proxy Server certificate and can protect only one HTTPS
web site at a time. [41131]
WhenanXTMdeviceis underhighload,someproxy connections may notterminatecorrectly. [61925,62503]
The ability to use an HTTP caching proxy server is not available in conjunction with the TCP-UDP
Proxy. [44260]
You cannot make a SIP-based call from Polycom PVX softphone behind a Firebox to a Polycom PVX on
the external network. [38567]
Workaround
You can use the H.323 protocol instead of SIP.
l
When you try to stream YouTube videos from an Apple device running iOS, you may see this error
message: "The server is not correctly configured."
Workaround
1. Edit your HTTP proxy policy.
2. Click View/Edit proxy.
3. Select the Allow range requests through unmodified check box.
4. Save this change to your XTM device.
l
The SIP-ALG does not send the Contact header correctly when the Contact header contains a domain
name. It only sends an empty string of: Contact: < >. If the Contact header contains an IP address, the
SIP-ALG sends the Contact header correctly: Contact: <sip:10.1.1.2:5060>. [59622]
Workaround
Configure the PBX to send the Contact header with an IP address, not a domain name.
Security Subscriptions
l
l
l
l
l
Some IPS signature information, such as the CVE number, is not available in Firebox System Manager.
We provide search capabilities and CVE information for IPS signatures on a web security portal for IPS
on the WatchGuard web site, which you can access at
http://www.watchguard.com/SecurityPortal/ThreatDB.aspx
Skype detection blocks only new Skype sessions. If a user is already logged in to Skype and a Skype
session is already started when Application Control is enabled, Application Control may not detect the
activity.
For XTM 2 Series devices only, Application Control is temporarily disabled during an upgrade, back up,
or restore. When the operation is complete, Application Control starts to work again.
It is not possible to assign a role for Application Control management from the WatchGuard System
Manager role-based administration feature. [59204]
You cannot use a WebBlocker Server through a branch office VPN tunnel. [56319]
Networking
l
l
18
If you manually created dynamic routing policies in Fireware XTM v11.5.x or earlier, the To and From
lists in these policies are cleared when you upgrade to v11.6. If dynamic routing is enabled, new policies
will be created automatically when you upgrade. [67721]
Policy Checker does not work when your XTM device is configured in Bridge mode. [66855]
WatchGuard Technologies, Inc.
Known Issues and Limitations
l
An apostrophe in a DHCP reservation name causes the DHCP reservation to fail. [65529]
l
You cannot configure traffic management actions or use QoS marking on VLANs. [56971, 42093]
l
You cannot bridge a wireless interface to a VLAN interface. [41977]
l
The Web Setup Wizard can fail if your computer is directly connected to an XTM 2 Series device as a
DHCP client when you start the Web Setup Wizard. This can occur because the computer cannot get
an IP address quickly enough after the device reboots during the wizard. [42550]
Workaround
1. If your computer is directly connected to the XTM 2 Series device during the Web Setup
Wizard, use a static IP address on your computer.
2. Use a switch or hub between your computer and the XTM 2 Series device when you run the
Web Setup Wizard.
l
l
l
l
l
l
l
l
l
l
l
l
When a secondary network is configured for an XTM 2 Series device configured in Drop-In Mode, it can
sometimes take a few minutes for computers that connect to the secondary network to appear in the
ARP list of the XTM 2 Series. [42731]
You must make sure that any disabled network interfaces do not have the same IP address as any
active network interface or routing problems can occur. [37807]
If you enable the MAC/IP binding with the Only allow traffic sent from or to these MAC/IP addresses
check box, but do not add any entries to the table, the MAC/IP binding feature does not become active.
This is to help make sure administrators do not accidentally block themselves from their own XTM
device. [36934]
Any network interfaces that are part of a bridge configuration disconnect and re-connect automatically
when you save a configuration from a computer on the bridge network that includes configuration
changes to a network interface. [39474]
When you change the IP address of a VLAN configured on an external interface from static to PPPoE
and the Firebox cannot get a PPPoE address, Firebox System Manager and the Web UI may continue
to show the previously used static IP address. [39374]
When you configure your XTM device with a Mixed Routing Mode configuration, any bridged interfaces
show their interface and default gateway IP address as 0.0.0.0 in the Web UI. [39389]
When you configure your XTM device in Bridge Mode, the LCD display on your XTM device shows the
IP address of the bridged interfaces as 0.0.0.0. [39324]
When you configure your XTM device in Bridge Mode, the HTTP redirect feature is configurable from the
user interface but does not work in this release. [38870]
Static MAC/IP address binding does not work when your XTM device is configured in Bridge mode. [36900
When you change your configuration mode from Mixed Routing to Bridge or from Bridge to Mixed
Routing, the CLI and Web UI may continue to show the previous configuration mode. [38896]
The dynamic routing of RIPv1 does not work. [40880]
When an IP address is added to the Temporary Blocked Site list by the administrator through the Firebox
System Manager > Blocked Sites tab, the expiration time is constantly reset when traffic is received
from the IP address. [42089]
Multi-WAN
l
l
The multi-WAN sticky connection does not work if your device is configured to use the multi-WAN
Routing Table mode. [62950]
When you enable the multi-WAN Immediate Failback option for WAN failover, some traffic may fail over
gradually. [42363]
Release Notes
19
Known Issues and Limitations
Wireless
l
The 5GHz Wireless band does not work when you use channels 36, 40, 149 or 165. [65559]
Authentication
l
Citrix 4.5/5/0 servers installed in VMware do not work with Terminal Server Single Sign-On. [66156]
Workaround
This feature works with Citrix 6.0 and 6.5 servers installed in VMware.
l
Clientless SSO is not supported on a TLS-Enabled Active Directory environment.
l
If you use Terminal Services authentication, no authentication verification is done against traffic of any
protocol that is not TCP or UDP. This includes DNS, NetBIOS, and ICMP traffic.
It is not possible to use the Automatically redirect users to the authentication page authentication option
together with Terminal Services authentication.
To enable your XTM device to correctly process system-related traffic from your Terminal or Citrix
server, the Terminal Services Agent uses a special user account named Backend-Service. Because of
this, you may need to add policies to allow traffic from this user account through your XTM device. You
can learn more about how Backend-Service operates in the product help system.
For the Authentication Redirect feature to operate correctly, HTTP or HTTPS traffic cannot be allowed
through an outgoing policy based on IP addresses or aliases that contain IP addresses. The
Authentication Redirect feature operates only when policies for port 80 and 443 are configured for user or
user group authentication. [37241]
l
l
l
Centralized Management
l
l
l
l
You cannot create a new user account for role-based administration from the Management Server that
includes unsupported special characters, such as an underscore. You must create the user account
from WatchGuard Server Center. [70464]
There is no option to set up a Traffic Management action in an XTM v11.x Device Configuration
Template. [55732]
If you used Centralized Management with devices subscribed to templates in earlier versions of WSM,
when you upgrade from WSM 11.x to v11.4 or higher, these templates are updated and the devices are
no longer subscribed. Each device retains its template configuration. Existing templates are updated to
use “T_” in their object names (to match the object names in the devices that used to subscribe to them).
After you upgrade, you’ll see the template upgrade that occurs during upgrade in your revision history.
When a XTM template is applied to a managed device, the Management Server creates a new
configuration revision for the device only if the new revision is going to be different from the current
revision. There is also no feedback about why a new configuration revision was not created. [57934]
FireCluster
20
l
You cannot upgrade an active/passive FireCluster over a BOVPN. [39746]
l
The time on the FireCluster backup master can get out of sync with the cluster master, even when NTP
is enabled. [66134]
WatchGuard Technologies, Inc.
Known Issues and Limitations
Workaround
Manually synchronize the time of the backup master. Connect to the cluster, launch Firebox
System Manager, and then select Tools > Synchronize Time. This synchronizes the time on both
cluster members to the time on the management computer.
l
When spanning tree protocol (STP) is enabled on some switches, a FireCluster failover can take 10
seconds or longer. [66180]
Workaround
Disable STP on the switch, configure the switch to use rapid STP, or use a different switch.
l
You might need to re-import the HTTPS DPI certificate after you upgrade the Fireware XTM OS for a
FireCluster. [65280]
l
You cannot use the secondary IP address of an XTM device interface to manage a FireCluster
configured in active/active mode. [64184]
Workaround
Use the primary IP address of an XTM device for all management connections to an active/active
FireCluster.
l
l
Users granted access to monitor FireCluster through role-based administration cannot see the
FireCluster device in Log and Report Manager. [65398]
The FireCluster backup master may become inactive when Mobile VPN with SSL or PPTP is configured
to use an IP address pool that includes the cluster IP address. [63762]
Workaround
Avoid using an IP address pool that conflicts with the cluster IP addresses.
l
l
l
If the Log Server cannot be reached from the management IP addresses, only the current FireCluster
master will be able to connect. This can occur if the Log Server is connected through an External
network, but the management IP addresses are on a Trusted or Optional network. [64482]
If you change the network configuration of a FireCluster from Routed mode to Drop-in mode, and then
change it back to Routed mode, the IP address of the cluster interface is not correctly shown in the
Policy Manager Network > Configuration dialog box. The correct cluster interfaces are shown in the
FireCluster configuration dialog box. [63905]
Gateway AV updates in a system that is low on memory may result in a FireCluster failover [62222]
Workaround
Reduce the frequency that the system checks for Gateway AV updates to minimize the chance of
this occurring.
l
If a monitored link fails on both FireCluster members, the non-master member is switched into passive
mode and consequently does not process any traffic. A multi-WAN failover caused by a failed
connection to a link monitor host does not trigger FireCluster failover. FireCluster failover occurs only
when the physical interface is down or does not respond. Release Notes
21
Known Issues and Limitations
l
Each XTM device has a set of default IP addresses assigned to the device interfaces in a range starting
with 10.0.0.1. The highest default IP address depends on the number of interfaces. If you set the IP
address of the Primary or Backup cluster interface to one of the default IP addresses, both devices
restart, and the backup master becomes inactive. [57663]
Workaround
Do not use any of the default IP addresses as the Primary or Backup cluster interface IP address.
l
l
l
l
l
l
l
When you have an active/active FireCluster and use the WebBlocker Override feature, you may be
prompted to enter your override password twice. [39263]
Every network interface enabled in a FireCluster is automatically monitored by FireCluster. You must
make sure that all enabled interfaces are physically connected to a network device.
If you use HP ProCurve switches, you may not be able to configure your FireCluster in active/active
mode because these switches may not support the addition of static ARP entries. [41396]
If you use the Mobile VPN with IPSec client from the same network as the external network address
configured on your FireCluster, some traffic may not go through the VPN tunnel. [38672]
Mobile VPN with PPTP users do not appear in Firebox System Manager when you are connected to a
passive FireCluster member. PPTP is only connected to the active Firebox when using an
active/passive FireCluster. [36467]
It is not possible to use a VLAN interface IP address for a FireCluster management IP address. [45159]
To perform a manual upgrade of a FireCluster from v11.3.x to v11.5.1, the management computer must
be on the same network as the FireCluster management IP addresses. [63278]
Logging and Reporting
l
When you change the log level for your WatchGuard Log Server and click Apply, the change does not
take effect. [60088]
Workaround
1. In WatchGuard Server Center, on the Log Server Logging tab, change the log level for log
messages from the Log Server and click Apply.
2. In the Servers tree, right-click Log Server and select Stop Server. In the confirmation
message, select Yes.
3. Right-click Log Server again and select Start Server.
l
The Denied Packets Summary report is not yet available in the Log and Report Manager. [63192]
l
The PDF output of the Web Activity Trend report does not include time labels on the x-axis when viewed
in Log and Report Manager. Date and time information is included in the table below the report. [64162]
When you upgrade from Fireware XTM v11.4.x to v11.5.1, reports generated near the time of the
upgrade may not show up in Log and Report Manager. [64325]
l
l
If a daily report schedule name includes a colon or certain other characters (for example: "1:35"), the
system returns an error. [63427]
Workaround
Make sure that your report schedule names use only characters that are valid in Windows file
names. You can find valid characters in articles such as http://msdn.microsoft.com/enus/library/windows/desktop/aa365247%28v=vs.85%29.aspx .
22
WatchGuard Technologies, Inc.
Known Issues and Limitations
l
Log collector will crash when it reaches the 2GB virtual size limit on 32-bit Windows systems. [64249]
l
There are two sorting issues in the new Log and Report Manager. When you sort by Destination, the
field sorts by IP address and not the destination host name (if available). When you sort by Disposition,
some items in the "deny" state do not sort accurately within groups. [62879]
Any configured daily or weekly “Archived Reports” you have in your v11.3 configuration are
automatically converted to scheduled reports after you upgrade to WSM v11.4 or higher.
l
Mobile VPN
l
l
You cannot generate a Mobile VPN with IPSec configuration file when the group name contains the
characters the asterisk or period characters(*, .). [66815]
If you set the diagnostic log level for Mobile VPN with SSL traffic to “debug” level, log messages stop
displaying in Firebox System Manager > Traffic Manager. [65165]
Workaround
Set the diagnostic log level for Mobile VPN with SSL to any log level less granular than “debug”.
l
l
If you add a new feature key that adds Mobile VPN with SSL licenses for your XTM device, you must
reboot your XTM device to enable the additional Mobile VPN with SSL users. [65620]
When you connect a Mobile VPN wth SSL v11.5.1 client for the first time to an XTM device upgraded to
v11.5.2, the client upgrade sometimes fails. [65635]
Workaround
Install the Mobile VPN with SSL client manually.
l
l
l
l
l
l
l
l
l
You cannot establish a Mobile VPN with SSL connection from a Windows-based computer when the
Windows system account is Chinese. [58208]
When you use the built in IPSec client from an iPhone or iPad, the client connection will disconnect
when the connection duration reaches 1 hour and 45 minutes. This is caused by a limitation in the Cisco
client used by iPhone/iPad. You must reconnect the IPSec client to reestablish the VPN tunnel. [63147]
Mobile VPN with PPTP connections from Android mobile devices do not work consistently on 3G mobile
networks. [63451]
Connections from the Mobile VPN with IPSec client can route through the wrong external interface when
the XTM device is configured for multi-WAN in round-robin mode. [64386]
You cannot configure Mobile VPN with SSL to bridge network traffic to a bridged interface. [61844]
Mobile VPN with SSL users cannot connect to some network resources through a branch office VPN
tunnel that terminates on an active/active FireCluster. [61549]
You cannot ping the IP address of the XTM device interface to which a Shrew Soft VPN client
established a VPN tunnel. You can ping computers on that network, but not the interface IP address
itself. [60988]
Shrew Soft VPN client connections can drop if there are multiple cilents connected to an XTM device at
the same time issuing Phase 2 rekeys. [60261]
Phase 1 rekeys initiated by the Shrew Soft VPN client cause the client to be disconnected, if connected
more than 24 hours. In this case, we recommend that you set the rekey on your XTM device to 23 hours
-- one hour shorter than the rekey hard-coded in the Shrew Soft client configuration. This forces the XTM
device to initiate the rekey, and gives the client a notification that the tunnel must be re-established.
[60260, 60259]
Release Notes
23
Known Issues and Limitations
l
A continuous FTP session over a Mobile VPN with IPSec connection could get terminated if an IPSec
rekey occurs during the FTP transfer. [32769]
Workaround
Increase the rekey byte count.
l
The Mobile VPN for SSL Mac client may not be able to connect to an XTM device when the
authentication algorithm is set to SHA 256. [35724]
Branch Office VPN
l
Manual branch office VPN fails when the pre-shared key exceeds 50 characters. [65215]
l
Do not use the same name for both a VPN Gateway and a VPN Tunnel. [66412]
l
When you configure your XTM device in multi-WAN mode, you must select which interfaces to include
in your multi-WAN configuration. If there are any interfaces that you choose not to include in your multiWAN configuration (i.e. you clear the check box for that interface), the system does not create a route
for that network. This can cause a problem if you have a branch office VPN configured to include that
same interface. In this case, the VPN tunnel can fail to negotiate with its remote peer. [57153]
Workaround
If you use multi-WAN and have problems with your branch office VPN tunnels failing to negotiate
with their remote peers, you must open your multi-WAN configuration and select Configure
adjacent to your chosen multi-WAN configuration mode. Make sure that the appropriate interfaces
are included in your multi-WAN configuration.
l
l
l
A branch office VPN tunnel does not pass traffic if an inbound static NAT policy that includes IP 50 and
IP 51 protocols exists for the external IP address of the XTM device. [41822]
Managed branch office VPN tunnels cannot be established if the CRL distribution point (for example, the
WatchGuard Management Server or a third-party CRL distribution site you use) is offline. [55946]
The use of Any in a BOVPN tunnel route is changed in Fireware XTM. If a branch office VPN tunnel
uses Any for the Local part of a tunnel route, Fireware XTM interprets this to mean network 0.0.0.0 and
subnet mask 0.0.0.0 (in slash notation, 0.0.0.0/0). If the remote IPSec peer does not send 0.0.0.0/0 as
its Phase 2 ID, Phase 2 negotiations fail. [40098]
Workaround
Do not use Any for the Local or the Remote part of the tunnel route. Change the Local part of your
tunnel route. Type the IP addresses of computers behind the XTM device that actually participate
in the tunnel routing. Contact the administrator of the remote IPSec peer to determine what that
device uses for the Remote part of its tunnel route (or the Remote part of its Phase 2 ID).
l
If you have a large number of branch office VPN tunnels in your configuration, the tunnels may take a
long time to appear in Policy Manager. [35919]
Workaround
From Policy Manager, select View > Policy Highlighting. Clear the Highlight Firewall
policies based on traffic type check box.
24
WatchGuard Technologies, Inc.
Using the CLI
Using the CLI
The Fireware XTM CLI (Command Line Interface) is fully supported for v11.x releases. For information on how
to start and use the CLI, see the CLI Command Reference Guide. You can download the CLI guide from the
documentation web site at http://www.watchguard.com/help/documentation/xtm.asp. There have been no
updates to the CLI Guide for this release.
Technical Assistance
For technical assistance, contact WatchGuard Technical Support by telephone or log in to the WatchGuard
Portal on the Web at http://www.watchguard.com/support. When you contact Technical Support, you must
supply your registered Product Serial Number or Partner ID.
Phone Number
U.S. End Users
877.232.3531
International End Users
+1 206.613.0456
Authorized WatchGuard Resellers 206.521.8375
Release Notes
25
Technical Assistance
Release Notes
26
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement