As Randy mentioned "set ip next-hop" for far end router (which really, is not really a BGP neighbour) is not supported. You could have a loopback on the Indy-Rtr, route map with next-hop as the loopback and then static route on the ASA for the said loopback and that would work
On Thu, Apr 28, 2011 at 9:59 AM, Christopher J. Wargaski <[email protected]>wrote: > Hey Keegan-- > > Yes, I have two routers separated by a firewall (which is incapable of > running BGP). The two routers exchange routes via eBGP multi-hop without > problem. Now, I would like to take some of those routes advertised by the > DMZ-rtr (and learned by the Indy-rtr) and advertise them back to the ASA > with the next hop being the DMZ-rtr. > > Re-advertising the routes is not the problem, I can do that fine. > However, making the next-hop be the DMZ-rtr is the thing that I have not > been able to do. After some more thought today, I am afraid this will just > not work so I think I'll wait until the ASA will run BGP. (Which > incidentally is targeted for late 2011.) > > > cjw > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
