Thanks, Tyson.
Do you ever sleep? From: Tyson Scott [mailto:[email protected]] Sent: 09 July 2010 06:48 AM To: Johan Bornman; 'OSL Security' Subject: Re: [OSL | CCIE_Security] Stateful NAT Vol 1 Task 2.7 There is a lot more you can do with the route map that you cannot do with just an access-list. But in this example there is no functional difference Sent from my HTC on the Now Network from Sprint! ----- Reply message ----- From: "Johan Bornman" <[email protected]> Date: Fri, Jul 9, 2010 12:13 am Subject: [OSL | CCIE_Security] Stateful NAT Vol 1 Task 2.7 To: "'OSL Security'" <[email protected]> Hi, The solution in this task is a simple one. I have done some reading about it and found another example using a route-map in the config. Why was a route-map used? What is the difference between the following and can it be done without the use of a route-map? Solution 1: access-list 101 permit tcp any any eq telnet route-map SNAT permit 10 match ip address 101 ip nat inside source route-map SNAT pool SNATp mapping-id 10 Solution 2: access-list 101 permit tcp any any eq telnet ip nat inside source list SNAT pool SNATp mapping-id 10 Found the route-map example at: http://blog.ipexpert.com/2009/04/27/high-availability-nat-with-hsrp/ Thanks Johan
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
