Known Issues and Limitations
These are known issues for Fireware XTM v11.3.2 and all management applications. Where available, we include a way to work around the issue.
General
- To power off an XTM 5 Series device, you must press and hold the rear power switch for 4-5 seconds. [42459]
- On an XTM 5 Series device, the link light for network interface 0 remains lit when the device is powered off using the rear power switch. [42388]
- For XTM 5 Series devices, Interface 0 does not support Auto-MDIX and does not automatically sense cable polarity.
- An XTM 2 Series device can take up to 5 minutes to reboot.
- If your Firebox X Edge e-Series device is connected to a modem, it may not boot correctly if you try to set your Edge to its factory default settings. [30284]
- When you use the Policy Manager > File > Backup or Restore features, the process can take a long time but does complete successfully. [35450]
- Policy Manager opens the locally stored copy of your configuration, instead of the configuration from the device, when you use a status passphrase with a "-" character as the first character in the passphrase (for example: "-1234567"). [42616]
Workaround
Do not use the "-" character as the first character in your status or configuration passphrase.
Upgrade Issues
- After you upgrade a Firebox X Edge from v10.2.x, it is important to know that you must use the user name "admin" when you want read/write access to the Edge. In versions older than v11.0 of Edge appliance software, you could use a name other than "admin" in your administrative credentials, but this is no longer possible in Fireware XTM. You must log in to the Edge with the user name "admin" and the read/write passphrase you set during the upgrade.
- The disk space occupied by data in the Report Server database before you upgrade to v11.2.x is not freed until after the number of days specified in the Keep reports on the Report Server setting in your Report Server configuration. Because of this, the Report Server database consumes more disk space until this number of days pass.
- If you upgrade to Fireware XTM from an earlier version of Fireware and used a branch office VPN Phase 2 encryption setting of None, this setting is not correctly converted during the configuration upgrade. You must edit your Phase 2 encryption setting manually when the upgrade is complete to select an appropriate encryption setting.
- If you have special characters (, ;) in the policy names of your v10.x configuration, you must remove them from your policy names after you upgrade to Fireware XTM v11 so that reporting and monitoring operate correctly. [36577]
- In WSM v10.x, you could create a Traffic Management action that set both incoming and outgoing traffic bandwidth for an external interface. This action could operate on a policy that managed traffic to and from a trusted network. To reproduce this feature in Fireware XTM v11.x, you must create a Traffic Management action that sets the maximum upload speed on the external interface and the maximum download speed on the trusted interface.
- The Firebox X Edge Require user authentication and Trusted Hosts features do not exist in Fireware XTM, because of the increased granularity available when you configure policies for Edge users. During the Edge upgrade, the users are added to a local group called Local-Users. If you previously had Require user authentication enabled, you must use this group in your policies to enforce user authentication. The Trusted Hosts feature is no longer necessary.
- The DNS suffix and second DNS server entries are not converted when you upgrade from v10.2.x to v11.x on Firebox X Edge e-Series. [40774]
Workaround
Add the DNS suffix and second DNS entries again after you upgrade to v11.x.
WatchGuard System Manager
- There can be problems when you add, update, or delete a server installation from WatchGuard Server Center if WatchGuard System Manager is installed on a Windows 7 computer that has “XP Compatibility Mode” enabled. [56355]
Workaround
Make sure that Windows XP compatibility mode is not enabled on the WSM v11.x executable file. To verify, locate the wsm.exe file in Windows Explorer. Right-click on the executable file, select Properties, and click the Compatibility tab.
- Remote managed Firebox devices configured in Drop-in Mode may not be able to connect to a Management Server that is behind a gateway Firebox also configured in Drop-in Mode. [33056] 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).
- You cannot uninstall WatchGuard System Manager successfully when the WatchGuard Server Center is running on a computer using 64-bit Windows Vista. [39078]
Workaround
Exit the WatchGuard Server Center before you start the uninstall WSM. You can then uninstall WatchGuard System Manager successfully.
Web UI
- The Fireware XTM Web UI does not support the configuration of some features. These features include:
- FireCluster
- Full proxy configuration options
- The editing of static NAT rules
- Certificate export
- You cannot turn on or off notification of BOVPN events
- 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]
- If you use the Web UI to edit an existing proxy policy that has alarm settings enabled, the alarm settings may be disabled when you save your configuration. [38585]
- You cannot create read-only Mobile VPN with IPSec configuration files with the Web UI. [39176]
WatchGuard Server Center
- If you run the v11.3.2 Management Server Setup Wizard, but your gateway Firebox or XTM device is installed with pre-v11.3.2 software, the setup wizard can fail.
Workaround
You can either upgrade your gateway Firebox or XTM device to WSM v11.3.2, or do not add the gateway Firebox device information when you run the v11.3.2 Management Server Setup Wizard.
- If the WatchGuard Server Center is open when you uninstall WSM, you see multiple warning messages to close the application, instead of just a single warning. [36901]
Command Line Interface (CLI)
- The CLI does not support the configuration of some features:
- 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.
Logging and Reporting
- The scheduled group reports to .pdf format option does not work. [44679]
- You cannot use a v11.x Report Server with a v10.x Log Server. You must upgrade both servers for reporting to work correctly. You can, however, use v11.x Report Manager with a v10.x Report Server.
- LogViewer always generates PDFs in English, regardless of the language you view LogViewer in. Also, unicode characters that cannot be displayed in the default font may not appear correctly in the PDF. [41244]
Multi-WAN
- When you enable the Multi-WAN Immediate failback option for WAN failover, some traffic may fail over gradually. [42363]
- When you enable Multi-WAN in round-robin mode, you cannot use the HTTP Proxy Caching Server option. [57561]
Networking
- You cannot bridge a wireless access point to an interface configured as trusted or optional if that network interface is already part of a bridge. [39603]
- You cannot configure traffic management actions or use QoS marking on VLANs. [56971, 42093]
- You cannot bridge a wireless interface to a VLAN interface. [41977]
- 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.
- 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]
- After you enable the MAC access control list or add a new MAC address, you must reboot your Firebox before the change takes effect. [39987]
- 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 Firebox. [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 Firebox 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 Firebox in Bridge Mode, the LCD display on your Firebox shows the IP address of the bridged interfaces as 0.0.0.0. [39324]
- When you configure your Firebox 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 Firebox is configured in Bridge mode. [36900]
- When your Firebox is configured to use Bridge mode, the physical interface of the Firebox does not appear correctly in log messages. Instead, the interface is represented as "tbrX". [36783]
- 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]
Firebox X Edge e-Series Wireless
- When a Firebox X Edge e-Series is configured as both a wireless access point and as a Mobile VPN with SSL endpoint, the wireless connection does not work correctly if the SSL VPN address pool is configured on the same subnet as the wireless access point. [42429]
- When you set the external interface as a wireless client and configure static NAT to use the Eth0 interface as its source IP address, inbound static NAT does not operate correctly. [38239]
- The MAC Address Override feature is not available on a Firebox X Edge that has a wireless interfaced configured as an external interface. [38241]
FireCluster
- Each XTM device has a set of default IP addresses assigned to the device interfaces in the range 10.0.0.1 – 10.0.11.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.
- If you change the IP address for the Primary or Backup cluster interface, when you save the configuration to the FireCluster, both clustered devices restart at the same time without warning. [57716]
- 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 cannot configure your FireCluster in active/active mode because these switches do not support the addition of static ARP entries. [41396]
- FireCluster is not supported if you use either a Drop-in or Bridge network configuration mode on your WatchGuard devices. [37287]
- 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]
- FireCluster does not support dynamic routing. [39442]
Authentication
- 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]
Proxies
- The ability to use an HTTP caching proxy server is not available in conjunction with the TCP-UDP Proxy. [44260]
- Application Blocker can only block the initial login to Skype. It cannot block traffic for a Skype client that has previously logged in. If a user with a laptop logs in to Skype when the computer is not connected to your network, and then the user connects to your network while the Skype client is still active, Application Blocker cannot block the Skype traffic until the user exits and logs out of the Skype application.
- Application Blocker does not stop all BitTorrent connections. It does stop most connections, which causes BitTorrent throughput to be significantly reduced. [44288]
- 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.
Security Subscriptions
- You cannot use a WebBlocker Server through a branch office VPN tunnel. [56319]
- To optimize performance of web browsing on the Firebox X Edge e-Series, Gateway AntiVirus does not scan the following content types when used with the HTTP proxy: text/*, image/*, audio/*, video/*, application/javascript, application/x-javascript, and application/x-shockwave-flash. The content types appear in the HTTP-Client proxy action configuration for the Edge, but Gateway AV does not scan for these content types. All other content types, including executable files, are scanned. Gateway AntiVirus also does not use code emulation capabilities of the AV engine on Firebox X Edge e-series appliances.
Mobile VPN with SSL
- Users who try to upgrade their Mobile VPN with SSL client from Fireware XTM v11.2.1 to a later version of Fireware XTM will fail. The failure does not damage the v11.2.1 client installation. [43970]
Workaround
To upgrade your Mobile VPN with SSL client from v11.2.1 to v11.3, use your web browser to connect to https://<IP address of a Firebox or XTM device>/sslvpn.html. You can then download and install the new client software. Or, you can download the client software from the Software Downloads page and email it your users to install on their computer.
- The Macintosh SSL VPN client may not be able to connect to a Firebox when the authentication algorithm is set to SHA 256. [35724]
- When the Macintosh SSL VPN client disconnects or is stopped manually, the client disables the AirPort wireless adapter on the Mac. [39914]
Mobile VPN with IPSec
- 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.
- When you use the Web UI or CLI to configure Mobile VPN with IPSec user profiles, user groups with extended authentication may show incorrectly as Firebox Local Authentication groups. [39695]
Branch Office VPN
- When you configure your Firebox or 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 multi-WAN 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.
- After ESP encapsulation, the IP header ID Field is not unique when IP fragmentation occurs. [56956]
- 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 Firebox or 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 Firebox 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).
- The VPN Keep-Alive feature is not available for the Firebox X Edge e-Series. [37769]
- 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]
- When you set the Phase 2 SA expiration to zero by setting both the Life-time and Life-size values to 0, the Firebox changes the rekey life-time to 8 hours. [37209]