<NAT translation from a sourced network to a destination network>
mruiz at lstfinancial.com
Sat Jun 19 16:58:57 UTC 2010
Ok cool. That is similar to what I have. Thank you.
Sent using BlackBerry
From: Greg Whynott <Greg.Whynott at oicr.on.ca>
To: Mike Ruiz <mruiz at lstfinancial.com>; nanog at nanog.org <nanog at nanog.org>
Sent: Sat Jun 19 11:02:48 2010
Subject: RE: <NAT translation from a sourced network to a destination network>
depending on your vendor equipment you'll need an ACL or a route map to define the traffic you wish to Nat and apply it to the 'nat engine'.
if you are doing this on cisco ASA or similar it might look something like this:
-define the interesting traffic with an ACL:
access-list 110 permit ip 192.168.1.0 0.0.0.255 10.0.1.0 0.0.0.31
access-list 110 deny ip any any
- create a route-map:
route-map natme permit 10
match ip address 110
- apply the map:
ip nat inside source route-map natme interface GigabitEthernet0/1 overload
hope that helps.
From: Mike Ruiz [mruiz at lstfinancial.com]
Sent: Friday, June 18, 2010 4:13 PM
To: nanog at nanog.org
Subject: <NAT translation from a sourced network to a destination network>
Ok here we go. I know the subject is a little ambiguous, please allow to explain.
I have a network of 192.168.1.0/24 and I need it to reach a network 10.0.1.0/27 only when it needs to be accessed by specific machines that reside on the 192.168.1.0/24 network.
192.168.1.10 à NAT à10.0.1.10 à route that packet to 10.0.1.1.
I only want specific host to route to that specific /27 network .
Any help would be appreciated. So far what I have gathered is only for VPN connections but I do not want to build a VPN. Thank you again in advance.
"If you tell people where to go, but not how to get there, you'll be amazed at the results." -- General George S. Patton Jr.
More information about the NANOG