WatchGuard Fireware v11.12 Update 2 was released on 11th April 2017. This replaces the previous version of 11.12.1.
It’s good practice to send WatchGuard Firebox traffic logs to a WatchGuard Dimension server so that you have a separate historic log of activity, as a Firebox won’t retain its logs over a power cycle. The WatchGuard Dimension server can be useful for troubleshooting, but also has a wealth of reports available as well.
To be able to send log traffic to the WatchGuard Dimension server it needs to be encrypted, so you need to supply enter an identical key on the Firebox and in the Dimension server.
If you have multiple Fireboxes you’ll need to know the existing encryption key so you can set it on the additional Fireboxes.
If you don’t know the encryption key, here is how to change it on the WatchGuard Dimension server (don’t forget to change it on existing Fireboxes).
Here’s a quick WatchGuard tip. I had to do some analysis on bandwidth usage recently, but although I could see the live usage via system manager there was no report for external bandwidth utilisation in WatchGuard Dimension.
To be able to report on bandwidth utilisation in WatchGuard Dimension you need to enable Performance Statistics logging on the WatchGuard Firebox. Here’s how to do it.
Note: Fireware v11.12 Update 1 is now available, see here for details.
WatchGuard Fireware v11.12 and WatchGuard System Manager v11.12 was released on 17th November, 2016. This replaces the previous version of 11.11.4 Update 2.
Full release notes can be found here. Please read them before upgrading! Your Firebox must be running, XTM v11.7.5, v11.8.4 or v11.9 or higher before upgrading.
The software can be downloaded from here.
New features and functions include:
- ConnectWise Integration
- Threat Detection and Response
- Geolocation Service
- Dynamic VPN Tunnels to Azure
- IPv6 Support in Services and Proxies
- Services and Proxies Enabled by Default
- Gateway Wireless Controller
- FireCluster with DHCP on External Interface
- X-forwarded Information from Header in Logs and Dimension
For more detailed information see the presentation below.
What’s New in Fireware v11.12
Working with a client’s WatchGuard XTM firewall recently I was asked to resolve an issue with the web certificate. The self signed default certificate had expired.
In this post I walk through the steps to renew the default web certificate on a WatchGuard XTM device.
I’ve seen a couple of instances recently from two different customers where the WatchGuard HTTP Proxy has blocked websites from being accessed with the following message:
Response denied by WatchGuard HTTP Proxy
Reason: header-line too large=’Set-Cookie:
Please contact your administrator for assistance. Continue reading