What's wrong with routing on Mikrotik?

Question

Mikrotik

On bgw, through a switch with 802.1q, I started the network in vid 69. I assigned an address to the interface from this network - 10.62.69.222/24 I
registered the connected route, connectivity appeared within the network. On that network, there is a gateway 10.62.69.254, behind which is another network 192.168.100.0/24. Registered a static route, expecting that everything will work. Unfortunately, it just didn't work out that way. Here is what Mikrotik says:

 > ping 10.62.69.254
HOST                                     SIZE TTL TIME  STATUS
10.62.69.254                               56  64 0ms
10.62.69.254                               56  64 0ms
    sent=2 received=2 packet-loss=0% min-rtt=0ms avg-rtt=0ms max-rtt=0ms

 > ip route print detail
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit
 0 ADS  dst-address=0.0.0.0/0 gateway=89.ХХ.ХХ.ХХ gateway-status=89.ХХ.ХХ.ХХ reachable via  pppoe-ХХХ distance=1 scope=30 target-scope=10

 1 A S  dst-address=10.62.69.0/24 gateway=v69 gateway-status=v69 reachable distance=1 scope=30 target-scope=10

 2 ADC  dst-address=10.62.69.222/32 pref-src=10.62.69.222 gateway=v69 gateway-status=v69 reachable distance=0 scope=10

 3 ADC  dst-address=89.хх.хх.хх/32 pref-src=95.хх.хх.хх gateway=pppoe-ХХХ gateway-status=pppoe-ХХХ reachable distance=0 scope=10

 4 A S  dst-address=192.168.0.0/24 gateway=ether10 gateway-status=ether10 reachable distance=1 scope=30 target-scope=10

 5 ADC  dst-address=192.168.0.254/32 pref-src=192.168.0.254 gateway=ether10 gateway-status=ether10 reachable distance=0 scope=10

 6   S  dst-address=192.168.100.0/24 pref-src=10.62.69.222 gateway=10.62.69.254 <b>gateway-status=10.62.69.254 unreachable</b> check-gateway=arp distance=2
        scope=30 target-scope=10

    
 > ip route nexthop print detail
 0 address=10.62.69.254 gw-state=unreachable forwarding-nexthop="" interface="" scope=10 check-gateway=arp gw-check-ok=no

 1 address=89.хх.хх.хх gw-state=reachable forwarding-nexthop="" interface="" scope=10 check-gateway=none

 > ping 192.168.100.3
HOST                                     SIZE TTL TIME  STATUS
192.168.100.3                                           timeout
192.168.100.3                                           timeout
    sent=2 received=0 packet-loss=100%

The question is, why is gw-state=unreachable in the 6th entry of the routing table and in the 0th in the output of ip route nexthop print and what am I doing wrong?

Answer 1

I solved the problem, it was in my own inattention, but Mikrotik also gave a surprise.
If you specify an address for an interface without a mask, then a route to the 10.62.69.0/24 network will not be created. Moreover, if you try to create an interface without a mask through Winbox - there is no swearing, but if through the CLI - it swears at a null mask:
> ip address add address=10.62.69.222 network=10.62.69.0 interface=ether9
failure: netmask cannot be /0
I, in this case, created the route manually - and nothing worked:
1 AS dst-address=10.62.69.0/24 gateway=ether9 gateway-status=ether9 reachable distance=1 scope=30 target-scope=10
2 ADC dst-address=10.62.69.222/32 pref-src=10.62.69.222 gateway=ether9 gateway-status=ether9 reachable distance=0 scope=10
5 ADC dst-address=192.168.0.0/24 pref-src=192.168.0.254 gateway=ether10 gateway-status=ether10 reachable distance=0 scope=10
ip address add address=10.62.69.222/24 network=10.62 .69.0 interface=ether9
then the route appears:
1 ADC dst-address=10.62.69.0/24 pref-src=10.62.69.222 gateway=ether9 gateway-status=ether9 reachable distance=0 scope=10
and everything works great.

Answer 2

интерфейс укажите на маршруте в ту подсеть
и раз пингуется с микротика шлюз, то должно работать
а обратный маршрут то прописан?