Invalid ACL created by CiscoIOSConfigWriter

Issue #22 new
Michael Kremer created an issue

In removeAcl, when creating a permit ACL on an interface with an existing access group, there doesn't seem to be a check to see if the existing access group is standard or extended. The new ACL is always extended but uses the name of the existing ACL, which is invalid if the existing ACL is standard.

For example, the following line is generated but invalid:

access-list 1 permit ip 13.0.0.0 0.255.255.255 11.0.0.0 0.255.255.255

I think a check should be added in the scope of these log messages

logger.debug("Could not find the ACL belonging to target interface!");
logger.debug("Assuming traffic is implicitly denied. Creating permit ACL.");

I was able to workaround this by only using extended ACLs in this config file.

Comments (0)

  1. Log in to comment