|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: Sprint/HiNet
[email protected] 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 | [email protected] [email protected] [email protected] phil | [email protected] [email protected] [email protected] at | [email protected] [email protected] [email protected] ipal | [email protected] [email protected] [email protected] dot | [email protected] [email protected] [email protected] net | [email protected] [email protected] [email protected]
|