Sprint internal inconsistency?

Sun Apr 16 17:30:27 UTC 2006

I remember getting a note from sprint when I was a sprint customer a few 
years back that said they were going to stop routing to the /30s for 
point-to-point customer links, unless requested to keep routing in place 
for that /30.

Hopes this helps.

-Justin

On Sun, 16 Apr 2006, neal rauhauser wrote:

>
>
>
>   AS16604 works fine, AS 22663 does not. I've picked at this for several 
> hours this AM - looks very much like 22663's serial interface, 
> 144.232.250.20/30, is blackholed somewhere inside Sprint. I got a tech who is 
> trying to help, but he is the guy who got stuck with Easter Sunday ... anyone 
> else awake at Sprint?
>
>
>
> These machines can't telnet to each other. Protocol capture and varying the 
> telnet source interface on the AS 22663 machine shows 144.232.250.22 can send 
> but receives no return traffic, while the loopback IP is accessible.
>
> Inside AS 16604
>
> interface Hssi3/0
> description DS3 to Sprint PL#:431846
> ip address 160.81.75.58 255.255.255.252
> ip route 144.232.250.20 255.255.255.252 160.81.76.57
>
> Inside AS 22663
>
> interface Serial5/1/0
> description 45076451-T, Prominic.net, Inc.  (SL-PROMI-1)
> bandwidth 44210
> ip address 144.232.250.22 255.255.255.252
>
> interface Loopback 0
> ip addresss 198.68.3.254 255.255.255.255
>
> ip route 160.81.75.56 255.255.255.252 144.232.250.21
>
>
>
>