This would be the correct ACL line to achieve your goal. Just make sure the ACL is applied in the right direction (in or out) keeping in mind that the first part describes source IPs and the second part describes destination IPs in the IP packets.
Every ACL has an implicit deny any any invisible as last statement. So if this is the full ACL then 172.18.44.0/24 can access any destination IP from 172.20.96.0 to 172.20.99.255 inclusive.
Be aware, that ACLs are used for different purposes (like for NAT). So depending on how it is used, connectivity might be restricted to the addresses above or not restricted at all.
To judge the real impact we would need a configuration excerpt with all references to this ACL.
: the number of networks and which networks can not be concluded from the ACL. This will depend on your IP environment and which subnetting is in use. This way you could have access to one network 172.20.96.0/22 or to 4 networks 172.20.96.0/24, 172.20.97.0/24, 172.20.98.0/24, 172.20.99.0/24 or to 255 networks with mask /30 or combinations thereof.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...