[irrtoolset]Error: badly formed AS_path filter
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?
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
I'm using the 4.8.2-FreeBSD 5 Precompiled binary. 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
On Mon, Aug 09, 2004 at 10:17:15AM -0400, Jason Lixfeld wrote:
I'm using the 4.8.2-FreeBSD 5 Precompiled binary.
Hmm, I'll recompile all binaries and will soon put the updated version on ftp.
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
-- Kind regards, Katje
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
On Mon, Aug 09, 2004 at 10:17:40AM -0400, Jason Lixfeld wrote:
Actually, I tried with 4.8.1 as well. Same result. Bug present there too?
Obviously. Please check the ftp site for the updated binaries for 4.8.2 later on.
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
-- Kind regards, Katje
participants (2)
-
Jason Lixfeld -
Katie Petrusha