From katie at ripe.net Tue Aug 3 13:21:27 2004 From: katie at ripe.net (Katie Petrusha) Date: Tue, 3 Aug 2004 13:21:27 +0200 Subject: [irrtoolset]The release of RPSLng IRRToolSet Message-ID: <20040803112127.GA10677@ripe.net> [ Apologies for multiple messages ] Dear Colleagues, The RIPE NCC is pleased to announce version 4.8.2 release of IRRToolSet. RPSLng is an effort to extend RPSL language, enabling the language to document routing policies for the IPv6 and multicast address families currently used on the Internet. IRRToolSet implements the Internet Draft Document draft-blunk-rpslng-07 (ftp://ftp.ietf.org/internet-drafts/draft-blunk-rpslng-07.txt) The release contains peval, rpslcheck and RtConfig that support RPSLng. The software can be compiled using GCC-3.x, and also includes numerous contributed patches, bug fixes and changes related to the new draft. Please note that this will be the last release of IRRToolSet made by the RIPE NCC. Further IRRToolSet will be maintained by ISC (Internet Systems Consortium). More details regarding the migration will follow soon. The source code release and binary packages can be downloaded from: ftp://ftp.ripe.net/tools/IRRToolSet You can also check the IRRToolSet project page: http://www.ripe.net/db/irrtoolset Thanks to everyone who contributed the patches and bug fixes. Please contact for any comments. -- Best regards, Katie Petrusha RIPE NCC From jason at lixfeld.ca Mon Aug 9 16:07:10 2004 From: jason at lixfeld.ca (Jason Lixfeld) Date: Mon, 9 Aug 2004 10:07:10 -0400 Subject: [irrtoolset]Error: badly formed AS_path filter Message-ID: <678DF9AB-EA0D-11D8-8F80-000A95989E4A@lixfeld.ca> 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 ??. 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 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? From katie at ripe.net Mon Aug 9 16:14:27 2004 From: katie at ripe.net (Katie Petrusha) Date: Mon, 9 Aug 2004 16:14:27 +0200 Subject: [irrtoolset]Error: badly formed AS_path filter In-Reply-To: <678DF9AB-EA0D-11D8-8F80-000A95989E4A@lixfeld.ca> References: <678DF9AB-EA0D-11D8-8F80-000A95989E4A@lixfeld.ca> Message-ID: <20040809141426.GB1752@ripe.net> 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 ??. 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 > 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 From jason at lixfeld.ca Mon Aug 9 16:17:15 2004 From: jason at lixfeld.ca (Jason Lixfeld) Date: Mon, 9 Aug 2004 10:17:15 -0400 Subject: [irrtoolset]Error: badly formed AS_path filter In-Reply-To: <20040809141426.GB1752@ripe.net> References: <678DF9AB-EA0D-11D8-8F80-000A95989E4A@lixfeld.ca> <20040809141426.GB1752@ripe.net> Message-ID: 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 ??. 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 >> 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 From jason at lixfeld.ca Mon Aug 9 16:17:40 2004 From: jason at lixfeld.ca (Jason Lixfeld) Date: Mon, 9 Aug 2004 10:17:40 -0400 Subject: [irrtoolset]Error: badly formed AS_path filter In-Reply-To: <20040809141426.GB1752@ripe.net> References: <678DF9AB-EA0D-11D8-8F80-000A95989E4A@lixfeld.ca> <20040809141426.GB1752@ripe.net> Message-ID: 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 ??. 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 >> 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 From katie at ripe.net Mon Aug 9 16:19:09 2004 From: katie at ripe.net (Katie Petrusha) Date: Mon, 9 Aug 2004 16:19:09 +0200 Subject: [irrtoolset]Error: badly formed AS_path filter In-Reply-To: References: <678DF9AB-EA0D-11D8-8F80-000A95989E4A@lixfeld.ca> <20040809141426.GB1752@ripe.net> Message-ID: <20040809141909.GD1752@ripe.net> 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 ??. 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 > >>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 From katie at ripe.net Mon Aug 9 16:20:02 2004 From: katie at ripe.net (Katie Petrusha) Date: Mon, 9 Aug 2004 16:20:02 +0200 Subject: [irrtoolset]Error: badly formed AS_path filter In-Reply-To: References: <678DF9AB-EA0D-11D8-8F80-000A95989E4A@lixfeld.ca> <20040809141426.GB1752@ripe.net> Message-ID: <20040809142002.GE1752@ripe.net> 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 ??. 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 > >>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 From gerard at ripe.net Tue Aug 10 09:54:01 2004 From: gerard at ripe.net (Gerard Leurs) Date: Tue, 10 Aug 2004 09:54:01 +0200 Subject: [irrtoolset]Virus Warning from the RIPE NCC Message-ID: <200408100754.i7A7s1K0023118@x44.ripe.net> Dear Colleagues. We are sorry for duplicate emails. On Monday 9 August 2004, a virus (bagle) was mailed to several mailing lists operated by the RIPE NCC. Unfortunately, the virus passed through the filters of several of these lists. At the moment of writing we know this happened for the db-wg, eof-wg, routing-wg. And the wg-chairs. Please do not open any suspicious .zip files. Please make sure you delete any such mails. The RIPE NCC is working to resolve the issue. We apologise for any inconvenience this may have caused. Regards, Gerard Leurs, Operations department, RIPE NCC. From mihai.sandu at gtstelecom.ro Tue Aug 31 13:07:16 2004 From: mihai.sandu at gtstelecom.ro (Sandu Mihai) Date: Tue, 31 Aug 2004 14:07:16 +0300 Subject: [irrtoolset]IRRToolset 4.8.2 - segfaults on SuSE9 under certain conditions Message-ID: <41345BE4.2010908@gtstelecom.ro> Dear all, I have managed to compile Irrtoolset on SuSE 9, using the compiler that comes with the dist. It compiles fine, but if I try to run: @RtConfig printSuperPrefixes "%p%l\n" filter AS-ROMANIA trough RtConfig it will segfault. The segfault occurs in malloc, called from src/irr/rawhoisclient.cc, on line 304 (there is a prev = strdup(buffer)). It will not segfault if I change the AS-set or if I use a certain AS (eg. @RtConfig printSuperPrefixes "%p%l\n" filter AS5606 works fine). Does anyone managed to get this beast to run without problems on Linux (compiled from the sources)? The only thing that works is a 4.7.3 binary that I've got from ftp.ripe.net, and only on Redhat 7.3. A 4.7.3 compiled from the source will not work. A 4.8.2 for Fedora downloaded from ftp.ripe.net, behaves the same. Best regards, Sandu Mihai GTS Telecom NOC Engineer From p.caci at seabone.net Tue Aug 31 14:39:23 2004 From: p.caci at seabone.net (Pierfrancesco Caci) Date: Tue, 31 Aug 2004 14:39:23 +0200 Subject: [irrtoolset]IRRToolset 4.8.2 - segfaults on SuSE9 under certain conditions In-Reply-To: <41345BE4.2010908@gtstelecom.ro> (Sandu Mihai's message of "Tue, 31 Aug 2004 14:07:16 +0300") References: <41345BE4.2010908@gtstelecom.ro> Message-ID: <877jrf8osk.fsf@paperino.noc.seabone.net> :-> "Sandu" == Sandu Mihai writes: > @RtConfig printSuperPrefixes "%p%l\n" filter AS-ROMANIA does not segfault here, if I use printSuperPrefixRanges (that command you mentioned doesn't seem to exist). Debian Linux, sparc64, gcc version 3.3.4 (Debian) Pf -- ------------------------------------------------------------------------------- Pierfrancesco Caci | Network & System Administrator - INOC-DBA: 6762*PFC p.caci at seabone.net | Telecom Italia Sparkle - http://etabeta.noc.seabone.net/ Linux paperino 2.4.20 #1 Mon Dec 2 17:02:14 CET 2002 i686 GNU/Linux From p.caci at seabone.net Tue Aug 31 14:44:32 2004 From: p.caci at seabone.net (Pierfrancesco Caci) Date: Tue, 31 Aug 2004 14:44:32 +0200 Subject: [irrtoolset]other sources ? Message-ID: <873c238ojz.fsf@paperino.noc.seabone.net> Hello, if I use RtConfig with -h whois.ripe.net, it returns me only data from source: RIPE. I'd like it to include also data from RADB, I know that RIPE mirrors other registries' data, but I fail to understand how to use '@RtConfig set sources = "RIPE,RADB" ' ... is this the correct syntax ? Is this the right way to do it ? Thank you Pf -- ------------------------------------------------------------------------------- Pierfrancesco Caci | Network & System Administrator - INOC-DBA: 6762*PFC p.caci at seabone.net | Telecom Italia Sparkle - http://etabeta.noc.seabone.net/ Linux paperino 2.4.20 #1 Mon Dec 2 17:02:14 CET 2002 i686 GNU/Linux From mihai.sandu at gtstelecom.ro Tue Aug 31 15:26:36 2004 From: mihai.sandu at gtstelecom.ro (Sandu Mihai) Date: Tue, 31 Aug 2004 16:26:36 +0300 Subject: [irrtoolset]IRRToolset 4.8.2 - segfaults on SuSE9 under certain conditions In-Reply-To: <877jrf8osk.fsf@paperino.noc.seabone.net> References: <41345BE4.2010908@gtstelecom.ro> <877jrf8osk.fsf@paperino.noc.seabone.net> Message-ID: <41347C8C.8080709@gtstelecom.ro> Pierfrancesco Caci wrote: >:-> "Sandu" == Sandu Mihai writes: > > > @RtConfig printSuperPrefixes "%p%l\n" filter AS-ROMANIA > >does not segfault here, if I use printSuperPrefixRanges (that command >you mentioned doesn't seem to exist). > >Debian Linux, sparc64, gcc version 3.3.4 (Debian) > > >Pf > > > First, please accept my apologies for my typo. The command used to cause the segfault is: @RtConfig printSuperPrefixRanges "%p/%l\n" filter AS-ROMANIA I have tried it on: Redhat 7.3 - glibc-2.2.5-42 SuSE 9 - glibc-2.3.2-88 On both, the compiled binary will segfault. The binary for Fedora (IRRToolset 4.8.2) will also segfault. The binary for Redhat7.3 + compat libs will work on Redhat7.3 (I have managed to make a RPM out of it :) ) without a problem. I did inserted a cerr << "Blah" << buffer << "Blah" before the place where it segfaults, and for AS-ROMANIA it segfaults right after spitting out the 4th route object: *_route_*: 192.162.16.0/24 _origin_: AS3233 I suspect that probably there is something wrong with AS-ROMANIA that triggers the segfault. I can eventually send the output of a bt in gdb. Best regards, Sandu Mihai GTS Telecom NOC Engineer