You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues, open and closed, and I'm convinced that mine is new.
The title contains the plugin to which this issue belongs
Describe the bug
Plugin version used: 1.2
The os-firewall automation-rules do not allow gateway-groups to be selected (as gateway).
If one tries to set a gw-group via API there is no error response.
The gateway of the processed rule is set to 'none'.
To Reproduce
Steps to reproduce the behavior:
Add a gateway group in 'System - Gateways - Group'
Install the plugin os-firewall
Try selecting the before created gw-group as target gateway for a rule in 'Firewall - Automation - Filter'
Expected behavior
Being able to select gateway groups as target gateway for those rules as this is an important functionality.
Screenshots
Per example:
automation rules
default rules
Additional context
This is a very commonly used functionality and therefore it would be nice for it to be available using the API.
Lack of this functionality makes the API management unusable in many practical use-cases and environments. (WAN-/VPN-Failover and so on..)
The text was updated successfully, but these errors were encountered:
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Describe the bug
Plugin version used: 1.2
The os-firewall automation-rules do not allow gateway-groups to be selected (as gateway).
If one tries to set a gw-group via API there is no error response.
The gateway of the processed rule is set to 'none'.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Being able to select gateway groups as target gateway for those rules as this is an important functionality.
Screenshots
Per example:
Additional context
This is a very commonly used functionality and therefore it would be nice for it to be available using the API.
Lack of this functionality makes the API management unusable in many practical use-cases and environments. (WAN-/VPN-Failover and so on..)
The text was updated successfully, but these errors were encountered: