|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Fri, 17 Aug 2012 16:45:34 +0100 From: Patrick Sumby <patrick.sumby@sohonet.com> To: nanog@nanog.org In-Reply-To: <E1T2OI6-0007al-Kb@valhalla.seastrom.com> Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org L3 can be tricky with IRR especially if you have objects split across multiple IRR databases. This should help with what filters you want them to put on: http://www.clarksys.com/blog/2009/09/02/using-irr-with-level3/ You can test before using: whois -h filtergen.level3.net "RIPE::YOUR-AS-SET -searchpath=RIPE;ARIN;RADB -recurseok -warnonly" Regards Patrick On 17/08/2012 16:16, Robert E. Seastrom wrote: > Hi folks, > > Sorry for the extremely broad email but I'm trying to sort out an IRR > issue regarding automatic filter generation at Level(3) on behalf of a > friend. > > The telemetry I'm getting (thirdhand and believed to originate from > first line support) suggests that both Level(3)'s direct customer and > any downstreams of that customer need to be in the same IRR component. > If true this would be a rather startling shortcoming of their filter > generation software and at odds with the whole point of having > multiple components to the IRR system. > > Anyone got any pointers or help? Email to rr@level3.net has not > gotten us anywhere, but I was not the one who sent it and can't > guarantee that the right questions were asked. > > Thanks, > > -r > >
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |