cogent bgp filtering policies?
pauldotwall at gmail.com
Sun Jul 27 18:29:59 CDT 2008
Cogent does not support IRR. Since you're using IRR yourself, Richard
Steenbergen's IRRPT (irrpt.sf.net) has a script called 'irrpt_nag'
which is good for sending automated requests for prefix-list updates
with providers that continue to process them manually.
You can (and should) ask that Cogent's "Engineering" department okay
you for support for de-aggregation down to the /24 level or more
specific. They will with proper justification or a general feeling
that you've got good reason and aren't just looking to gratuitously
de-aggregate prefixes for no reason.
On Sun, Jul 27, 2008 at 5:59 AM, John van Oppen <john at vanoppen.com> wrote:
> Now that I am on my third round of an email argument with cogent's
> support department about adding prefixes to our filters (and them not
> understanding why I want le 24 matches on the blocks from which we
> allocate subnets to multi-homed customers) I figure it would be a good
> idea to ask if anyone has ever gotten cogent to setup any IRR based
> filtering on a customer connection.
> We are a small-ish regional transit provider in the northwest announcing
>> 100 prefixes and just spent the last few days writing emails and
> calling trying to get cogent to accept more than 30% of the routes we
> were announcing. We have IRR (radb to be specific) filters set up
> with our other four providers which really lowered my tolerance for
> having to go round and round to get prefixes added. Heck, at this
> point I would settle for a direct email address for their engineering
> department just to avoid the arguments with the support monkeys.
> I should note that this is actually the second time I have had this
> issue (the last time was with one of our customers and their cogent
> connection) even though we only turned up our service recently.
> John van Oppen
More information about the NANOG