Hi all! Whenever we do a traceroute from our Sprint connection to a host in the HiNet network, we get timed out in the Sprint/HiNet link, as follows: Tracing route to w3.hinet.net [168.95.1.82] over a maximum of 30 hops: 1 138 ms 116 ms 113 ms pi-ph-ts01.pacific.net.ph [210.23.234.128] 2 142 ms 111 ms 116 ms pi-ph-gw01.pacific.net.ph [210.23.234.1] 3 332 ms 330 ms 340 ms 204.59.178.25 4 375 ms 324 ms 328 ms 204.59.120.198 5 323 ms 322 ms 339 ms 144.232.1.153 6 380 ms 366 ms 365 ms 144.232.8.70 7 347 ms 373 ms 374 ms 144.232.4.142 8 * * * Request timed out. 9 546 ms 529 ms 523 ms 168.95.253.126 10 540 ms 532 ms 540 ms 168.95.253.189 11 547 ms 556 ms 547 ms w3.hinet.net [168.95.1.82] Trace complete. Line 8 is always like this and a customer of ours is complaining about it. Is this a time out or congestion or something else? William
william@pacific.net.ph writes:
Tracing route to w3.hinet.net [168.95.1.82] over a maximum of 30 hops:
1 138 ms 116 ms 113 ms pi-ph-ts01.pacific.net.ph [210.23.234.128] 2 142 ms 111 ms 116 ms pi-ph-gw01.pacific.net.ph [210.23.234.1] 3 332 ms 330 ms 340 ms 204.59.178.25 4 375 ms 324 ms 328 ms 204.59.120.198 5 323 ms 322 ms 339 ms 144.232.1.153 6 380 ms 366 ms 365 ms 144.232.8.70 7 347 ms 373 ms 374 ms 144.232.4.142 8 * * * Request timed out. 9 546 ms 529 ms 523 ms 168.95.253.126 10 540 ms 532 ms 540 ms 168.95.253.189 11 547 ms 556 ms 547 ms w3.hinet.net [168.95.1.82]
Trace complete.
Line 8 is always like this and a customer of ours is complaining about it. Is this a time out or congestion or something else?
Most likely there is a private address (in one of 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16) being used there. Tell the customer it is not their router and to not worry about it. Private addresses are often used this way. There are complications to it, and this is one of those. But it is still commonly done for many links as there is a huge supply of /30's in that space that can be used over and over again in the net. Only those engineers responsible for the router need access to it, and they probably figured that out well before they decided to assign such addresses. There is a remote possibility it is filtered or just a very very old router. -- Phil Howard | die4spam@anywhere.net no7way61@spammer0.com stop5795@s2p5a0m4.org phil | blow9me0@no1where.com no5spam4@no69ads6.net blow1me0@spam5mer.com at | end1it81@no5where.com ads6suck@no71ads5.net a7b4c5d9@no8where.edu ipal | end1it32@anywhere.net no1spam9@noplace3.org stop3387@noplace0.com dot | w2x8y5z5@nowhere0.edu no3way45@lame6ads.edu stop0919@spammer6.edu net | a6b3c2d4@no8place.com suck0it9@spammer2.org end7it80@no96ads5.net
On Wed, 26 Aug 1998, Phil Howard wrote:
william@pacific.net.ph writes:
8 * * * Request timed out.
Line 8 is always like this and a customer of ours is complaining about it. Is this a time out or congestion or something else?
Most likely there is a private address (in one of 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16) being used there. Tell the customer it is not their router and to not worry about it.
Private addresses are often used this way. There are complications to it, and this is one of those.
Unless someone upstream from your location is blocking packets sourced from private space, that's probably not what's happening here. Remember at no time during a traceroute are you sending packets directly to any hop along the way, all packets have the destination address of the address you're tracing to. On the way back they have a source address of the router along the way, which might be private, but have a destination address of the machine you started the traceroute from. More likely the router in question is just not sending ICMP TTL expired, or it is unable to route packets going back toward you for some reason. As others have said, tell the customer that as long as the packets make it _through_ the router, it's not a problem. Brandon Ross Network Engineering 404-815-0770 800-719-4664 Director, Network Engineering, MindSpring Ent., Inc. info@mindspring.com ICQ: 2269442 Stop Smurf attacks! Configure your router interfaces to block directed broadcasts. See http://www.quadrunner.com/~chuegen/smurf.cgi for details.
Hi William, APOPS is the more appropriate forum for a problem with HiNet. Barry
-----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of william@pacific.net.ph Sent: Thursday, August 27, 1998 2:55 AM To: nanog@merit.edu Subject: Sprint/HiNet
Hi all!
Whenever we do a traceroute from our Sprint connection to a host in the HiNet network, we get timed out in the Sprint/HiNet link, as follows:
Tracing route to w3.hinet.net [168.95.1.82] over a maximum of 30 hops:
1 138 ms 116 ms 113 ms pi-ph-ts01.pacific.net.ph [210.23.234.128] 2 142 ms 111 ms 116 ms pi-ph-gw01.pacific.net.ph [210.23.234.1] 3 332 ms 330 ms 340 ms 204.59.178.25 4 375 ms 324 ms 328 ms 204.59.120.198 5 323 ms 322 ms 339 ms 144.232.1.153 6 380 ms 366 ms 365 ms 144.232.8.70 7 347 ms 373 ms 374 ms 144.232.4.142 8 * * * Request timed out. 9 546 ms 529 ms 523 ms 168.95.253.126 10 540 ms 532 ms 540 ms 168.95.253.189 11 547 ms 556 ms 547 ms w3.hinet.net [168.95.1.82]
Trace complete.
Line 8 is always like this and a customer of ours is complaining about it. Is this a time out or congestion or something else?
William
participants (4)
-
Barry Raveendran Greene -
Brandon Ross -
Phil Howard -
william＠pacific.net.ph