Operational Defect Database
BugZero found this defect 780 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
WatchGuard Technologies | kA16S000000O6zYSAS
Firebox networks unavailable in new policies for cloud-managed Fireboxes
Last update date:
3/16/2023
Affected products:
Firebox M200
Firebox M300
Firebox M270
Firebox M370
Firebox M470
Firebox M570
Firebox M670
Firebox M290
Firebox M390
Firebox M400
Firebox M500
Firebox M440
Affected releases:
All
Fireware
11.x
11.1.x
11.10.x
11.10
11.10.1
11.10.2
11.10.3
11.10.4
11.10.5
11.10.6
Fixed releases:
All
Description:
Issue
WatchGuard development has identified a bug that prevents the WatchGuard Cloud user interface from correctly displaying Firebox networks used in Firewall policies.When you try to add a Firebox network to either the To: or From: fields of a policy, no Firebox networks are listed for selection.Existing policies that use Firebox networks still function, but the WatchGuard Cloud interface displays an objectID instead of the Firebox network name. The format of these objectIDs looks like "net_310814_12345678XXXXXXXXX".
Workaround/Solution
Firebox networks display correctly when you add them to aliases. As a workaround, create an alias and add the Firebox network to it. Firewall policies can then be made with this alias, or by specifying the Firebox network's subnet as a Network Ipv4 type address.
