You would need to use two NAT pools and two different ACLs to separate your internal clients depending on the destination they want to communicate with, and to subsequently NAT them using a selected NAT pool. For example:
ip access-list extended NAT_2 permit ip <LAN Network> <Wildcard> <DestinationX> <WildcardX> ... ... ! ip access-list extended NAT_3 permit ip <LAN Network> <Wildcard> <DestinationY> <WildcardY> ... ... ! ip nat pool NATPOOL_2 22.214.171.124 126.96.36.199 netmask 255.255.255.0 ip nat pool NATPOOL_3 188.8.131.52 184.108.40.206 netmask 255.255.255.0 ip nat inside source list NAT_2 pool NATPOOL_2 overload ip nat inside source list NAT_3 pool NATPOOL_3 overload
Exactly one of the ACLs should actually contain an entry saying
permit ip <LAN Network> <Wildcard> any
to make sure that the internal network gets translated to some of the two public addresses even if itt does not communicate with any specific destination IP.
Do you believe this could be a workable solution for you?
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.