Re: looping traceroutes

[Ratul Mahajan <ratul () cs washington edu>]

>  >27  208.63.128.3 (208.63.128.3)  111.475 ms  69.670 ms  69.267 ms
>  >28  208.63.128.1 (208.63.128.1)  68.883 ms  67.147 ms  72.106 ms
>  >29  208.63.128.3 (208.63.128.3)  69.842 ms  67.889 ms  66.944 ms
>  >30  208.63.128.1 (208.63.128.1)  70.986 ms  73.124 ms  68.452 ms
>
> This looks exactly like a routing loop to me.  Why do you think it is not a 
> routing loop?

I was assuming that any routing loop in the system would be transient, but
this one is not (the traceroute is still showing the same behavior). The
extent to which I see this also makes me think that there is something
else going on.

Do you think that it can be a real persistent routing loop (data packets
would actually shuttle between the two interfaces) as against some
wierdness because of traceroute?

        thanks,
        -- ratul