jrr@SCAMP.CONCERT.NET (Joe Ragland) (12/03/89)
To someone at Proteon that might like to reply: 128.167.9.1 is a serial line interface on the UT-Knoxville SURAnet p4200 connected to 128.167.9.2 serial line interface on the Univ. of Kentucky p4200. My question is why does p4200 routing zip through UT-Knoxville and do a bank shot off UKY and back to UTK when I attempt to route to the UTK address as follows? Script started on Sat Dec 2 17:30:28 1989 scamp# tracerouter 128.167.9.1 traceroute to 128.167.9.1 (128.167.9.1), 30 hops max, 40 byte packets 1 * suranet-gw.concert.net (128.109.193.3) 18 ms 19 ms 2 clemson-u.sura.net (128.167.5.2) 56 ms 55 ms 222 ms 3 georgia-tech.sura.net (128.167.6.2) 2806 ms 320 ms 193 ms 4 alabama-birmingham-u.sura.net (128.167.7.2) 202 ms 112 ms 113 ms 5 u-tennessee.sura.net (128.167.8.2) 469 ms 4981 ms 150 ms 6 u-kentucky.sura.net (128.167.9.2) 171 ms 2654 ms 220 ms 7 u-tennessee.sura.net (128.167.9.1) 263 ms 373 ms 351 ms scamp# exit scamp# script done on Sat Dec 2 17:31:10 1989 I agree that one would not follow this path in routing to hosts at UTK but this result is at least interesting for us folk that like to use SNMP to check interfaces and other matters of connectivity and network performance. Seems routing to any p4200 serial line address on all p4200s in SURAnet behaves similarily. The erratic response times are characteristic of the present overloaded SURAnet circuits outside of the SURAnet/NSFnet gateway congestion at UMD. Joe Ragland