Why doesn't routing work on Windows 10?

F

fdroid2019-05-13 21:11:00

Computer networks

fdroid, 2019-05-13 21:11:00

Given:
1. Mikrotik, on which a VPN tunnel has been raised to a remote network. There are several subnets in a remote network, routes to each of them are registered in Routes.
2. Home network, which is routed by the same microtic. Several subnets, remote access is available from any home host.
3. Computer on W10 Pro.
Situation. It was necessary to get access to one more remote subnet - 169.254.0.0/24 and a host in it 169.254.0.252. I registered Routes on Mikrotik, the host on the subnet pings and is accessible from any internal host with Linux from any subnet, and even from managed switches it pings. Only W10 is thrown out - it does not respond, "general failure", tracert to the host ends with error 1231. I suspect that it is in W10, because from any other host under other operating systems there is no such problem. Where to dig - it is not clear. Googled it, but didn't come up with anything useful.
On W10 I set both a static IP and via DHCP, rebooted the router, the computer too. On a computer two network interface cards, in different subnets. The first is connected via a managed switch to the network, the second directly to the Mikrotik. Only one is constantly used, the second is always disabled, but, nevertheless, I tried to reach 169.254.0.0/24 with one and the other network, to no avail.

Reply

Answer the question

In order to leave comments, you need to log in

4 answer(s)

S

Stanislav Valsinats, 2019-05-15
@fdroid

Only a change of addressing in the subnet will save the Father of the Revolution

R

Radjah, 2019-05-14
@Radjah

https://en.wikipedia.org/wiki/Link-local_address
> Link-local subnets are not routable: Routers must not send packets with link-local addresses to other networks.
> For IPv4, the 169.254.0.0/16 subnet is allocated as link-local addresses (with the exception of the first and last /24 subnets, which are reserved for the same for the future). According to RFC 3927 (2.1), the block 169.254.1.0 through 169.254.254.255 is reserved for link-local addresses.

A

anykey_ua, 2019-05-14
@anykey_ua

If only Windows 10 is not available from the subnet, and other devices in it are available, then check the Firewall on Windows, as a rule, they turn off ping now (This is especially noticeable on servers)

V

Vladimir Dubrovin, 2019-05-14
@z3apa3a

Add a static route on windows 10
route add -p 169.254.0.0 mask 255.255.255.0 ip
where ip is the address of Windows 10 itself, or simply enter the address from this network + mask in the network connection settings as an additional