smd at icp.net
Mon Sep 25 06:01:17 UTC 1995
Thank-you Andrew. That matches my diagnosis.
Kai: computel, our customer, should be able to help you
prepare an entry for the RADB; failing that, please
feel free to turn to noc at ans.net or engineer at sprint.net
for assistance in updating the RADB so that your prefix
is heard by ANS.
See, ANS has an inbound route-filter too... and it's MUCH older than Sprint's.
Sean Doran <smd at sprint.net>
| From nanog-request at merit.edu Mon Sep 25 01:04:24 1995
| Resent-Date: Mon, 25 Sep 1995 01:03:08 -0400
| From: asp at uunet.uu.net (Andrew Partan)
| Resent-To: <smd at chops.icp.net>
| Subject: Re: 184.108.40.206/22 invisible
| To: kai at belcom.net (Kai)
| Cc: dorian at CIC.Net, kai at belcom.net, avg at sprintlink.net, baldwin at SDD.COMSAT.COM, bertolini at computel.com, concaj at belcom.net, donagm at belcom.net,
| ilya at phri.nyu.edu, insc at sprintlink.net, ken at belcom.net, khalfk at belcom.net, ladycom at computel.com, nanog at MERIT.EDU, noc at digex.net, smd at icp.net,
| smd at sprint.net, susan.evans at SPRINT.SPRINT.COM
| Resent-From: nanog at MERIT.EDU
| X-Mailing-List: <nanog at MERIT.EDU> archive/latest/167
| X-Loop: nanog at MERIT.EDU
| Resent-Sender: nanog-request at MERIT.EDU
| Poking at this futher, Sprint is announcing 204.82.160/22; Digex is
| behind ANS; this route is not in the RADB; and since ANS insists on all
| routes being in the RADB, they are not accepting it, so Digex is not
| seeing it.
| Fix: Either get ANS to not insist on all routes being in the RADB or
| submit an update to the RADB & wait for ANS to regenerate their
| Kai: Please don't widly accuse folks before poking into the facts.
| --asp at uunet.uu.net (Andrew Partan)
More information about the NANOG