Has PSI been assigned network 1?
Or why are they announcing it to the rest of the Internet through their box at MAE-East??? bash$ whois 1.0.0.0 No match for "1.0.0.0". The InterNIC Registration Services Host contains ONLY Internet Information (Networks, ASN's, Domains, and POC's). Please use the whois server at nic.ddn.mil for MILNET Information. traceroute 1.1.1.1 traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 40 byte packets 1 sl-dialup-2.sprintlink.net (192.157.36.128) 252 ms 245 ms 223 ms 2 192.157.36.1 (192.157.36.1) 251 ms 250 ms 251 ms 3 sl-dc-1-S3-T1.sprintlink.net (144.228.0.225) 252 ms 262 ms 253 ms 4 icm-dc-1-F0/0.icp.net (144.228.20.101) 275 ms 269 ms 252 ms 5 psi-mae-east-1.psi.net (192.41.177.235) 268 ms 254 ms 241 ms 6 washington2.dc.isdn.psi.net (38.146.99.110) 261 ms 271 ms 262 ms 7 1.1.1.1 (1.1.1.1) 457 ms 1284 ms 543 ms bash$ traceroute 1.1.1.2 traceroute to 1.1.1.2 (1.1.1.2), 30 hops max, 40 byte packets 1 sl-dialup-2.sprintlink.net (192.157.36.128) 253 ms 253 ms 246 ms 2 192.157.36.1 (192.157.36.1) 246 ms 243 ms 228 ms 3 sl-dc-1-S3-T1.sprintlink.net (144.228.0.225) 249 ms 447 ms 313 ms 4 icm-dc-1-F0/0.icp.net (144.228.20.101) 274 ms 251 ms 278 ms 5 psi-mae-east-1.psi.net (192.41.177.235) 265 ms 257 ms 266 ms 6 core.net228.psi.net (38.1.2.7) 286 ms 278 ms 276 ms 7 core.net99.psi.net (38.1.2.10) 338 ms 370 ms 279 ms 8 core.net228.psi.net (38.1.2.7) 306 ms 326 ms 290 ms 9 core.net99.psi.net (38.1.2.10) 335 ms 308 ms 325 ms 10 core.net228.psi.net (38.1.2.7) 372 ms 353 ms 341 ms 11 core.net99.psi.net (38.1.2.10) 376 ms 385 ms 377 ms 12 core.net228.psi.net (38.1.2.7) 438 ms 375 ms 365 ms 13 core.net99.psi.net (38.1.2.10) 384 ms 441 ms 371 ms 14 core.net228.psi.net (38.1.2.7) 394 ms 426 ms 474 ms 15 core.net99.psi.net (38.1.2.10) 427 ms 540 ms 565 ms 16 core.net228.psi.net (38.1.2.7) 521 ms 500 ms 489 ms 17 core.net99.psi.net (38.1.2.10) 530 ms 483 ms 527 ms 18 core.net228.psi.net (38.1.2.7) 567 ms 493 ms 561 ms 19 core.net99.psi.net (38.1.2.10) 779 ms 462 ms 670 ms 20 core.net228.psi.net (38.1.2.7) 531 ms 620 ms 613 ms 21 core.net99.psi.net (38.1.2.10) 562 ms 728 ms 598 ms 22 core.net228.psi.net (38.1.2.7) 812 ms 566 ms 835 ms 23 core.net99.psi.net (38.1.2.10) 661 ms 678 ms 574 ms 24 core.net228.psi.net (38.1.2.7) 647 ms 820 ms 666 ms 25 core.net99.psi.net (38.1.2.10) 649 ms 625 ms 628 ms 26 core.net228.psi.net (38.1.2.7) 900 ms 634 ms 733 ms 27 core.net99.psi.net (38.1.2.10) 648 ms 659 ms 656 ms 28 core.net228.psi.net (38.1.2.7) 776 ms 979 ms 834 ms 29 core.net99.psi.net (38.1.2.10) 715 ms 689 ms 734 ms 30 core.net228.psi.net (38.1.2.7) 782 ms 785 ms 677 ms ---Peter
Or why are they announcing it to the rest of the Internet through their box at MAE-East???
bash$ whois 1.0.0.0 No match for "1.0.0.0".
traceroute 1.1.1.1 traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 40 byte packets 1 sl-dialup-2.sprintlink.net (192.157.36.128) 252 ms 245 ms 223 ms 2 192.157.36.1 (192.157.36.1) 251 ms 250 ms 251 ms 3 sl-dc-1-S3-T1.sprintlink.net (144.228.0.225) 252 ms 262 ms 253 ms 4 icm-dc-1-F0/0.icp.net (144.228.20.101) 275 ms 269 ms 252 ms 5 psi-mae-east-1.psi.net (192.41.177.235) 268 ms 254 ms 241 ms 6 washington2.dc.isdn.psi.net (38.146.99.110) 261 ms 271 ms 262 ms 7 1.1.1.1 (1.1.1.1) 457 ms 1284 ms 543 ms
Interesting...I used to trace 1.1.1.1 back when I was a Sprint customer as a quick and easy way to verify ans connectivity. Then one day, it stopped working...and I had to resort to more creative elements. It doesn't really hurt anything, does it? Dave -- Dave Siegel, Director of Engineering Network (99) Operations Center (800)638-9947 (602)249-1190 after hours dsiegel@net99.net
Date Sent: 16-APR-1995 16:03:53
It doesn't really hurt anything, does it?
The standard by which network management is done is not the "it doesn't hurt anything" standard. It's the "do the right thing" standard. When PSI or their customers get net 1, they should feel free to announce it. I suspect that won't be anytime this week. :-)
Dave
Ehud -- Ehud Gavron (EG76) gavron@Hearts.ACES.COM
In message <199504162239.PAA26427@dewey.net99.net>, net99@net99.net writes:
Or why are they announcing it to the rest of the Internet through their box at MAE-East???
bash$ whois 1.0.0.0 No match for "1.0.0.0".
traceroute 1.1.1.1 traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 40 byte packets 1 sl-dialup-2.sprintlink.net (192.157.36.128) 252 ms 245 ms 223 ms 2 192.157.36.1 (192.157.36.1) 251 ms 250 ms 251 ms 3 sl-dc-1-S3-T1.sprintlink.net (144.228.0.225) 252 ms 262 ms 253 ms 4 icm-dc-1-F0/0.icp.net (144.228.20.101) 275 ms 269 ms 252 ms 5 psi-mae-east-1.psi.net (192.41.177.235) 268 ms 254 ms 241 ms 6 washington2.dc.isdn.psi.net (38.146.99.110) 261 ms 271 ms 262 ms 7 1.1.1.1 (1.1.1.1) 457 ms 1284 ms 543 ms
Interesting...I used to trace 1.1.1.1 back when I was a Sprint customer as a quick and easy way to verify ans connectivity. Then one day, it stopped working...and I had to resort to more creative elements. It doesn't really hurt anything, does it?
Dave
A minor clarification - ANS has never had or announced a route to net 1.0.0.0/8. I'm not saying what you calimed to be doing wouldn't work. You were probably verifying that PSI was announcing net 1 and had a working default route to ANS. At that point you should have received !H in the traceroute. The fact that you could rely on this anomoly also verifies the consistency of PSI incompetence in configuring their routing. Curtis BTW- You might try a traceroute to an address in 140.222/16. That's the ANS backbone. For example, traceroute 140.222.32.62 would verify that you could reach ANS NY POP. Traceroute 140.222.1.1 would give you a !H as soon as you reach an ANS interface (look for t3.ans.net in the DNS if the response is not from a 140.222 address).
-- Dave Siegel, Director of Engineering Network (99) Operations Center (800)638-9947 (602)249-1190 after hours dsiegel@net99.net
participants (5)
-
bergum＠MR.Net -
Curtis Villamizar -
Ehud Gavron -
net99＠net99.net -
Peter Lothberg