Reachable gateway marked as unreachable

RouterOS General
1

Hello
I have to use a gateway which is not on the local network (virtualized environment).
Local ip address is 46.105.62.97 (eth1)
Gateway address is 37.187.139.254, reachable via eth1.

So i put a route to 37.187.139.254 via eth1, then added default route via 37.187.139.254. Problem is that route is not active, marked as unreachable.. It is reachable.
How can i force that route to be active?

Thanks

Routing Failover without Scripting
2

The rule can not be active, because the GATEWAY must be directly connected to the same “LAN”.

For Ex.

Routerboard 1.1.1.1/24
Router2 1.1.1.2/24
Gateway 3.3.3.3/24

If you want use 3.3.3.3/24 as gateway, you can not directly:
The gateway must be set to 1.1.1.2/24
and inside Router2 must be set to 3.3.3.3/24

3

I understand that, but that kind of configuration works with Windows or Linux.. as long as you have a route to your gateway, you can use this gateway even if it’s not in the local LAN

4

Fixed!

As stated in http://forum.mikrotik.com/t/ros-on-kvm-on-hosted-server-issue-dedibox-online-net/54695/1
the trick is to put the gateway as ether1 network, so Routerboard thinks that the gateway is on the LAN…

/ip address
add address=46.105.62.97/32 interface=ether1 network=37.187.139.254

/ip route
add distance=1 gateway=37.187.139.254
Default gateway from a different subnet marked unreachable
5

You need to adjust scope and target scope of default route, so that its gateway is recursively reachable over static route.

6

Thanks mrz I’m afraid i’m not sure to fully understand your sentence, what do you mean by “adjusting”?

Here is my current routing table

> 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 A S  dst-address=0.0.0.0/0 gateway=37.187.139.254 gateway-status=37.187.139.254 reachable via  ether1 distance=1 scope=30 target-scope=10 

.... L2TP & EoIP routes...

20 ADC  dst-address=37.187.139.254/32 pref-src=46.105.62.97 gateway=ether1 gateway-status=ether1 reachable distance=0 scope=10
7

You can read more in this article with example
http://wiki.mikrotik.com/wiki/Manual:Using_scope_and_target-scope_attributes

8

Ping it from windows and see what the TTL is.

If it’s for example, 30:
On that route, set scope to 64 and target scope also 64. Or try higher. Until it says “reachable recursive”.

Windows has automatic scope. Mikrotik does not. So funny. So we have to work extra and do it manually. But it can be dangerous, as you can cause loops.

9

Probably after 6-7 years the problem is solved.