Named Access Lists (NACL) Cisco CCNA

[@artemisgladstone42]

These video series are so good. Really helpful. Gonna recommend these to everyone ever.

[@RakeshKumar-ep1eh]

This is so amazing there is not even one dislike since 2012 till date 2019 ..! perfect explanation . Thanks a lot

[@yxmordarbert]

im gonna donate to you when i get my first job in networking

[@Uncle_KuKu]

You are the best. Saved my time to read through lecture slide !!!!!

[@aruizsilva]

Thank you very much for your videos. They are very useful for us beginners

[@agnesthomas9169]

Thank you sooo much for. i was able to clearly understand ACL.

[@kekaemmanuel6443]

thank you so much, this is much more clear

[@mustafaocalan1954]

thanks for good explanations!

[@jackdoe8257]

Love your videos.
One question I have is why does this NACL prevent the pinging of 192.168.4.1 from the 192.168.2.0/24 network?
192.168.4.1 is in the 192.168.4.0 0.0.0.254 network we specified in the NACL, however 192.168.2.1 reports destination host unreachable.
I am guessing it is treating the 192.168.4.1 interface on R0 as part of the 192.168.3.0/30 network, but I do not understand why.
Adding an additional statement to the NACL "permit ip 192.168.2.0 0.0.0.255 host 192.168.4.1" corrects this issue.

[@mrnobody6743]

It appears this issue is due to a typo on the wildcard of the NACL. Change the 192.168.4.0 0.0.0.254 to 192.168.4.0 0.0.0.255 and it should work.

[@davidadams2395]

@@mrnobody6743
Good catch. I scanned right over Jack's typo without a thought to it's being incorrect.

[@bills4915]

Just out of curiosity, why do you control C out of most of your commands instead of "exit" or "control z?

[@prakashsubramanian4671]

Thankyou

[@irshadnetworks]

thanx buddy for dis video...

[@MrRapell]

could you please post your packet tracer topology files for download? I am lazy

[@edgblades]

Thank you!!!!!

[@danscourses]

You are very welcome. I am glad the videos are helping out. -Dan