North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
Re: Sprint internal inconsistency?
- From: neal rauhauser
- Date: Sun Apr 16 14:22:29 2006
I suspected as much myself with regard to not routing customer serial
links, but I've turned up half a dozen Sprint peering sessions in the
last six years and I've never seen one act the way this one does.
Maybe its something I'm doing ... I'm going to take the kids to the
park and not think about this for a while. Thanks for the response.
Justin Kreger wrote:
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.
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,
188.8.131.52/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
184.108.40.206 can send but receives no return traffic, while the
loopback IP is accessible.
Inside AS 16604
description DS3 to Sprint PL#:431846
ip address 220.127.116.11 255.255.255.252
ip route 18.104.22.168 255.255.255.252 22.214.171.124
Inside AS 22663
description 45076451-T, Prominic.net, Inc. (SL-PROMI-1)
ip address 126.96.36.199 255.255.255.252
interface Loopback 0
ip addresss 188.8.131.52 255.255.255.255
ip route 184.108.40.206 255.255.255.252 220.127.116.11
mailto:[email protected] // IM:layer3arts
voice: 402 408 5951
cell : 402 301 9555
fax : 402 408 6902