Two seperate issues for mxfirewallcontrol.py about automation-scripts HOT 7 CLOSED

Thank you for your feedback. I will take a look at these.

On the second issue: are you asking for the script to verify if the line it is going to insert is the same as the one that already exists in the same position and skip that appliance if true?

from automation-scripts.

Thank you for your feedback. I will take a look at these.

On the second issue: are you asking for the script to verify if the line it is going to insert is the same as the one that already exists in the same position and skip that appliance if true?

Hopefully, I can communicate it better. Sorry for the confusion. What is happening is, It does not go to each backup file and restore to file for each meraki. It actually is taking the first backup file and restoring it to the other Meraki MX devices. So is acting like one backup file for all MX appliances. So it changes the source IP addresses to the wrong backup file. Does that make sense?

from automation-scripts.

I think I fixed the second issue you reported. Please have a look at the latest version of the script, which has moved here: https://github.com/meraki/automation-scripts/tree/master/mx_firewall_control

I will do some testing on the other issue next week.

The script has also been updated to use API v1 and now has the option to fetch the API key from an environment variable.

from automation-scripts.

Thank you for getting this completed. I will test and let you know what I find. It is a great script for Outbound Firewall rules changes on the Meraki MX devices.

from automation-scripts.

Please check the latest version of the script. It should no longer duplicate "allow any" default rules.

Note that if the ruleset you are inserting ends with an "allow any", the script will not strip it, unless it ends up being positioned as the last rule of the merged ruleset. Inserting an "allow any" in between other rules can be intentional, for example to disable processing part of the ruleset without removing it. To prevent inserting the "allow any" in this scenario, modifying the source ruleset is the way to go.

Let me know how your tests go.

from automation-scripts.

Closing due to inactivity. If the problem persists in the latest version, please reopen this issue.

from automation-scripts.

Sorry for the delay in responding. I have finally tested and the two issues have been resolved successfully. Thanks for getting it done.

from automation-scripts.