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 581 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

 

295 New Members signed up 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. Hmm I should try that. The command is still accepted right?

    The easiest method is probably advertising a default route through redistribution or by using the summary-address command on an interface. I never really liked the ip default-network command.

  3. Rene you should give this section a rewrite - you suggest 2 methods which are both not mentioned by cisco and are partly legacy.

    Default-route injection into eigrp should be done via redistribution (prefered) or via summarization on the interface:

    http://www.cisco.com/c/en/us/support/docs/ip/enhanced-interior-gateway-routing-protocol-eigrp/16406-eigrp-toc.html#defaultrouting

    We should be aware of all possible methods but always prefer the best practices from cisco.

  4. andrew says:

    Nope. Do you? Maybe just paste the config into a code window.

  5. The second configuration did not work for me as well. I can the interface of the ISP router and get replies but not the loopback of 3.3.3.3

    So it seems to be partly working.

    the routes seem fine I am using this version of IOS: c3640-jk9s-mz.124-16.bin

    here is another pic

    if want to see something else I will upload.

    I also took wireshark on the interface between ISP and R2.

    Now to me that seems to say its getting there correctly from the default route but from my understanding no response found means that it is unable to find its way back. So I tried to change the ip route on ISP to fastethernet 0/0 instead of and IP but that did not work.

    I am betting if I changed and added a default route on ISP it would work but not sure that would be a good thing to default route back into the network lol…

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