From: Chris Lewis (chrlewiscsco@yahoo.com)
Date: Mon Oct 24 2005 - 10:27:07 GMT-3
Not sure if you got ananswer tothis, but the config is mmissing 4 elements, all described at
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/ipv6_c/sa_natpt.htm
you need the following translation commands
ipv6 nat v4v6 source 192.168.34.3 2001:1111::1
ipv6 nat v6v4 source 2001:14::12 192.168.34.5
ipv6 nat prefix 2001:1111::/96
Then yo need to make sure R1 knows that to get to 2001:1111::/64 it has to go to R4 either via static or routing protocol update.
The key thing here is you are translating source addresses, so you translate the source address of R1 originating the IPv6 ping to an IPv4 address in to an address within the subnet of the R3 to R4 link, likewise translate the source address of the IPv4 router to an address in the v6 subnet you are going to use for the v6 side.
Chris
Scott Smith <hioctane@gmail.com> wrote:
Would someone mind providing a working example of the following IPv6
NAT config? I know some of the config is missing and that is the
problem. Something isn't clicking and I hope seeing a working example
will turn on the light bulb. The goal is to allow R1 and R3 to
communicate.
R1 ---- R4 ---- R3
R1 IPv6 e0/0 <--> R4 IPv6 e0/1 - R4 IPv4 e0/0 <--> R3 IPv4 e0/0
R1:
interface Ethernet0/0
no ip address
ipv6 address 2001:14::1/64
R4:
interface Ethernet0/1
no ip address
ipv6 address 2001:14::4/64
ipv6 nat
interface Ethernet0/0
ip address 192.168.34.4 255.255.255.0
ipv6 nat
R3:
interface Ethernet0/0
ip address 192.168.34.3 255.255.255.0
TIA
-- Scott Smith
This archive was generated by hypermail 2.1.4 : Sun Nov 06 2005 - 22:00:52 GMT-3