Can't get Mikrotik RouterOS 4.2 to use default route

RouterOS Forwarding Protocols
1

What could be wrong with an active route with distance 1? Why won’t this router use it? Why does it insist on using a route with distance 200?

Here is the routing table:

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            DISTANCE
 0 X S  0.0.0.0/0                          63.201.69.217      255     
 1 A S  0.0.0.0/0                          10.12.7.85         1       
 2 ADb  0.0.0.0/0                          10.100.10.1        200     
 3 ADC  10.0.0.0/16        10.0.0.1        lan                0       
 4 ADb  10.1.0.0/16                        10.100.10.1        200     
 5 A S  10.7.16.0/21                       10.12.7.85         1       
 6 ADC  10.12.7.84/30      10.12.7.86      ether1             0       
 7 ADC  10.100.10.0/24     10.100.10.254   wan                0       
 8  Db  10.100.10.0/24                     10.100.10.1        200     
 9 ADb  10.100.12.0/24                     10.100.10.1        200     
10 ADb  10.224.27.8/32                     10.100.10.1        200     
11 ADb  10.224.27.9/32                     10.100.10.1        200     
12 ADb  10.252.0.0/24                      10.100.10.1        200     
13 ADC  63.201.69.216/29   63.201.69.219   inet_dsl           0       
14 ADC  172.16.0.0/24      172.16.0.9      rich_phone_br      0       
15 ADb  172.20.0.0/24                      10.100.10.1        200     
16 ADb  172.20.10.0/30                     10.100.10.1        200     
17 ADb  172.20.12.0/30                     10.100.10.1        200     
18 ADb  172.20.12.1/32                     10.100.10.1        200     
19 ADC  192.168.100.0/24   192.168.100.254 lan                0       
20 ADb  192.168.101.0/24                   10.100.10.1        200

And this is how the router actually gets to an arbitrary Internet address:

> /tool traceroute 8.8.8.8
     ADDRESS                                    STATUS
   1     10.100.10.1 1ms 3ms 2ms 
   2     172.20.10.1 247ms 169ms 311ms 
   3      172.20.0.1 255ms 184ms 215ms 
   4      172.20.0.2 202ms 260ms 360ms 
   5   67.203.117.33 388ms 419ms 427ms 
   6   100.43.223.69 432ms 452ms 433ms 
   7   100.43.223.69 444ms 390ms 487ms 
   8    4.53.178.213 432ms 535ms 541ms 
   9    4.69.144.207 507ms timeout timeout 
  10      4.68.71.18 timeout 566ms 638ms 
  11  209.85.248.185 561ms timeout 242ms 
  12     72.14.238.0 300ms 415ms 414ms 
                      mpls-label=568021 exp=4
  13   72.14.239.157 416ms 413ms 469ms 
                      mpls-label=419961 exp=4
  14  64.233.174.131 473ms 510ms 584ms 
  15         0.0.0.0 timeout timeout timeout 
  16         8.8.8.8 641ms 654ms 651ms

This would be OK if the route the router insists on using weren’t malfunctioning and limited to 2 Mbps in the best of cases, and the route I’m trying to get it to use weren’t offering a full 10 Mbps,

Thanks!

2

I figured it out: the problem was the routing mark I’d put on the route. Silly me, I thought it was just like a comment, didn’t realize the router would use it to qualify traffic for the route.