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