I thought of that, Based on my original experimentation, the ASA box would not route to the secondary interface. Lets say a user from outside has a public IP of 99.99.99.99. That user connects to the 1811, ISP2, on ip 2.2.2.2... which then gets forwarded to the ASA on the secondary interface. The ASA would see the 99.99.99.99 coming into its secondary ip, and when it responds, would then consult the routing table for how to route 99.99.99.99... which, because 99.99.99.99 is a public ip... would be down the primary interface... and therefor out ISP1.
Main Topics
Browse All Topics





by: wingateslPosted on 2009-07-04 at 10:50:21ID: 24777479
My idea here is to put a secondary IP address on the ASA. You then would route-map the second IP to the second ISP on the 1811. The ASA would perform NAT, Firewall, and VPN.