Hi, I've specivied a reachable subnet by the next hop, this hop is pingable from both sides (so why it shows "unreachable"?), on both sides the interface is declared LAN, from the hop I can ping a remote subnet on the first route.. so why the first route doesn't want to see a remote subnet on the hop?
The main router is a CHR @ 7.21.3
On main route the default route has distance 2, the desidered subnet is also on the main table with distance 1, there are no other subnets overlapping, there is no reason to behave like this.
How a gateway is declared unreachable? There is a particular discover protcol that Mikrotik uses and it may on the next hop be unanswered? This is a mistery
Thank you for help!
Check the scope and target-scope values of the routes (make those columns as well as the Immediate Gateway column visible in WinBox, if using the print command in Terminal then include the columns in proplist).
See the diagram in this thread for the required relationship between scope and target-scope:
It's also more helpful if you can also put the output of /ip route print (with the 3 extra columns included).
thank you dear friend, putting the targing scope to 10 as the scope is set, solved the problem- I don't know why this parameter was changed from default, strange.
Now the route is back to AS 