Routing, Traceroute, who's up for a challenge?
Posted on 2004-04-16
Let's say your internal subnet is 220.127.116.11, your default gateway to the Internet is 18.104.22.168. You seem to be able to run a trace to every other subnet in the world that allows it. In particular, 22.214.171.124, you can trace to 126.96.36.199. you can trace to every subnet on 188.8.131.52 but one. When you try and run a trace to 184.108.40.206, the response you get makes it appear that 220.127.116.11 is inside your network. It never seems to hit our gateway 18.104.22.168.
example traceroute 22.214.171.124
replys 126.96.36.199 which is what I expect, my gateway, the first hop.
188.8.131.52 gateway address on the router, this is good, and on to success.
problem child example traceroute 184.108.40.206
replys 220.127.116.11 this is not good.
18.104.22.168 and again repeatedly until it hits 30 hops and stops.
nslookup 22.214.171.124 returns a domain not found.
I can't ping 126.96.36.199, (destination net unreachable) but I can ping the other 188.8.131.52.
I've examined the routing table on the servers and routers we control and find no trace of 184.108.40.206, or 220.127.116.11.
Level 3 manages the router that connects us to the Internet. They say that they can run a trace from the router to 18.104.22.168.
I've added a static route to 22.214.171.124 on the gateway, still no luck.
Who has suggestions on a cause and solution or troubleshooting tips?