-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] FirewallPolicyRuleGroup data returned is incomplete for IPGroup based DNAT rules. #1295
Comments
Adding more troubleshooting details based on the network traffic capturing done: Here' the REST API request being sent out when using the above SDK :
and the Response is:
Not sure how to send the IPGroup as part of Policy rule creation... The earlier shared code works if the IPGroup Resource Id is replaced by an IP address. |
@krsanty |
That is still in pre-release, any timelines for the release? |
Should be within a month or so (however it already got delayed multiple times). |
Decided to go ahead with Azure REST API. Will switch to new SDK once it is released. |
Bug Description
On test environment, we have Firewall Manager set up and have added DNAT rules to it. Getting FirewallPolicyRuleGroup using GetAsync, returns the correct FirewallPolicyRuleGroup. However, the Rules that is returns does not contain SourceAddresses if the rule is IP Group as source type. For IP Address as source type, rule returned has correct SourceAddresses.
client.FirewallPolicyRuleGroups.GetAsync(fwPolicyResourceGroupName, fwPolicyName, fwPolicyCollGroupName);
Here's the RuleCondition when Rule is IP Group as source (note the SourceAddresses):
In addition, when we try to create new DNAT rule based on IP Group, it throws an exception
Microsoft.Rest.Azure.CloudException: 'The request is invalid.'
.The SourceAddresses that is being passed is List of IPGroup ResourceID. Code snippet used to test is below.
To Reproduce
Steps to reproduce the behavior:
Code Snippet
Expected behavior
The text was updated successfully, but these errors were encountered: