08-30-2022 11:02 PM - edited 08-31-2022 12:00 AM
Hi,
I feel like I am doing some obvious mistake but I cannot figure it out for the life of me. I have a lab with 2 router A and B between those 2 router I am using an iBGP istance to advertise routes to each other.
Router A ID is 192.168.0.141
Router B ID is 192.168.0.140
On router A I have configured on an interface the 192.168.0.186/28 ip address. Connected to this interface there's a device with the ip address of 192.168.0.183. This device can be pinged from router A just fine.
From Router B however, I am unable to do so. A "show ip route 192.168.0.183" shows me this:
show ip route 192.168.0.183
Routing entry for 192.168.0.176/28
Known via "bgp 65535", distance 200, metric 0, type internal
Last update from 192.168.0.141 00:02:24 ago
Routing Descriptor Blocks:
* 192.168.0.141, from 192.168.0.141, 00:02:24 ago
Route metric is 0, traffic share count is 1
AS Hops 0
MPLS label: none
So the network is being advertised just fine and the route to it is installed in the routing table by Router B but, trying to ping 192.168.0.183 fails. If I try to ping the interface on router A (192.168.0.186) the ping works just fine. I cannot figure out why this is happening. If I reach the interface that is in the same network I should by all means be able to reach anything on the same subnet but that's not happening.
Can anyone advise?
Thank you
08-31-2022 12:42 AM
Hello
Its due to IBGP loop prevention, An IBGP learned route is not advertised to another IBGP peer as part of the inbult a loop
prevention mechanism.
Redistribute that internal subnet into bgp or make the two rtrs ebgp peers.
08-31-2022 01:29 AM
Hi Paul,
thanks for the reply but I am not sure I am following you. Router A learns the route because it's directly connected to it. It then advertises it to its only iBGP neighbor Router B. It was my understanding that loop prevention would prevent a router to redistribute routes it learned from another iBGP neighbor to another iBGP neighbor but in this case, there are just 2 routers.
Additionally, if it was loop prevention kicking in, how does router B manages to install the route to the subnet in its routing table? From router B I can ping the interface on Router A that has the server directly connected just fine but, I cannot ping the server directly
08-31-2022 04:22 AM
the device you connect
1- config with default GW
2- config with default route
the device can not know path for return traffic.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide