First off, this is not the first time I did this... but it is the first time in 12.4... and it seems there have been changes that are causing me issues.
Here is a sample of what I had done in 12.3 which worked perfectly.
description Internal Side
ip address 10.0.2.254 255.255.255.0
ip nat inside
description Internet Side
ip address 220.127.116.11 255.255.255.240 secondary
ip address 18.104.22.168 255.255.255.240
ip nat outside
ip nat inside source static tcp 10.0.2.2 80 22.214.171.124 80 extendable
ip nat inside source static tcp 10.0.2.2 80 126.96.36.199 80 route-map biWAN-PAE extendable
ip route 0.0.0.0 0.0.0.0 188.8.131.52 permanent
route-map biWAN-PAE permit 10
set ip next-hop 184.108.40.206
Now when I try to do this in 12.4, it simply won't work. First it won't allow the two "ip nat inside source static" commands as-is. I need to define them with a route-map each. So I created another route-map with a "set ip next-hop" for the 220.127.116.11 gateway. But all my traffic is headed to 18.104.22.168 regardless of what translation/route-map it uses.
My thought at this point is to setup a loopback interface for all 'outside' traffic and try to setup a route-map on the loopback interface so I can have the route-map ACLs working on public IP addresses...
Thoughts on this?
Thanks! -Cheers, Peter.