Report failed for policy NAT statements
-
Craig Bugzefsky
- State changed from new to open
This is a known issue, Flint does not comprehend ACL based NAT rules at this time.
How does this fail for you tho, it should just not comprehend the NAT mapping, but continue to analyze the rest of the firewall.
-
securantakra
The report failed with the following message:
application error
Flint::LineError at /upload
Error analyzing static <>wrong number of arguments (1 for 2)
* file: range_set.rb * location: initialize * line: 234Is this feature planned for future releases, or have a workaround. The report is only running if I delete alle ACL based NAT statements.
Kind regards -
Craig Bugzefsky
Lighthouse <no-reply@lighthouseapp.com> writes:
Unfortuantely, I cannot think of a workaround at this time.
Deleting all ACL lines does make it work, but it's going to give you
some incorrect results, particularly the set of hsots that can speak a
given protocol thru the firewall.It is planned for a future release, and I'll try to prioritize this.
The machinery to manage ACL NAT is there, we just haven't had time to
hook it all up.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.