From: ISolveSystems (support@isolvesystems.com)
Date: Fri Sep 28 2007 - 13:07:11 ART
I got it working now. Does anyone know why i have to turn off ip route-cache
on the serial interface to make it work?
R6(config-if)#do sh run | sec ipv
ipv6 unicast-routing
int lo0
ipv6 address 3333:6:6:6::6/64
ipv6 nat
int s1/2
ip address 104.69.69.6 255.255.255.0
no ip route-cache cef
no ip route-cache
ipv6 nat
ipv6 route 3333:9:9:9::9/128 Serial1/2
ipv6 nat v4v6 source 104.69.69.16 3333:6:6:6::6
ipv6 nat v6v4 source 3333:6:6:6::6 104.69.69.16
ipv6 nat prefix 3333:9::/96
R9
ipv6 unicast-routing
int lo0
ipv6 address 3333:9:9:9::9/64
ipv6 nat
int s1/2
ip address 104.69.69.9 255.255.255.0
no ip route-cache cef
no ip route-cache
ipv6 nat
ipv6 route 3333:6:6:6::6/128 Serial1/2
ipv6 nat v4v6 source 104.69.69.19 3333:9:9:9::9
ipv6 nat v6v4 source 3333:9:9:9::9 104.69.69.19
ipv6 nat prefix 3333:6::/96
On 9/28/07, Alex Steer <alex.steer@eison.co.uk> wrote:
>
> Because you haven't configured most of it.
> Check below:-
>
> 1. Firstly. As with any nat you need to enable it on the outside
> and inside interface(s) with the "ipv6 nat" command
>
> 2. Next you need a prefix that can be used by v4 hosts for
> reachablity (config)#ipv6 nat prefix X::X:X/96 (this can also be
> configured on a per interface basis)
>
> 3. You need a translation in each direction (remember the command
> here is SOURCE so it isn't the same command flipped on its head)
>
> Ipv6 nat v6v4 source ipv6hostsource ipv4somethingmadeup
> Ipv6 nat v4v6 source ipv4hostsource somethingintheprefixrange
>
> Don't forget the v6 host needs a route to the prefix range and the v4
> host needs a route to the ipv4somethingmadeup range
>
> Check to see if this works below:-
>
> R6
> Int lo1
> Ipv6 nat
> Int fastconnection r/9
> Ipv6 nat
>
> Ipv6 nat prefix 2001:6::/96
> ipv6 nat source v6v4 source 3333:6:6:6::6 104.69.69.16
> ipv6 nat source v4v6 104.69.69.16 2001:6::104:69:69:16
> ipv6 route 2001:9::/96 next-ipv6-hop-address
>
> -------------------------------------------------------
>
> R9
> Int lo1
> Ipv6 nat
> Int gigaconnection r/6
> Ipv6 nat
>
> Ipv6 nat prefix 2001:9::/96
> ipv6 nat v6v4 source 3333:9:9:9::9 104.69.69.19
> ipv6 nat v4v6 source 104.69.69.19 2001:9::104:69:69:16
> ipv6 route 2001:6::/96 next-ipv6-hop-address
>
>
>
> let me know how you get on (forgive if my syntax is wrong). Debug ipv6
> nat and debug ipv6 packet will show you if you have the correct routing
> and nat statements in both directions.
>
> Alex
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> ISolveSystems
> Sent: 28 September 2007 03:05
> To: groupstudy
> Subject: Simple IPv6 NAT config
>
> R6 connects to R9 via Serial using IPv4 address. R6(104.69.69.6); R9(
> 104.69.69.9)
>
> R6 Lo1 - 3333:6:6:6::6
>
> R9 Lo1 - 3333:9:9:9::9
>
> Task asks to configure IPv6 NAT over the serial link. Lo1 int should be
> able to ping each other using IPv4 address from the shared subnet. Do
> not
> use Overload.
>
> Below is the config. Any idea why it doesn't work?
>
> R6
> ipv6 nat v6v4 source 3333:6:6:6::6 104.69.69.16
>
> R9
> ipv6 nat v6v4 source 3333:9:9:9::9 104.69.69.19
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
This archive was generated by hypermail 2.1.4 : Sat Oct 06 2007 - 12:01:16 ART