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@ans.net or engineer@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. - -- Sean Doran <smd@sprint.net> - -- | From nanog-request@merit.edu Mon Sep 25 01:04:24 1995 | Resent-Date: Mon, 25 Sep 1995 01:03:08 -0400 | From: asp@uunet.uu.net (Andrew Partan) | Resent-To: <smd@chops.icp.net> | Subject: Re: 204.82.160.0/22 invisible | To: kai@belcom.net (Kai) | Cc: dorian@CIC.Net, kai@belcom.net, avg@sprintlink.net, baldwin@SDD.COMSAT.COM, bertolini@computel.com, concaj@belcom.net, donagm@belcom.net, | ilya@phri.nyu.edu, insc@sprintlink.net, ken@belcom.net, khalfk@belcom.net, ladycom@computel.com, nanog@MERIT.EDU, noc@digex.net, smd@icp.net, | smd@sprint.net, susan.evans@SPRINT.SPRINT.COM | Resent-From: nanog@MERIT.EDU | X-Mailing-List: <nanog@MERIT.EDU> archive/latest/167 | X-Loop: nanog@MERIT.EDU | Resent-Sender: nanog-request@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 | configs. | | Kai: Please don't widly accuse folks before poking into the facts. | --asp@uunet.uu.net (Andrew Partan) | | |