Named Access Lists (NACL) Cisco CCNA

แชร์
ฝัง
  • เผยแพร่เมื่อ 4 มี.ค. 2012
  • A quick tutorial on writing and applying a named access list to a Cisco router. The tutorial is done using Packet Tracer.
    Find more information on access lists by going to my CCNA 3 playlist: • Cisco CCNA 3 - Scaling...
    Subscribe! and for more information visit me at danscourses.com

ความคิดเห็น • 17

  • @artemisgladstone42
    @artemisgladstone42 3 ปีที่แล้ว

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

  • @RakeshKumar-ep1eh
    @RakeshKumar-ep1eh 5 ปีที่แล้ว +1

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

  • @yxmordarbert
    @yxmordarbert 11 ปีที่แล้ว +2

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

  • @aruizsilva
    @aruizsilva 3 ปีที่แล้ว

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

  • @Uncle_KuKu
    @Uncle_KuKu 7 ปีที่แล้ว

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

  • @agnesthomas9169
    @agnesthomas9169 6 ปีที่แล้ว +2

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

  • @mustafaocalan1954
    @mustafaocalan1954 8 ปีที่แล้ว +1

    thanks for good explanations!

  • @kekaemmanuel6443
    @kekaemmanuel6443 4 ปีที่แล้ว

    thank you so much, this is much more clear

  • @irshadnetworks
    @irshadnetworks 12 ปีที่แล้ว

    thanx buddy for dis video...

  • @jackdoe8257
    @jackdoe8257 6 ปีที่แล้ว +1

    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
      @mrnobody6743 6 ปีที่แล้ว +1

      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
      @davidadams2395 5 ปีที่แล้ว

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

  • @bills4915
    @bills4915 10 ปีที่แล้ว

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

  • @prakashsubramanian4671
    @prakashsubramanian4671 4 ปีที่แล้ว

    Thankyou

  • @edgblades
    @edgblades 7 ปีที่แล้ว

    Thank you!!!!!

    • @danscourses
      @danscourses  7 ปีที่แล้ว +1

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

  • @MrRapell
    @MrRapell 12 ปีที่แล้ว

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