What are possible reasons for route to be inactive

RouterOS General
1

I am setting some pretty straightforwart static routing on MT board, and ther eis one route that stays inactive for no apparent reason (at least I do not see any).

Rout may be inactive because there is other route with the sam scope but lower distance, thus having higher priority. Also, id static route is set but interface is inactive, that route will be inactive. Are there other reasons for static route to be inactive?

Here is my routing table

[me@MT] > /ip route print 
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 
 #      DST-ADDRESS       PREF-SRC       GATEWAY-STATE GATEWAY        DISTANCE INTERFACE   ROUTING-MARK
 0 A S  0.0.0.0/0                        reachable     188.12.128.1    1        wan-1       wan-1-route
 1 A S  0.0.0.0/0                        reachable     192.168.1.1     1        wan-2       wan-2-route
 2 A S  0.0.0.0/0                        reachable     80.174.164.249  1        pppoe-1     pppoe-1-route
 3   S  0.0.0.0/0                        reachable     10.80.0.1       1        pptp-1      pptp-1-route
 4  DS  0.0.0.0/0                        reachable     192.168.1.1     15       wan-2
 5 ADS  0.0.0.0/0                        reachable     188.12.128.1    10       wan-1
 6 A S  10.216.0.0/16                    reachable     10.216.6.33     1        llnk-21
 7 ADC  10.216.6.32/29     10.216.6.34                                 0        llnk-21
 8 A S  10.231.0.0/16                    reachable     10.216.6.33     1        llnk-21
 9 A S  10.50.10.0/24                    reachable     10.216.6.33     1        llnk-21
10 ADC  10.80.0.1/32      10.80.0.2                                   0        pptp-1
11 ADC  80.174.164.249/32  81.118.55.48                               0        pppoe-1
12 ADC  188.12.128.0/22    188.12.129.109                             0        wan-1
13 ADC  192.168.1.0/24    192.168.1.2                                 0        wan-2

There are two routes that are inactive. Route #4 is obvious, there is route #5 withthe same scope but shorter distance.

But, I have problem with route #3, it stays inactive no matter what I do. I checked gateway, it is pingable. There are no routes with the same scope and the same routing-mark. I see no reason why it should not be active.

Can someone exerienced check it out. Maybe I am overlooking something.

2

is version the latest? what if you reconnect that pptp?

3

It’s 3.30. Yes I tried lots of things but it just stays inactive.

4

Does it go active if you disable 0, 1, and 2, and can you verify that you can actually reach 10.80.0.1, in spite of what it says?

You may also want to look into putting all four of those routes in as one route with multiple gateways instead, not sure if that’s how 3.30 works though (unless you are doing something else that requires them to be separate).

5

It becomes active when I disable all other interfaces.

I cannot put them in one multiple gateways route as route are specific for marked connections

This 10.80.0.0/24 should route ony for marked connections. Thisg is if conection is market to this rute it simply does not match to any other route, so I do not understand why it is inactive. There is no other route tht may have higher priorty. And I checked - connections are marked.

Route is inactive and does not work. All connections that are marked to go through it, stil go through default gateway, used for not marked connections.

If I just remove routing-mark condition for this rule, it becomes active. Icannot understand why is that an issue? I have other pppoe connection set in exactly same manner and there is no problem.

6

Rather than disabling the interfaces, I was wondering if it became active when disabling the other routes (and if they all had to be disabled or only some of them).

When checking the above you may want to add a logging rule for topic=route and see if there are any messages pertaining to when/why the other route becomes active/inactive.

If that doesn’t help can you post output from /ip route export?

And do I understand correctly, you have another router set up the same way, which is working?

7

I solved problem.

I had typing error in route mark name in mangling rule. Route mark set in route was nonnexisting so thus Mikrotik, sets route inactive.

It would be really great if MT provides some hints on such occasions. This one was really hard to guess.