While trying to solve my chronical DNS timeout problems when querrying my
parent server at 204.122.16.13 (eskimo.com), I have run traceroute from the
hosts on my LAN, as well as in the opposite direction and noticed the
following:
When running traceroute from the host on the Internet to my PM-2ER, the
route is newer completed. Tracking route into other hosts on the Internet
is completed almost always. The traceroute dump below is a typical
situation.
Find route to: 207.54.20.2 (207.54.20.2), Max 30 hops, 40 byte packets
1 198.68.184.68 (198.68.184.68): 175 ms 162 ms 343 ms
2 198.68.184.65 (198.68.184.65): 156 ms 161 ms 156 ms
3 144.228.73.9 (144.228.73.9): 197 ms 191 ms 190 ms
4 144.228.70.2 (144.228.70.2): 199 ms 237 ms 200 ms
5 144.228.10.25 (144.228.10.25): 195 ms 199 ms 197 ms
6 144.228.40.13 (144.228.40.13): 208 ms 233 ms 210 ms
7 144.228.140.70 (144.228.140.70): 307 ms 228 ms 259 ms
8 204.122.31.23 (204.122.31.23): 311 ms 246 ms 276 ms
9 * * *
10 to 29 repeats the same -> * * *
30 * * *
*Maximum Hop Count Exceeded!!*
207.54.20.2 is a host on my LAN.
The PM WAN address is 204.122.31.23
Ethernet address of the PM is 207.54.20.1
The situation is very simillar when I run traceroute on my local:
Find route to: apple.com. (130.43.2.2), Max 30 hops, 40 byte packets
1 207.54.20.1 (207.54.20.1): 1 ms 1 ms 1 ms
2 204.122.31.1 (204.122.31.1): 25 ms 26 ms 28 ms
3 144.228.140.69 (144.228.140.69): 47 ms 47 ms 65 ms
4 144.228.40.1 (144.228.40.1): 47 ms 46 ms 47 ms
5 206.157.77.65 (206.157.77.65): 61 ms 54 ms 57 ms
6 166.48.19.250 (166.48.19.250): 92 ms * *
7 166.48.19.250 (166.48.19.250): 437 ms 411 ms 271 ms
8 131.119.0.204 (131.119.0.204): 119 ms 123 ms *
9 131.119.26.30 (131.119.26.30): 191 ms * 96 ms
10 205.180.175.29 (205.180.175.29): 92 ms 105 ms 99 ms
11 * 130.43.9.9 (130.43.9.9): 77 ms 78 ms
12 * * *
13 to 29 repeats the same -> * * *
30 * * *
*Maximum Hop Count Exceeded!!*
Any ideas?
Alexander