We have Mikrotik v.7.11.2 router with two uplink ports eth1 and eth2 and DHCP Client active on each interface, both connected to the same ISP.
ISP DHCP server assigns different IPv4/32 address to each interface, but provides single gateway IPv4 for both interfaces.

Effect is that only one of the interfaces gets actively used (routed through) by Mikrotik, while the other interface remains connected, but not routed through and both routes having the same gateway IP get status of +AS.
Since routing is defined based on the IP, I guess Mikrotik uses whichever interface gets DHCP/gateway issued in order.

Is there any way that I could tie route to a specific interface exclusively?

Note, ISP router is not pingable, but so what I am trying to achive is:
- define one route to ping 1.1.1.1 through eth1 exclusively
- define second route to ping 9.9.9.9 through eth2 exclusively
and then use netwatch through these routes for testing connectivity.
Based on the netwatch results, netwatch scripts could control sending internal subnet 10.1.0.0/16 through eth1
and internal subnet 10.2.0.0/16 through eth2 (if both work) or prioritize differently if only one link is routable through.

So this seems like a typical dual-wan scenario, but having the same ISP gtw confuses matters.
I could make a clumsy addition of two small routers adding additional 192.168.x.x subnets in between which would work and simplify matters, but this would add 2 points of failure, etc.

Thanks!