We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 643 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

454 Sign Ups in the last 30 days

satisfaction-guaranteed
100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!

Forum Replies

  1. Hi Rene,

    Is there a tutorial on EIGRP default routes using redistribution?

    Cheers
    Rob

  2. hi Rene,
    In the case of ip default network as u explained above, I don’t understand why we need to configure a default route on R2 for the network 192.168.23.3 as in R1 it already shows * next to the “D” for this EIGRP entry.

    Shashank

  3. Hi Shashank,

    The 192.168.23.0 /24 network is used as the default network which means R1 will send packets with an unknown destination there. However, R2 still has to know where to forward packets to…it has no clue how to reach 3.3.3.0 /24 so that’s why we need the default route.

    Rene

  4. I don’t see any attachments.

  5. Hello Minghui

    When you use an Ethernet port as an exit interface, what will happen depends on several factors including the IOS version and the platform that you are using. In some platforms/IOS combinations, what Rene has implemented will work as configured. However, there are some other situations in which it doesn’t. The following link shows a couple of examples where you have an IP address as a next hop IP or an interface as an exit interface. In this example, the use of an exit interface fails.

    https://community.cisco.com/t5/networking-documents/static

    ... Continue reading in our forum

24 more replies! Ask a question or join the discussion by visiting our Community Forum