Hi Adam
Thanks for getting back to me!
On Sun, Jul 1, 2012 at 10:05 AM, Adam Bower adam@thebowery.co.uk wrote:
On Sun, Jul 01, 2012 at 05:23:16AM +0100, Paul Grenyer wrote:
inet addr:94.196.143.233 P-t-P:10.64.64.64 Mask:255.255.255.255What happens if you try to ping the P-t-P partner?
Just hangs:
ping 10.64.64.64 PING 10.64.64.64 (10.64.64.64) 56(84) bytes of data. ^X^C --- 10.64.64.64 ping statistics --- 89 packets transmitted, 0 received, 100% packet loss, time 88702ms
and then something like 8.8.8.8 (googles public dns servers),
This is better:
ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_req=1 ttl=53 time=192 ms 64 bytes from 8.8.8.8: icmp_req=2 ttl=53 time=182 ms 64 bytes from 8.8.8.8: icmp_req=3 ttl=53 time=183 ms 64 bytes from 8.8.8.8: icmp_req=4 ttl=53 time=182 ms 64 bytes from 8.8.8.8: icmp_req=5 ttl=53 time=172 ms 64 bytes from 8.8.8.8: icmp_req=6 ttl=53 time=172 ms 64 bytes from 8.8.8.8: icmp_req=7 ttl=53 time=171 ms ^C --- 8.8.8.8 ping statistics --- 7 packets transmitted, 7 received, 0% packet loss, time 6001ms rtt min/avg/max/mdev = 171.460/179.638/192.944/7.476 ms
from there can you do a traceroute?
What does the output of ip route say?
I just let it run for about a minute:
traceroute 8.8.8.8 traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets 1 172.31.62.137 (172.31.62.137) 158.243 ms 207.677 ms 247.622 ms 2 * * * 3 * * * 4 92.40.252.137 (92.40.252.137) 517.887 ms 190.140 ms 229.929 ms 5 * * * 6 209.85.240.61 (209.85.240.61) 350.102 ms 209.85.240.63 (209.85.240.63) 389.662 ms 86.431 ms 7 209.85.253.92 (209.85.253.92) 106.764 ms 209.85.253.90 (209.85.253.90) 116.654 ms 209.85.253.92 (209.85.253.92) 136.484 ms 8 209.85.243.33 (209.85.243.33) 146.315 ms 156.360 ms 169.569 ms