Home > IT Answers > Development > Able to ping L3 VPN but unable to tracepath
SearchEnterpriseWAN
250 pts.
 Able to ping L3 VPN but unable to tracepath
Linux hosting, L3 VPN, BGP
I am running an L3 VPN between 2 edge routers and have connected one router to a client (Linux Host). I tried pinging from the client an IP address (present on the other router) that was learnt via BGP VPN. It's pinging, but I am unable to do tracepath from the client. It gives me a "No Reply" after it goes to the interface of the router connected to the client. Why is this happening? Could anyone please explain this behavior?
ASKED: Feb 14, 2012  8:07 PM GMT
UPDATED: March 2, 2012  6:23:07 PM GMT
RELATED QUESTIONS
TessaLP
390 pts.
Answer Wiki:
SearchEnterpriseWAN.com's resident VPN expert, Rainer Enders, has responded to your question here: Why am I able to ping but not do tracepath over my Layer 3 VPN?
Last Wiki Answer Submitted:  Mar 1, 2012  3:14 PM (GMT)  by  TessaLP   390 pts.
To see other answers submitted to the Answer Wiki View Answer History.
RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



 

Just try the command as: man tracepath, and hope u’ll get ur ans from there. R u trying traceroute and what it replied, with this u can get a maximum number of hops.

Rechil
 20,980 pts.
 

Could your problem be connected with some UDP filtering and/or ICMP reply prohibition on the router?

Petkoa
 3,060 pts.