Just sent in a support file.
Hello Folks!
Routing marks does not work for us in either RoS6.9 or RoS6.10 last known working is RoS6.7
We do not use any PING or ARP for the Routing marks, they are there for static policy routing on protocol and source server.
Default GW points in another direction than those policy routed routes. And yes, the networks inside MT router is vlan:s.
Routing marks for policy based routing that do not use ping and arp to keep them up or something does not work since RoS6.7.
I has before that been working for 5-6 years, something has been broken in RoS regarding routing marks, that is 100% sure, no matter!
A supout file has been generated for MT and they have replyed to it as not reproducable, and asked for a test setup to login and try, we asked them to come back with a date for such test but so far they have not ansered back with test date.
Has there been any progress on this? I’m seeing these exact symptoms moving from 6.7 to 6.9, 6.10 or 6.11 (I don’t have 6.8 to test with). As mentioned here, downgrading to 6.7 resolves the issue again.
Do I need to also contact support? Multiple route tables is kinda crucial to my config.
They are working in my setups for 6.10 and 6.11 (and where broken on 6.9, at least on RB450).
Checked on RB450G, 750GL, 951Hnd, CRS-125 and RB1100AH2x.
Please see this post and raise a bug ticket if necessary. The post contain step by step how to reproduce as well as video show how to reproduce.
http://forum.mikrotik.com/t/radius-server-not-working-in-2-8-11/127/1
As I stated in the post above, these problems seem to be solved in 6.10 and 6.11.
My problem is back with 6.15…
with routing mark:
3 S dst-address=0.0.0.0/0 gateway=192.168.3.20 gateway-status=192.168.3.20 inactive check-gateway=ping distance=1 scope=30 target-scope=10 routing-mark=Closeness
when I remove the routing mark:
1 S dst-address=0.0.0.0/0 gateway=192.168.3.20 gateway-status=192.168.3.20 reachable via Closeness check-gateway=ping distance=1 scope=30 target-scope=10
Every automatic upgrade cause this to my router’s with routing mark’s, dont know how.. My solution is rename the mark (add a ‘_’ or remove) and re-set the route to use the new mark, works fine but is disappointing.