BGP route error in Routing table

[NayAungLin7876]

From the R1 cannot ping to R3's loopback 192.168.5.1 although R1 have the route in routing table. And then R4 also cannot ping to R2's loopback 192.168.3.1 and R4 have no route in routing table for them. When I check R4 bgp table it show:

r i 192.168.3.0 192.168.34.2 0 100 0 100 i
r>                    192.168.13.1 0 100 i
*>i 192.168.5.0 192.168.34.2 0 100 0 i

R1

router bgp 100
bgp log-neighbor-changes
neighbor 192.168.12.2 remote-as 100
neighbor 192.168.12.2 next-hop-self
neighbor 192.168.13.2 remote-as 200

R2

router bgp 100
bgp log-neighbor-changes
network 192.168.3.0
neighbor 192.168.12.1 remote-as 100
neighbor 192.168.12.1 next-hop-self
neighbor 192.168.24.2 remote-as 200

R4

router bgp 200
bgp log-neighbor-changes
neighbor 192.168.13.1 remote-as 100
neighbor 192.168.34.2 remote-as 200
neighbor 192.168.34.2 next-hop-self

R3

router bgp 200
bgp log-neighbor-changes
network 192.168.5.0
neighbor 192.168.24.1 remote-as 100
neighbor 192.168.34.1 remote-as 200
neighbor 192.168.34.1 next-hop-self

[Abzal · Accepted solution]

Hi,

It's because R2 doesn't know how to reach 192.168.13.0 subnet between R1-R4. If you put static route for example pointing like on R2:

ip route 192.168.13.0 255.255.255.252 192.168.12.1

it will work so that R2 knows the route for return path. Same thing applies for R1 because R3 doesn't know how to route packet back because it doesn't know a route to the subnet between R1-R4.

[NayAungLin7876]

For static route, it is ok for R1 to R3. But R4 have still have bgp route error and there is no route 192.168.3.0/24 in routing table. When check bgp table, it doesn't show "*" sign on 192.168.3.0/24. What would be issue for route failure?

[Cristian Matei]

Hi,

    A small diagram, even handmade, with how are the routers connected, which interconnects are used and what are the BGP peering would help.

Regards,

Cristian Matei.

[NayAungLin7876]

I upload the topology diagram