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