Hello Vadim
Concerning your statement, I understand the logic behind it. However, we must also take into account the many problems that NAT causes. Some of the most notable are:
- A degradation of performance
- difficulty of applying QoS
- causes problems with some applications, including VoIP, IPSec, FTP etc which require further configuration to resolve
- increased complexity
Now the solutions that you describe above are indeed solutions that NPT delivers, however, the question is, do you want to have those solutions at the expense of the above mentioned problems? Most would probably say no. Redudnancy can be achieved in other ways so you wouldn’t typically see the use of NAT in IPv6 for this purpose. It really comes down to what each administrator chooses to deploy of course, but what you describe would not be that common. Actually I’m interested, do you have any examples of a production network that has such a setup?
There is no nat66 command on Cisco IOS. You would use the ipv6 nat command to implement NAT66. Here is an example configuration:
! Enable IPv6 unicast routing
ipv6 unicast-routing
! Configure the inside and outside interfaces
interface GigabitEthernet0/0
description Inside Interface
ipv6 address 2001:db8:1::1/64
ipv6 enable
ipv6 nat inside
no shutdown
!
interface GigabitEthernet0/1
description Outside Interface
ipv6 address 2001:db8:2::1/64
ipv6 enable
ipv6 nat outside
no shutdown
! Configure the static NAT66 translation
ipv6 nat translation static 2001:db8:1::10 2001:db8:2::10
I hope this has been helpful!
Laz