Does anyone know if I can use traceroute on a vpn connection to see if everything on my end is working ok?
I ran ipsec eroute and it shows the tunnel is up and passing traffic to it but just curious what all tests that I can run on them.
On 16 Jan 2006, at 8:47 PM, Andrew Rice wrote:
Does anyone know if I can use traceroute on a vpn connection to see if everything on my end is working ok?
I ran ipsec eroute and it shows the tunnel is up and passing traffic to it but just curious what all tests that I can run on them.
I might be talking out of my arse here but would traceroute -i <specify interface> work?
James
hmm I tried that but it didnt seem to want to let me specify the interface just printed out the options for traceroute...
| | On 16 Jan 2006, at 8:47 PM, Andrew Rice wrote: | | >Does anyone know if I can use traceroute on a vpn connection to | >see if everything on my end is working ok? | > | >I ran ipsec eroute and it shows the tunnel is up and passing | >traffic to it but just curious what all tests that I can run on | >them. | | I might be talking out of my arse here but would traceroute -i | <specify interface> work? | | James | | _______________________________________________ | CentOS mailing list | CentOS@centos.org | http://lists.centos.org/mailman/listinfo/centos
On 16 Jan 2006, at 8:59 PM, Andrew Rice wrote:
hmm I tried that but it didnt seem to want to let me specify the interface just printed out the options for traceroute...
Sorry Andrew, my bad. I had a connection via OpenVPN to a remote server and did the test quickly ... from a Mac. Was lost in other shell stuff and forgot I wasn't on the same platform as you this time. Can you do anything with ping -R (I'm sure that's universal) to record the route and see what happens. Other than that I'm lost on what you could try.
Apologies, James
Well thanks for the help anyhow James..just wondering why this vpn route isnt working. getting some errors such as Informational Exchange message for an established ISAKMP S A must be encrypted and ignoring vendor payload.
| | On 16 Jan 2006, at 8:59 PM, Andrew Rice wrote: | | >hmm I tried that but it didnt seem to want to let me specify the | >interface | >just printed out the options for traceroute... | | Sorry Andrew, my bad. I had a connection via OpenVPN to a remote | server and did the test quickly ... from a Mac. Was lost in other | shell stuff and forgot I wasn't on the same platform as you this | time. Can you do anything with ping -R (I'm sure that's universal) to | record the route and see what happens. Other than that I'm lost on | what you could try. | | Apologies, | James | | _______________________________________________ | CentOS mailing list | CentOS@centos.org | http://lists.centos.org/mailman/listinfo/centos
On Tue, 2006-01-17 at 00:35 +0800, James Gallagher wrote:
On 16 Jan 2006, at 8:59 PM, Andrew Rice wrote:
hmm I tried that but it didnt seem to want to let me specify the interface just printed out the options for traceroute...
Sorry Andrew, my bad. I had a connection via OpenVPN to a remote server and did the test quickly ... from a Mac. Was lost in other shell stuff and forgot I wasn't on the same platform as you this time. Can you do anything with ping -R (I'm sure that's universal) to record the route and see what happens. Other than that I'm lost on what you could try.
Apologies, James
If you have a VPN established and routing setup correctly then a traceoute will show only the main gateway for the VPN and the other endpoint ... then any other routes after that.
Like this:
[johnny@myth kernel]$ traceroute 192.168.169.40 traceroute to 192.168.169.40 (192.168.169.40), 30 hops max, 38 byte packets 1 192.168.10.3 (192.168.10.3) 0.720 ms 0.424 ms 0.369 ms 2 192.168.168.40 (192.168.169.40) 89.227 ms 87.933 ms 114.058 ms