Routing
Highlighted
Routing

Problem Accessing Certain WebSite

[ Edited ]
‎10-24-2012 02:27 AM

Hi,

 

I need some help to troubleshoot the problem.

 

My router connected to 2 ISP and both run BGP. Received full routing table.

 

I've check the routing bgp adverstise and receive and seems to me ok as i can see all the routing table listed. For example not able to ping to the websites from the pc, when ping i can get the ip of the web(106.10.170.118) and also not able to ping using the ip address.

 

ping www.yahoo.com

Pinging ds-sg-fp3.wg1.b.yahoo.com [106.10.170.118] with 32 bytes of data:

Request timed out.
Reply from a.b.c.d: Destination net unreachable.
Reply from a.b.c.d: Destination net unreachable.
Reply from a.b.c.d: Destination net unreachable.

Ping statistics for 106.10.170.118:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms


ping 106.10.170.118

Pinging 106.10.170.118 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 106.10.170.118:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 

One more thing fr example when i ping from router to yahoo it reply something like this

no route

ping6:wrote ds-eu-fp3.wa1.b.yahoo.com 16 char, ret=1

 

=> why it reply ping6? this is command fr ipv6 right?

 

Same problem when accessing some of the websites.

 

May i know whats the possiblities of the problem.

 

Is it somethg to do with the routing or DNS? How can i check further on my side just to ensure the problem is it from my side or ISP.

 

Please help me further.

 

Thank you.

 

Regards,

chenoi

1 REPLY 1
Highlighted
Routing

Re: Problem Accessing Certain WebSite

‎11-09-2012 03:07 PM

In your first ping, the output indicates (a.b.c.d) does not have a route to that destination.  So it returns the icmp net unreach.  The second ping simply times out.  So, we do not know.  Possibly try a traceroute to see how far you get.

 

In the third ping, it appears the namserver that router is configured for is getting a AAAA record for yahoo (ipv6).  So, it tries to reach that first.

 

None of your output indicates a dns problem.  The first one points to a routing problem on a downstream device (a.b.c.d).

Feedback