Basically, what I want to accomplish is a static subnet nat translation from between 10.0.0.0 and 126.96.36.199
But I only want some specific conversations to be NATted, so I added a ACL in combination with a route-map, to specifiy the traffic to be NATted.
When I test the conversations specified in the ACL, the NAT process does add the translation, but only as fasr as the classufll bits count, 10.0.0.0 in this case. Show ip nat translations shows us the following:
R019#show ip nat translations
Pro Inside global Inside local Outside local Outside global
after implementing this in my config, the specific ip connections, did get NATted the correct way, and not just the first 8 bits. All this sounds not clear to me, and I think they have to further investigate this issue.
and this is the answer for the config u have done:
Typically, the ip nat inside source static command is used to translate a small number of entries between your network and two other networks. However, this command provides one interesting parameter: extendable. This parameter causes the Cisco IOS to create an extended translation entry in the translation table instead of a simple entry
example, internal has two Internet connections for redundancy. ISP1 has assigned an IP address space of 188.8.131.52/24. ISP2, which does not support ISP1's address space, has assigned 184.108.40.206/24 to this network. This poses a problem because you need to set up a static translation for the internal web server. Normally, a static statement allows only one translation. In this example, you must choose between 220.127.116.11 translated to 10.0.0.1, or 18.104.22.168 translated to 10.0.0.1 for the web server translation.
Using the extendable parameter, however, you can associate more than one global address with a local address