![]() Like I said, this works from the router at all times and does work from the LAN if I run: I should clarify that yes, I do need to NAT overload out both interfaces: I chose to setup static routes over policy routes because I don't really care what the source IP/mask is, but the destination: any LAN packet that matches the destination address of my static routes needs to go out the fe0/1 WAN interface. ![]() I've tried adding a pool and associating it with access-list 1 I also created another access-list 15 with the same LAN ip network address, but they all just seem to "replace" the NAT scheme so that my static routes work for fe0/1 (tested from LAN with ping .address), but stop working for Dialer1 (fe0/0/0). Ip nat inside source list 1 interface Dialer1 overload Here's what I have in my config that's relevant:Īccess-list 1 permit 192.168.0.0 0.0.0.255 However, machines on the LAN cannot get out on fe0/1 ( ping .address doesn't work). I also have NAT working for Dialer1 machines on the LAN can get out without issue. ![]() I believe this is working ok - I can traceroute from the IOS shell and it's going out fe0/1. I've setup permanent static routes for various IPs to route out through fe0/1. I have a feeling the answer is policy-routing, but I'd like someone to clarify that.īasically I'm not having any luck getting NAT to work with two WAN interfaces.
0 Comments
Leave a Reply. |