One router, two gateways

[wrobynson]

Hi. I need some help here...

In this topology, I need the destined traffic interfaces are returned to their respective gateway. That is, traffic to 1.1.1.1 is answered via 1.1.1.2 and traffic to 2.2.2.1 is answered via 2.2.2.2.
The router is a ISR 4000 Series.

Is it possible?

Thank you very much.

[balaji.bandi]

yes it is possible with PBR and NAT correctly.

example :

https://community.cisco.com/t5/networking-documents/dual-internet-links-nating-with-pbr-and-ip-sla/ta-p/3126275

[wrobynson]

Thanks for your repply...

There is NO NAT. And the traffic is from OUTSITE to router interface's (like a simple PING). It's not a traffic from INSIDE to OUTSIDE... In this case we don't have traffic FROM LAN (where the PBR route-map is applyed) TO INTERNET.

[balaji.bandi]

here is NO NAT. And the traffic is from OUTSITE to router interface's (like a simple PING).

Did not get your requirement here or use case, when the p2p link pinging, why does the Router take another path?

Need More Clarity here, is BGP between Routers?

[wrobynson]

Because default route. 

I'm pinging anywhere from the INTERNET. 

Of course I'm simplifying the problem here... For a better understanding.

I need packages destined for 1.1.1.1 to be answered by interface 1.1.1.1. And packages destined for 2.2.2.1 to be answered by interface 2.2.2.1.

Note that the internal network does not matter. We're looking the traffic FROM INTERNET TO INTERFACES.

Thank's.

[Joseph W. Doherty]

How that might be accomplished depends much on how your topology is actually set up.

If the two actual router interfaces were NATed, devices on the Internet would "see" those addresses as the "source" IP and send return traffic to them via their ISP link.  (I.e. 1.1.1.1 would use the 1.1.1.0/30 link and 2.2.2.1 would use the 2.2.2.0.30 link.)

If those router interface are not NATed, i.e. router interfaces are just another L3 transit IP, to IP(s) beyond/behind (i.e. non Internet side) of the router, then we're a bit stuck if the destination (inside/internal) IP is "visible" as the same IP on both ISP connections.  If however, if you can split the (internal/inside) IPs into different minimal Internet addressable address blocks (IPv4 minimum, I believe, is a /24), you can generally advertise those IP address blocks so one IP address block is "better" reached on one ISP connection vs. the other ISP connection.  (I.e. 3.3.1.0/24 prefers 1.1.1.0/30 link and 3.3.2.0/24 prefers 2.2.2.0/30 link.)

BTW, unless you're dealing with a stateful device, in theory (for L3 transit), traffic going to Internet out 1.1.1.1 should be able to return on 2.2.2.1 and the converse too.)