BGP Failover

I face a problem in BGP in Mikrotik. The thing is My computer is connected to a 450G router, which in turn connected to another RouterBoard 1100 router through two links, say Left and Right, using BGP. RouterBoard 1100 is connected to the internet. 450G is receving two default routes from 1100 and I am announcing 192.168.10.0/24 from 450G. By default it prefers Right path, as seen in the ip route table. when I increase the Local Preference of Left link the preferred path will be Left link as seen in the ip route table. But when I trace to google from my PC it is still going through Right link.

Is this a bug of Mikrotik or what? How to control outgoing traffic? Thing seems correct but not working.

Can anyone help me.

Outgoing traffic is controlled by default routes received from RB1100. Which default route is active, that link is used.

The route with the high local preference value is preferred and becomes active as seen in ip route table. I am seeing this and this is ok. but when I trace from my pc or from the 450G with src-address=192.168.1.1 (which is an IP in 450G and gateway to my PC) it is going through other link, not through the active link.
This is the problem sir!!!

post “/ip route print” from RB450 and RB1100

Here it is, First is 450G and Second is RB1100


[admin@R1] > 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 DISTANCE

0 ADb 0.0.0.0/0 192.168.2.2 20
1 Db 0.0.0.0/0 192.168.3.2 20
2 ADC 192.168.2.0/30 192.168.2.1 ether2 0
3 ADC 192.168.3.0/30 192.168.3.1 ether1 0
4 ADC 192.168.10.0/24 192.168.10.1 ether5 0
5 ADC 192.168.20.0/24 192.168.20.1 ether5 0
6 ADC 192.168.30.0/24 192.168.30.1 ether5 0
[admin@R1] >


[admin@R3] > 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 DISTANCE

0 A S 0.0.0.0/0 119.2.60.225 1
1 ADC 119.2.60.224/28 119.2.60.235 ether4 0
2 ADC 192.168.2.0/30 192.168.2.2 ether2 0
3 ADC 192.168.3.0/30 192.168.3.2 ether1 0
4 ADb 192.168.10.0/24 192.168.2.1 20
5 Db 192.168.10.0/24 192.168.3.1 20
6 ADb 192.168.20.0/24 192.168.2.1 20
7 Db 192.168.20.0/24 192.168.3.1 20

For your reference here is the trace report also

[admin@R1] > tool traceroute www.google.com src-address=192.168.10.1
ADDRESS STATUS
1 192.168.3.2 1ms 1ms 1ms
2 119.2.60.225 1ms 1ms 1ms
3 119.2.56.242 1ms 1ms 1ms
4 119.2.56.217 1ms 1ms 1ms
5 119.2.56.154 1ms 1ms 1ms
6 202.79.197.30 86ms 86ms 86ms
7 209.85.243.156 86ms 89ms 86ms
8 72.14.233.107 86ms 87ms 86ms
9 72.14.254.104 86ms 86ms 88ms
[admin@R1] >

Try with adding a +2 prepend on the unwanted peer

It works in that way, but as per the BGP standard, you know path prepend is used to influence incoming traffic and Local Preference is used to influence outgoing traffic. Why Mikrotik is not following this standard?