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

 

411 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 Rene,

    So far I know we dont use src rewrite for Outside NAT . For outsite NAT ,We use Port forwarding to a particular IP(Dont translate SRC IP Just rewrite DST IP).So how the problem occure .I think no issue on Legacy NAT or do me more explanation in which situation, we will use NAT Virtual Interface.Thanks

    br//
    zaman

  2. This article is important, for having a good understanding of NAT.

    I do understand that the real issue is : How to reach a WAN address from a LAN domain, by pinging a LAN address (that is supposed to be translated to the target WAN address). I do also understand that the solution is not supposed to use routing rules for jumping from LAN side to WAN side.

    However, some points are confusing for me.

    * Point-1

    The issue is first demonstrated by typing the command below :

    R1#ping 192.168.12.3 repeat 1

    But ; the following explanation lines do no longer use it. Inst

    ... Continue reading in our forum

  3. Hello Maodo

    The command ping 19.168.12.3 repeat 1 is used to test if a NAT translation without a default route will function correctly.

    The command ping 192.168.23.1 repeat 1 is a completely different test. which is testing the NAT translation between 192.168.23.1 and 192.168.12.1. This can be seen from the words: “Let’s try something else…” before the command as seen below:

    https://cdn-forum.networklessons.com/uploads/default/original/1X/6d0c020b8ef1d033c

    ... Continue reading in our forum

  4. Rene,

    Regarding NAT VI I noticed a limitation I am having when configuring this and I was wondering if you can shed some light on this.

    First off, great explanations and examples of NAT VI. Network Lessons has definitely been one of my go to sources for studying and I have been recommending this site to co-workers which find this site amazing as well.

    Back to my question:

    When I configure NAT VI I can test my nat translations from within my LAN hitting my WAN ip address ex: (12.1.1.1 port 80) but why can I no longer remote into that device through its local IP

    ... Continue reading in our forum

  5. Hello Juan

    From my understanding, this is your topology (correct me if I’m wrong:

    https://cdn-forum.networklessons.com/uploads/default/original/1X/f6e6af614d5eb1a432c13de01c9e27f8e4c5d48c.jpg

    You are translating:
    * 12.1.1.1:80 on the WAN interface to 10.1.1.2:80
    * 12.1.1.1:443 on the WAN interface to 10.1.1.4:443

    So, you are able to remote into Device 1 from Device 2 ONLY when you connect via the 12.1.1.1:80 address and you cannot connect when you attempt to connect directly to 10.1.1.2. Correct?

    If this is the case, then the NAT configuration has nothing to

    ... Continue reading in our forum

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