Static vs iBGP distance

Hi @Poseidonn ,

Can you run the following?

get router info routing-table details x.x.x.x

x.x.x.x is the routing entry for the network in this issue.

I tested it with 7.4.6. And looks like a newer route seems to be preferred.

When eBGP route for 10.0.9.0/29 preexists, I put in the same static route with AD 20. Then got below, overriden by the static route:

FortiGate-60F # get router info routing-t detail 10.0.9.0

Routing table for VRF=0
Routing entry for 10.0.9.0/29
  Known via "static", distance 20, metric 0, best
  * vrf 0 x.x.x.x, via wan1

Routing entry for 10.0.9.0/29
  Known via "bgp", distance 20, metric 0
  Last update 07:06:01 ago
    vrf 0 10.245.254.225 priority 1 (recursive via ny-corp tunnel x.x.x.x)

However, when I dropped the eBGP once then reintroduced it again, I got below, overriden by the eBGP route:

FortiGate-60F # get router info routing-t detail 10.0.9.0

Routing table for VRF=0
Routing entry for 10.0.9.0/29
  Known via "bgp", distance 20, metric 0, best
  Last update 00:03:24 ago
  * vrf 0 10.245.254.225 priority 1 (recursive via ny-corp tunnel x.x.x.x)

Routing entry for 10.0.9.0/29
  Known via "static", distance 20, metric 0
    vrf 0 x.x.x.x, via wan1

So, if you want the FGT to prefer iBGP route, try setting AD for the static route higher than 200, like 201.

Toshi

I know the topic is administrative distance, I put the routing table database in another post.

Thanks

you may find this one helpful: https://community.fortinet.com/t5/FortiGate/Technical-Tip-Multiple-Active-Concurrent-Default-Routes/ta-p/368427 

Even with the same administrative distance, static routes typically take precedence over dynamic routes like iBGP. You might also want to check route preference, longest prefix match Minecraft Bedrock Edition, and any route filtering or redistribution policies that could be affecting selection.