cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3081
Views
0
Helpful
2
Replies

Strange results from ping and traceroute over VPN

I have 2 Cisco 800's connected to each other with a VPN

One  thing that puzzles me - although I can ping and tracert between devices  on either side of the VPN I get a strange response from the remote  router when trying TraceRt to a remote server.

eg:

Server1: 192.168.50.10

Router1: 192.168.50.252

Router2: 10.10.10.1

Server2: 10.10.10.10

Ping from Server1 -> 10.10.10.10 - ok - response time ~33ms

Ping from Server1 -> 192.168.50.252 - ok - response time <1ms

Ping from Server1 -> 10.10.10.1 - ok - response time ~33ms

TraceRt from Server1 -> 10.10.10.1

Tracing route to 10.10.10.1 over a maximum of 30 hops
   1     1 ms    <1 ms     1 ms  192.168.50.252
   2    31 ms    34 ms    32 ms  10.10.10.1
Trace complete.

TraceRt from Server1 -> Server2

Tracing route to 10.10.10.10 over a maximum of 30 hops
   1    <1 ms    <1 ms    <1 ms  192.168.50.252
   2     *        *        *     Request timed out.
   3     *        *        *     Request timed out.
   4     *        *        *     Request timed out.
   5     *        *        *     Request timed out.
   6    31 ms    31 ms    32 ms  10.10.10.10
Trace complete.

Why am I getting these timeouts?

2 Replies 2

I have the following route line stated in the config

ip route 10.10.10.0 255.255.255.0

and the opposite one on the other router ...

cadet alain
VIP Alumni
VIP Alumni

Hi,

You're going through an IPSec VPN and so traffic from server1 to server2 is interesting traffic and is encrypted so when it hits router 2 it is dropped.

In your first traceroute you were going from server1 to router 2 and so the traffic was not going through the tunnel.

Regards.

Alain.

Don't forget to rate helpful posts.
Review Cisco Networking products for a $25 gift card