Routing decision when there are two default gateways on windows

Solution 1:

Your ping to 10.0.0.180 goes out to 10.0.0.191 based on the 3rd rule

Solution 2:

Have a look at this:

Using multiple gateways

If you have multiple interfaces and you configure a default gateway for each interface, TCP/IP by default automatically calculates an interface metric that is based on the speed of the interface. The interface metric becomes the metric of the default route in the routing table for the configured default gateway. The interface with the highest speed has the lowest metric for its default route. The result is that whenever multiple default gateways are configured on multiple interfaces, the fastest interface will be used to forward traffic to its default gateway.

If multiple interfaces of the same speed have the same lowest interface metric, then, based upon the binding order, the default gateway of the first network adapter is used. The default gateway for the second network adapter is used when the first is unavailable.

In previous versions of TCP/IP, multiple default gateways all had a default route metric set to 1, and the default gateway used depended on the order of the interfaces. This sometimes caused difficulty in determining which default gateway the TCP/IP protocol was using.

Solution 3:

Have this issue when WiFi and Ethernet are connected at the same time. Ethernet is faster per previous post thus behavior is that the PC wants to send data thru Ethernet gateway by default and does not load balance or utilize both paths if one path does not lead to the internet.

I wanted to have WiFi access when configuring bench devices. So I went into TCP advanced settings on each adapter, un-check auto metric - set Ethernet to 15. Set WiFi to 1. The problem was gone. Just like OSPF metric for preferred path selection.