|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: 204.82.160.0/22 invisible
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 [email protected] or [email protected] 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 <[email protected]> - -- | From [email protected] Mon Sep 25 01:04:24 1995 | Resent-Date: Mon, 25 Sep 1995 01:03:08 -0400 | From: [email protected] (Andrew Partan) | Resent-To: <[email protected]> | Subject: Re: 204.82.160.0/22 invisible | To: [email protected] (Kai) | Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], | [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], | [email protected], [email protected] | Resent-From: [email protected] | X-Mailing-List: <[email protected]> archive/latest/167 | X-Loop: [email protected] | Resent-Sender: [email protected] | | 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. | [email protected] (Andrew Partan) | | |
|