While out of the state last week I was not able to use ssh to access my office server. The hotel replaced their wifi with ethernet (yay, team!) so there was no problem obtaining an IP address from their provider's server. However, packets would go no further than a Frontier Communications server in Beaverton.
I would like to understand why I could ping the server (mail dot appl-ecosys dot com) by name or IP address (which I obtained using 'host' since Frontier changes it several times each evening and night), but traceroute and ssh failed to reach the same destination. Here are typical results running traceroute to both the host.domainname and IP address: traceroute mail dot appl-ecosys dot com # obfuscated in this message traceroute to mail dot appl-ecosys dot com (50.38.88.85), 30 hops max, 60 byte packets 1 192.168.0.1 (192.168.0.1) 42.949 ms 44.991 ms 45.164 ms 2 64-42-65-21.atgi.net (64.42.65.21) 46.603 ms 47.737 ms 48.830 ms 3 70.97.0.1 (70.97.0.1) 49.822 ms 50.419 ms 51.363 ms 4 pao.paix.frontiernet.net (198.32.176.27) 58.242 ms 58.974 ms 59.762 ms 5 ae2--0.cor01.plal.ca.frontiernet.net (74.40.3.149) 72.998 ms 74.469 ms 84.398 ms 6 74.40.1.226 (74.40.1.226) 144.296 ms 65.962 ms 66.228 ms 7 ae0---0.car01.tgrd.or.frontiernet.net (74.40.1.182) 70.655 ms 70.999 ms 73.825 ms 8 ae1---0.adr01.bvtn.or.frontiernet.net (74.42.151.138) 110.589 ms 111.971 ms 111.393 ms 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * traceroute 216.99.193.149 traceroute to 216.99.193.149 (216.99.193.149), 30 hops max, 60 byte packets 1 192.168.0.1 (192.168.0.1) 4.874 ms 6.524 ms 9.222 ms 2 64-42-65-21.atgi.net (64.42.65.21) 10.446 ms 27.930 ms 28.943 ms 3 70.97.0.1 (70.97.0.1) 52.117 ms 55.425 ms 56.254 ms 4 * tg9-1.ar10.ptldorfj.integra.net (209.63.114.154) 81.273 ms 82.310 ms 5 67.136.135.70 (67.136.135.70) 92.406 ms 96.759 ms 100.120 ms 6 * * * 7 * * * 8 * * * 9 * * * It is curious that traceroute fails at hop 8 for the name but at hop 5 for the IP address. N.B. The two IP addresses are the result of my saving the output on two different days and Frontier had changed it between attempts. My interpretation is that this is a telco issue. Is that correct? If so, is there anything I can do should this problem re-appear the next time I'm away from the office? Rich _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
