Windows 10 does not route packet on the direct interface

Question

Hello,

In our setup we have 1 PC running Windows 10 (up to date) with several network interfaces.

• 1 wifi connection
• 1 wired connection

The Wifi connection is configured with DHCP. It has a default gateway.

The wired connection is configured with static IP. It does not have default gateway (intentional)

IMPORTANT: we are using public IPv4 range in our private network (I know it is very bad, but I did not choose that one)

Here are the IPv4 routes known by Windows OS:

What we see is Windows use the default gateway instead of using the network interface which is connected to the target network (here the 80.0.0.0/5):

We are sure IP of 80.0.1.10 replies to ping as when we connected directly we get response.

I thought in networking one of the rule was to use the network interface which is connected directly to the network/subnet of the IP we try to reach but here it is not the case when we look at the tracert command report.

Can you let me know why Windows use the network interface where the default gateway is defined? and not the interface where the subnet 80.0.0.0/5 is defined?

Answer 1

behavior probably due to bad cable... sorry