Weird traceroute output.

[syancy]

Has someone ever seen or explain why I when I do a traceroute I get returns from 2 interfaces one after another up to the max 30 hops. Here is an excerpt:

192.168.146.16 (192.168.146.16) 12.450 ms 11.835 ms 11.992 ms 20

192.168.146.32 (192.168.146.32) 14.544 ms 14.117 ms 15.560 ms 21

192.168.146.16 (192.168.146.16) 14.124 ms 15.594 ms 14.280 ms 22

192.168.146.32 (192.168.146.32) 16.334 ms 15.880 ms 14.187 ms 23

192.168.146.16 (192.168.146.16) 15.636 ms 14.175 ms 15.702 ms 24

192.168.146.32 (192.168.146.32) 17.588 ms 14.767 ms 19.205 ms 25

192.168.146.16 (192.168.146.16) 15.582 ms 14.287 ms 15.400 ms 26

192.168.146.32 (192.168.146.32) 16.033 ms 17.950 ms 16.509 ms 27

192.168.146.16 (192.168.146.16) 18.921 ms 16.195 ms 17.952 ms 28

192.168.146.32 (192.168.146.32) 17.599 ms 17.637 ms 19.910 ms 29

192.168.146.16 (192.168.146.16) 16.520 ms 18.235 ms 21.203 ms 30

192.168.146.32 (192.168.146.32) 19.504 ms 20.033 ms 19.842 ms

[dnewell24]

This is a routing loop. 192.168.146.16 thinks the destination of IP tracrt packet can be found via 192.168.146.32. 192.168.146.32 thinks the destination of the IP tracrt packet can be found via 192.168.146.16.

If you have access to both devices issue a show ip route x.x.x.x (destination ip or network of the tracrt packet). There should be a route with a next hop IP of each other in both routers. If the show ip route responds with "network not in table" then check your default routes. Once you find the erroneous route correct it.