The route-map refereces as ACL that permits three hosts, as follows:
match ip these-hosts
ip access-list extended these-hosts
permit ip host 172.16.1.100 host 10.10.10.100
permit ip host 172.17.1.100 host 10.10.10.100
permit ip host 192.168.1.100 host 10.10.10.100
One observation: the 192.168.1.0 /24 is the network of the nat inside interface (fa0/0) and the address space of the third ACE in the ACL referenced in the route-map. This may or may not be related to the problem (I suspect it is).
Finally, the problem is that the two source addresses in the 172.NumberSpace are correctly nat'ed to the serial0/0 interface address, but the source address 192.168.1.100 (and others tested in that same class C address space) do NOT get NAT'ed.
Re: Source address NAT ok for some addresses, not others
NAT config looks good.
The only traffic that would be NATted from the 192.168.1.0/24 subnet is if it comes from 192.168.1.100 destined for host 10.10.10.100. Was the source traffic coming from another host on the 192.168.1.0/24 subnet. In that case, you would have to reconfigure the 3rd ACL statement to permit the whole subnet.
If you still have problems, can you post the router config and show ip nat transalations.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...