A subnet NAT'ing out DSL occasionally ends up going across another public and then out on the internet in a
set up with 2 differing private subnets that each NAT out each of their own public interfaces.
For sake of example:
DSL: 22.214.171.124, next-hop indicated in route table 126.96.36.199
Bonded Multilink: 188.8.131.52, next-hop 184.108.40.206
Eth1: 220.127.116.11/24 (Hardwired LAN)
Eth2: 18.104.22.168/24 (Wifi)
ip route 0.0.0.0 0.0.0.0 Multilink1
ip route 0.0.0.0 0.0.0.0 Dialer0
ip nat inside source route-map nonat Multilink 1 overload
ip nat inside source list 1 Dialer0 overload
route-map nonnat = 22.214.171.124/24 (Hardwired LAN) permited to NAT, and a VPN subnet (not listed excluded from NAT) that is excluded from NAT
list 1 = 126.96.36.199/24 (Wifi)
Things I've tried that didn't work to effectively fully segment the NAT instances...
- setting next-hop in a route-map
- inserting Null routes so the proper route gets picked up out of the translation table and doesn't get to
its NAT interface only to hop over and out another public interface.
*I think setting next-hop on my DSL doesn't work because of the setup bridging-wise on the ISP side
Appreciate any help. I'm sure its some minor little oversight, but my main issue is simply to just have
wifi NAT out DSL only, no hopping over and out via another public and vice-versa.