About RIPE NCC | Contact  | Search | Sitemap    
Homepage RIPE NCC  
RIPE NCC Mail Archives
     
Mailing Lists:
RIPE NCC Navigation Ends
Link to NCC Lists Archive NCC Lists Archive
Link to RIPE Lists Archive RIPE Lists Archive
RIPE NCC Navigation Ends
Next Section
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

Re: [irrtoolset]Error: badly formed AS_path filter

  • To: Katie Petrusha < >
  • From: Jason Lixfeld < >
  • Date: Mon, 9 Aug 2004 10:17:40 -0400

Actually, I tried with 4.8.1 as well. Same result. Bug present there too?

On 9-Aug-04, at 10:14 AM, Katie Petrusha wrote:

On Mon, Aug 09, 2004 at 10:07:10AM -0400, Jason Lixfeld wrote:

Dear Jason,

Which version are you using?
Latest 4.8.2 had a tiny bug in it, the patch and source are available at:

ftp://ftp.ripe.net/ripe/tools/IRRToolSet/IRRToolSet-4.8.2/

If you take the latest version and apply the patch, as-path filters work fine.

I'm not sure what I'm missing here. When I pass the following through
RtConfig, I get the above error. As per the man pages, RFC2622 states:
"An AS-path regular expression can be used as a policy filter by
enclosing the expression in ?<? and ?>?. An AS-path policy filter
matches the set of routes which traverses a sequence of ASes matched by
the AS-path regular expression." I read that as meaning that my
RtConfig line which reads @RtConfig aspath_access_list filter <AS577>
should work fine. I'm using 577 as an example just to test things out.
I'm not peering with 577 and have no relationship with them, however
that shouldn't prevent me from being able to generate an as-path
access-list using their information, should it?
--
Kind regards,
Katje



  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>
 

Next Section
     About RIPE NCC | Service Announcements | Site Map | LIR Portal | About RIPE | Contact | Legal | Copyright Statement
RIPE NCC Homepage Go to the RIPE NCC LIRPortal Go to the RIPE Community pages