MikroTik RouterOS v2.9 Reference Manual page 132

# NETWORK
0 10.2.0.0/24
1 10.3.0.0/24
After all routers have been set up as described above, and the links between them are operational,
the routing tables of the three routers look as follows:
[admin@OSPF_MAIN] ip route> print
Flags: X - disabled, I - invalid, D - dynamic, J - rejected,
C - connect, S - static, r - rip, o - ospf, b - bgp
# DST-ADDRESS
0 Io 192.168.0.0/24
1 DC 192.168.0.0/24
2 Do 10.3.0.0/24
3 Io 10.2.0.0/24
4 DC 10.2.0.0/24
5 Io 10.1.0.0/24
6 DC 10.1.0.0/24
[admin@OSPF_peer_1] ip route> print
Flags: X - disabled, I - invalid, D - dynamic, J - rejected,
C - connect, S - static, r - rip, o - ospf, b - bgp
# DST-ADDRESS
0 Do 192.168.0.0/24
1 Io 10.3.0.0/24
2 DC 10.3.0.0/24
3 Do 10.2.0.0/24
4 Io 10.1.0.0/24
5 DC 10.1.0.0/24
[admin@OSPF_peer_2] ip route> print
Flags: X - disabled, I - invalid, D - dynamic, J - rejected,
C - connect, S - static, r - rip, o - ospf, b - bgp
# DST-ADDRESS
0 Do 192.168.0.0/24
1 Io 10.3.0.0/24
2 DC 10.3.0.0/24
3 Io 10.2.0.0/24
4 DC 10.2.0.0/24
5 Do 10.1.0.0/24
Routing tables with Revised Link Cost
This example shows how to set up link cost. Let us assume, that the link between the routers
OSPF_peer_1 and OSPF_peer_2 has a higher cost (might be slower, we have to pay more for the
traffic through it, etc.).
Page 118 of 695
Copyright 1999-2007, MikroTik. All rights reserved. Mikrotik, RouterOS and RouterBOARD are trademarks of Mikrotikls SIA.
Other trademarks and registred trademarks mentioned herein are properties of their respective owners.
AREA
local_10
local_10
G GATEWAY
r 0.0.0.0
r 10.2.0.1
r 10.1.0.1
r 0.0.0.0
r 0.0.0.0
G GATEWAY
r 10.1.0.2
r 0.0.0.0
r 10.1.0.2
r 10.3.0.2
r 0.0.0.0
G GATEWAY
r 10.2.0.2
r 0.0.0.0
r 0.0.0.0
r 10.3.0.1
r 10.2.0.2
DISTANCE INTERFACE
110
0 main_gw
110 to_peer_2
to_peer_1
110
0 to_peer_2
110
0 to_peer_1
DISTANCE INTERFACE
110 to_main
110
0 backup
110 to_main
backup
110
0 to_main
DISTANCE INTERFACE
110 to_main
110
0 to_peer_1
110
0 to_main
110 to_peer_1
to_main