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

 

365 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!

Tags: ,


Forum Replies

  1. Hi,

    Excellent article. I especially like this kind of setup because they are rare and enforce us to make our brain work harder.
    I think there’s some kind of typo in the beginning, in the basic configuration of R2. The following line seems to be missing:

    R2(config)#interface fa0/0
    R2(config-if)#no shutdown
    R2(config-if)#ip address 192.168.12.2 255.255.255.0
    
    R2(config-if)#interface loopback 0       <- This one
    
    R2(config-if)#ip address 2.2.2.2 255.255.255.0

  2. Thanks again bhargavi for your words. You message has been forwarded to Rene.

    Good learning.

  3. Very interesting ; but, I have some questions.

    * Question-1

    I do not see the signification of “PBR” in the lesson ?

    * Question-2

    In the first scenario, the answer is return back by a “Reply” arrow. But, in second and third scenarios, the answer is returned by a “NAT” arrow. What is the difference between “Reply” and “NAT” answers ?

  4. Hello Maodo

    If you notice after the second diagram, it states that any traceroute initiated from R1 to R2 will cause FastEthernet 0/0 to respond rather than going all the way to the loopback interface and back triggering a NAT translation. This is remedied by using PBR.

    ... Continue reading in our forum

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