> 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 msInteresting...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).