On Fri, Apr 12, 2002 at 04:04:42PM -0400, Bradley Corner wrote:
I tried to notify UUNET at their 800-900-0241 number that there was a loop in their network. They told me that if I didnt have an account with them they were not interested in any information that I may have had for them. I stated that I was just calling so that they could pass the information onto an engineer. He repeated himself saying if you do not have an account with us I will not do anything with the information. I guess they think they run the internet and us small ISPs couldnt possibly know anything...
I don't think this is a UUnet problem. -snip-
12 | 65.195.230.218 | core62007-gw.customer.alter.net 13 | 162.33.130.4 | i97.toad.net 14 | 162.33.128.249 | tiara-2-balto.ds1.toad.net 15 | 205.197.182.201 | max2.toad.net 16 | 162.33.138.129 | mmsi-cpe.dsllan.toad.net 17 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET 18 | 65.195.230.218 | core62007-gw.customer.alter.net 19 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET 20 | 65.195.230.218 | core62007-gw.customer.alter.net -snip-
To me, it looks like the customer has no internal route for this address and is defaulting to UUnet. The customer's default is the cause of the apparent loop, not anything UUnet is doing. Judging by the various toad.net hops before the loop becomes apparent, this may be caused by route instability inside the customer's network. Either way, this is not a UUnet issue. Their policies aside, I'm not sure what you want them to do about this. Incidentally, normal UNIX-style traceroute formats much better for email. --msa