Comments

  • Roger that, thanks James & Bruce!
  • Turns out the ISP tripped the Port Scan Attack threshold and was auto-blocked..lol Addressed that, still curious about the code: 255 and if there is a need for Type: 0 ?
  • You may have already gone through the upgrades but here is my process, hope it helps! * Activate New Trade-Up Firebox: I use the Web UI to speed through the setup with everything default, EXCEPT for the status and admin passwords that I copy over from the the old to new Trade-Up firebox since those are not saved to config…
  • Strange... same here. I see it still mentioned in their support articles below, however via TDR dashboard > Settings > Host Sensor - it seems to have disappeared? http://www.watchguard.com/help/docs/help-center/en-US/Content/en-US/Fireware/services/tdr/tdr_host_sensor_settings_c.html…
  • Bruce is correct for the time being. I believe WatchGuard's Cloud Roadmap has lots of enhancements and updates slated for Q3 & Q4 that will address features like that. For the time being, we use both the Cloud and a Dimension VM for notifications/alarms. It might also be worth looking into the Technology Integrations such…