cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
858
Views
0
Helpful
4
Replies

Strange routing behavior unable to ping from router

yassine_hell
Level 1
Level 1

Hello everyone, 

Im trying to implement this small network:

What i want to do is to ping from "Bizerte" router to "Berlin" Router, i configured OSPF and BGP, and distributed the BGP into OSPF

Viewing the Bizerte routing table and Berlin routing table everything seems fine, 

But when i try to ping, it always fail,

I tried to traceroute from Bizerte to Berlin, and the packets seems to stop at the TTCore4 router, and at the Telefonica1 router on the other way(from berlin to bizerte)

here is a screen showing the routing table and the ping/traceroute

Then i tried to lunch the 2 virtual machines, and tried to ping & traceroute from VM to VM and both worked fine, and gave me the correct routes, even from VM to router worked.

why cant i ping from router to router or router to VM, but i can from VM to VM or from VM to router?

you can find attached the configuration files for the Berlin, Bizerte, TTCore4 and Telefonica1 routers incase someone needed them.

1 Accepted Solution

Accepted Solutions

You are not advertising the IP subnets via BGP for the router interfaces

So when Bizerte tries to ping 172.16.5.129 the source IP is 10.0.0.50 but you are not advertising 10.0.0.48/30 via BGP which means your traceroute isn't working..

And the same goes for the Berlin router the other way.

You need to add "network ..." statements for those subnets or just use extended ping and use the 172.16.x.x interface on each router as the source of the ping and it should work.

For future troubleshooting always work out what the source IP will be and then check the routing tables of all routers in the path to make sure they have routes.

If you check either of the core routers running BGP then you will see that they do not know about those subnets for the remote AS.

Jon

View solution in original post

4 Replies 4

I can't see the diagram properly even with magnifier, can you post as a separate picture

Hi, thank you for your reply, i attached the diagram below, but you can also right click the image and select "Open image in new Tab" and you'll the original sized picture.

You are not advertising the IP subnets via BGP for the router interfaces

So when Bizerte tries to ping 172.16.5.129 the source IP is 10.0.0.50 but you are not advertising 10.0.0.48/30 via BGP which means your traceroute isn't working..

And the same goes for the Berlin router the other way.

You need to add "network ..." statements for those subnets or just use extended ping and use the 172.16.x.x interface on each router as the source of the ping and it should work.

For future troubleshooting always work out what the source IP will be and then check the routing tables of all routers in the path to make sure they have routes.

If you check either of the core routers running BGP then you will see that they do not know about those subnets for the remote AS.

Jon

yassine_hell
Level 1
Level 1

That's the exact behavior that i wanted, did not know about the extended ping, and just found out that the default destination source is the outgoing interface address.

Thank you.