From alex at teleportsv.net Wed Nov 3 14:34:49 2004 From: alex at teleportsv.net (Alexander Moskalenko) Date: Wed, 03 Nov 2004 15:34:49 +0200 Subject: [irrtoolset]exit code Message-ID: <4188DE79.3050207@teleportsv.net> Hello! I use RtConfig in some scripts, but sometimes it cant get information from RIPE DB. In result it returns an empty output. I cant find any information about which exit code returned in this case. Could anyone explain which exit code returned in which situation? From f.ferreri at namex.it Thu Nov 4 16:36:49 2004 From: f.ferreri at namex.it (Francesco Ferreri) Date: Thu, 04 Nov 2004 16:36:49 +0100 Subject: [irrtoolset]generating import filters with RtConfig Message-ID: <418A4C91.7000905@namex.it> Dear all, I'm quite new to RtConfig, I would like to know how I can generate import filters both using prefix lists and as-path lists. Playing around with RIPE test database I got this: if I specify an import policy in such a way: import: from ASx accept ASy (having a route object for ASy), then "@RtConfig import ASx ASy " gives me back a filter based on prefix lists. Otherwise, if I specify an import policy (or similar): import: from ASx accept <^ASy+$> then I get back a filter based on an as-path. So the main difference seems to reside in the way the aut-num object is written: using simple AS names gives prefix list filters, using regular expressions on AS names gives as-path based filters, am I right ? Is there a way to combine both things to obtain both types of filters for the same peering relationship ? Thank you in advance and best regards, Francesco Ferreri -- ----------------------------------------- Francesco Ferreri NaMeX - Nautilus Mediterranean Exchange Via dei Tizii 6b, 00185 - Roma Tel. +39-0644486.302 E-mail: f.ferreri at namex.it WWW http://www.namex.it ----------------------------------------- From mrp at mrp.net Fri Nov 5 10:47:49 2004 From: mrp at mrp.net (Mark Prior) Date: Fri, 05 Nov 2004 20:17:49 +1030 Subject: [irrtoolset]generating import filters with RtConfig In-Reply-To: <418A4C91.7000905@namex.it> References: <418A4C91.7000905@namex.it> Message-ID: <418B4C45.1000100@mrp.net> Francesco Ferreri wrote: > Dear all, > I'm quite new to RtConfig, I would like to know how I can generate > import filters both using prefix lists and as-path lists. > > Playing around with RIPE test database I got this: > if I specify an import policy in such a way: > > import: from ASx accept ASy > > (having a route object for ASy), > then "@RtConfig import ASx ASy " gives me back a > filter based on prefix lists. > > Otherwise, if I specify an import policy (or similar): > > import: from ASx accept <^ASy+$> > > then I get back a filter based on an as-path. > > So the main difference seems to reside in the way the aut-num object is > written: using simple AS names gives prefix list filters, using regular > expressions on AS names gives as-path based filters, am I right ? > Is there a way to combine both things to obtain both types of filters > for the same peering relationship ? import: from ASx accept ASy AND <^ASy$> Mark. From jason at lixfeld.ca Fri Nov 5 19:05:03 2004 From: jason at lixfeld.ca (Jason Lixfeld) Date: Fri, 5 Nov 2004 13:05:03 -0500 Subject: [irrtoolset]Syntax errors in inet-rtr Message-ID: <375B4788-2F55-11D9-BA78-000A95D6AB8E@lixfeld.ca> Trying to reference a peering-set in an inet-rtr: inet-rtr: router1.example.com descr: AS1234 Example Company alias: r1.example.com local-as: AS1234 ifaddr: 198.32.245.52 masklen 24 peer: BGP4 prng-example asno(PeerAS) tech-c: See MAINT-AS1234 mnt-by: MAINT-AS1234 changed: noc at example.com 20041105 source: INTERNAL When I submit it, I get a message back complaining of a syntax error: UPDATE FAILED: [inet-rtr] router1.example.com inet-rtr: router1.example.com descr: AS1234 Example Company alias: r1.example.com local-as: AS1234 ifaddr: 198.32.245.52 masklen 24 peer: BGP4 prng-example asno(PeerAS) tech-c: See MAINT-AS1234 mnt-by: MAINT-AS1234 changed: noc at example.com 20041105 source: INTERNAL #ERROR: 6: peer: Syntax error All the material I've read indicates that this syntax should work. Any ideas? From ljb at merit.edu Fri Nov 5 19:44:06 2004 From: ljb at merit.edu (Larry J. Blunk) Date: Fri, 5 Nov 2004 13:44:06 -0500 Subject: [irrtoolset]Syntax errors in inet-rtr In-Reply-To: <375B4788-2F55-11D9-BA78-000A95D6AB8E@lixfeld.ca> References: <375B4788-2F55-11D9-BA78-000A95D6AB8E@lixfeld.ca> Message-ID: <200411051344.06106.ljb@merit.edu> On Friday 05 November 2004 13:05, Jason Lixfeld wrote: > Trying to reference a peering-set in an inet-rtr: > > inet-rtr: router1.example.com > descr: AS1234 Example Company > alias: r1.example.com > local-as: AS1234 > ifaddr: 198.32.245.52 masklen 24 > peer: BGP4 prng-example asno(PeerAS) > tech-c: See MAINT-AS1234 > mnt-by: MAINT-AS1234 > changed: noc at example.com 20041105 > source: INTERNAL > > When I submit it, I get a message back complaining of a syntax error: > > UPDATE FAILED: [inet-rtr] router1.example.com > inet-rtr: router1.example.com > descr: AS1234 Example Company > alias: r1.example.com > local-as: AS1234 > ifaddr: 198.32.245.52 masklen 24 > peer: BGP4 prng-example asno(PeerAS) > tech-c: See MAINT-AS1234 > mnt-by: MAINT-AS1234 > changed: noc at example.com 20041105 > source: INTERNAL > #ERROR: 6: peer: Syntax error > > All the material I've read indicates that this syntax should work. > > Any ideas? Your syntax is okay, it's a problem with the syntax checker in IRRd (actually, the bug is in the RFC2622 dictionary definition -- I can blame it on Cengiz :-). I'll try to get out a fixed release soon. -Larry Blunk Merit From engin at ripe.net Fri Nov 5 21:14:14 2004 From: engin at ripe.net (Engin Gunduz) Date: Fri, 5 Nov 2004 21:14:14 +0100 Subject: [irrtoolset]Syntax errors in inet-rtr In-Reply-To: <200411051344.06106.ljb@merit.edu> References: <375B4788-2F55-11D9-BA78-000A95D6AB8E@lixfeld.ca> <200411051344.06106.ljb@merit.edu> Message-ID: <20041105201414.GA2495@x47.ripe.net> On 2004-11-05 13:44:06 -0500, Larry J. Blunk wrote: > On Friday 05 November 2004 13:05, Jason Lixfeld wrote: > > Trying to reference a peering-set in an inet-rtr: > > > > inet-rtr: router1.example.com > > descr: AS1234 Example Company > > alias: r1.example.com > > local-as: AS1234 > > ifaddr: 198.32.245.52 masklen 24 > > peer: BGP4 prng-example asno(PeerAS) > > tech-c: See MAINT-AS1234 > > mnt-by: MAINT-AS1234 > > changed: noc at example.com 20041105 > > source: INTERNAL > > > > When I submit it, I get a message back complaining of a syntax error: > > > > UPDATE FAILED: [inet-rtr] router1.example.com > > inet-rtr: router1.example.com > > descr: AS1234 Example Company > > alias: r1.example.com > > local-as: AS1234 > > ifaddr: 198.32.245.52 masklen 24 > > peer: BGP4 prng-example asno(PeerAS) > > tech-c: See MAINT-AS1234 > > mnt-by: MAINT-AS1234 > > changed: noc at example.com 20041105 > > source: INTERNAL > > #ERROR: 6: peer: Syntax error > > > > All the material I've read indicates that this syntax should work. > > > > Any ideas? > > Your syntax is okay, it's a problem with the syntax checker > in IRRd (actually, the bug is in the RFC2622 dictionary definition -- Now that we can have errata for RFCs (http://www.rfc-editor.org/errata.html), how about preparing one for RPSL RFCs? -engin > I can blame it on Cengiz :-). I'll try to get out a fixed release soon. > > -Larry Blunk > Merit From cengiz at packetdesign.com Fri Nov 5 22:10:04 2004 From: cengiz at packetdesign.com (Cengiz Alaettinoglu) Date: Fri, 05 Nov 2004 13:10:04 -0800 Subject: [irrtoolset]Syntax errors in inet-rtr In-Reply-To: <20041105201414.GA2495@x47.ripe.net> References: <375B4788-2F55-11D9-BA78-000A95D6AB8E@lixfeld.ca> <200411051344.06106.ljb@merit.edu> <20041105201414.GA2495@x47.ripe.net> Message-ID: <1099689004.9710.41.camel@zen> Good idea. I have a list already. If someone volunteers, I will pass my list... On Fri, 2004-11-05 at 21:14 +0100, Engin Gunduz wrote: > On 2004-11-05 13:44:06 -0500, Larry J. Blunk wrote: > > On Friday 05 November 2004 13:05, Jason Lixfeld wrote: > > > Trying to reference a peering-set in an inet-rtr: > > > > > > inet-rtr: router1.example.com > > > descr: AS1234 Example Company > > > alias: r1.example.com > > > local-as: AS1234 > > > ifaddr: 198.32.245.52 masklen 24 > > > peer: BGP4 prng-example asno(PeerAS) > > > tech-c: See MAINT-AS1234 > > > mnt-by: MAINT-AS1234 > > > changed: noc at example.com 20041105 > > > source: INTERNAL > > > > > > When I submit it, I get a message back complaining of a syntax error: > > > > > > UPDATE FAILED: [inet-rtr] router1.example.com > > > inet-rtr: router1.example.com > > > descr: AS1234 Example Company > > > alias: r1.example.com > > > local-as: AS1234 > > > ifaddr: 198.32.245.52 masklen 24 > > > peer: BGP4 prng-example asno(PeerAS) > > > tech-c: See MAINT-AS1234 > > > mnt-by: MAINT-AS1234 > > > changed: noc at example.com 20041105 > > > source: INTERNAL > > > #ERROR: 6: peer: Syntax error > > > > > > All the material I've read indicates that this syntax should work. > > > > > > Any ideas? > > > > Your syntax is okay, it's a problem with the syntax checker > > in IRRd (actually, the bug is in the RFC2622 dictionary definition -- > > Now that we can have errata for RFCs (http://www.rfc-editor.org/errata.html), > how about preparing one for RPSL RFCs? > -engin > > > I can blame it on Cengiz :-). I'll try to get out a fixed release soon. > > > > -Larry Blunk > > Merit -- Cengiz Alaettinoglu From curtis at faster-light.net Fri Nov 5 23:40:30 2004 From: curtis at faster-light.net (Curtis Villamizar) Date: Fri, 05 Nov 2004 17:40:30 -0500 Subject: [irrtoolset]Syntax errors in inet-rtr In-Reply-To: Your message of "Fri, 05 Nov 2004 13:10:04 PST." <1099689004.9710.41.camel@zen> Message-ID: <200411052240.iA5MeUgG093249@workhorse.faster-light.net> In message <1099689004.9710.41.camel at zen> Cengiz Alaettinoglu writes: > > Good idea. I have a list already. If someone volunteers, I will pass my > list... The errata was intended for typos and what would normally be considered minor editorial changes that don't change the meaning of the RFC. If you want to make changes you still need a new RFC. Curtis > On Fri, 2004-11-05 at 21:14 +0100, Engin Gunduz wrote: > > On 2004-11-05 13:44:06 -0500, Larry J. Blunk wrote: > > > On Friday 05 November 2004 13:05, Jason Lixfeld wrote: > > > > Trying to reference a peering-set in an inet-rtr: > > > > > > > > inet-rtr: router1.example.com > > > > descr: AS1234 Example Company > > > > alias: r1.example.com > > > > local-as: AS1234 > > > > ifaddr: 198.32.245.52 masklen 24 > > > > peer: BGP4 prng-example asno(PeerAS) > > > > tech-c: See MAINT-AS1234 > > > > mnt-by: MAINT-AS1234 > > > > changed: noc at example.com 20041105 > > > > source: INTERNAL > > > > > > > > When I submit it, I get a message back complaining of a syntax error: > > > > > > > > UPDATE FAILED: [inet-rtr] router1.example.com > > > > inet-rtr: router1.example.com > > > > descr: AS1234 Example Company > > > > alias: r1.example.com > > > > local-as: AS1234 > > > > ifaddr: 198.32.245.52 masklen 24 > > > > peer: BGP4 prng-example asno(PeerAS) > > > > tech-c: See MAINT-AS1234 > > > > mnt-by: MAINT-AS1234 > > > > changed: noc at example.com 20041105 > > > > source: INTERNAL > > > > #ERROR: 6: peer: Syntax error > > > > > > > > All the material I've read indicates that this syntax should work. > > > > > > > > Any ideas? > > > > > > Your syntax is okay, it's a problem with the syntax checker > > > in IRRd (actually, the bug is in the RFC2622 dictionary definition -- > > > > Now that we can have errata for RFCs (http://www.rfc-editor.org/errata.html), > > how about preparing one for RPSL RFCs? > > -engin > > > > > I can blame it on Cengiz :-). I'll try to get out a fixed release soon. > > > > > > -Larry Blunk > > > Merit > -- > Cengiz Alaettinoglu From fredrik at sunet.se Mon Nov 8 12:55:51 2004 From: fredrik at sunet.se (Fredrik Widell) Date: Mon, 8 Nov 2004 12:55:51 +0100 (CET) Subject: [irrtoolset]peval & whois.ripe.net Message-ID: <20041108124637.S99951@bardisk.pilsnet.sunet.se> Hi all, currently (and for the last 1-2 weeks) I am utterly unable to fetch/make filterlists for peers with large as-sets, to mee it seems whois.ripe.net is quite unresponsive, and sometimes even delivers the wrong results with peval, the example I have most trouble with atm below: peval -h whois.ripe.net -protocol ripe -no-as "AS702 AS702:RS-EURO AS702:RS-CUSTOMER" mostly, this justs exits with a "141 pipe broken", but, sometimes the result is ((AS702)) which is very far from the truth. So, can I still trust ripe-dbm to create my filterlists? or should I get other means to make my filters? -- Regards /Fredrik ------------------------------------------------------- KTHNOC, KTH, S-100 44 Stockholm, Sweden +46 8 790 65 17 ------------------------------------------------------- From alex.dempsey at vodafone.com Mon Nov 8 15:02:56 2004 From: alex.dempsey at vodafone.com (alex.dempsey at vodafone.com) Date: Mon, 8 Nov 2004 14:02:56 +0000 Subject: [irrtoolset]Alex Dempsey/Vodafone is out of the office. Message-ID: I will be out of the office starting 08/11/2004 and will not return until 22/11/2004. I will be out of the office starting 08/11/2004 and will not return until 22/11/2004. For any urgent queries, please call me on +353 87 6227222, otherwise I will respond to your message on my return. Regards, Alex Dempsey ****************************************************************************** The content of this e-mail may be confidential or legally privileged. If you are not the named addressee or the intended recipient please do not copy it or forward it to anyone. If you have received this email in error please destroy it and kindly notify the sender and postmaster.ie at vodafone.com. Email cannot be guaranteed to be secure or error-free, it is your responsibility to ensure that the message (including attachments) is safe and authorised for use in your environment. Vodafone Ireland Limited. Directors: Peter Bamford Chairman (UK), Pauline Best (UK), Paul Donovan Chief Executive (UK), Gerry Fahy, David Boorman (UK), David Smithwhite (UK), Patrick Teahon, Alfred Kane. Registered in Ireland at MountainView, Leopardstown, Dublin 18. Co Reg No.: 326967 VAT Reg No. IE6346967G ****************************************************************************** From alex.dempsey at vodafone.com Tue Nov 9 14:59:33 2004 From: alex.dempsey at vodafone.com (alex.dempsey at vodafone.com) Date: Tue, 9 Nov 2004 13:59:33 +0000 Subject: [irrtoolset]Alex Dempsey/Vodafone is out of the office. Message-ID: I will be out of the office starting 08/11/2004 and will not return until 22/11/2004. I will be out of the office starting 08/11/2004 and will not return until 22/11/2004. For any urgent queries, please call me on +353 87 6227222, otherwise I will respond to your message on my return. Regards, Alex Dempsey ****************************************************************************** The content of this e-mail may be confidential or legally privileged. If you are not the named addressee or the intended recipient please do not copy it or forward it to anyone. If you have received this email in error please destroy it and kindly notify the sender and postmaster.ie at vodafone.com. Email cannot be guaranteed to be secure or error-free, it is your responsibility to ensure that the message (including attachments) is safe and authorised for use in your environment. Vodafone Ireland Limited. Directors: Peter Bamford Chairman (UK), Pauline Best (UK), Paul Donovan Chief Executive (UK), Gerry Fahy, David Boorman (UK), David Smithwhite (UK), Patrick Teahon, Alfred Kane. Registered in Ireland at MountainView, Leopardstown, Dublin 18. Co Reg No.: 326967 VAT Reg No. IE6346967G ****************************************************************************** From engin at ripe.net Thu Nov 11 03:55:33 2004 From: engin at ripe.net (Engin Gunduz) Date: Thu, 11 Nov 2004 03:55:33 +0100 Subject: [irrtoolset]Syntax errors in inet-rtr In-Reply-To: <200411052240.iA5MeUgG093249@workhorse.faster-light.net> References: <1099689004.9710.41.camel@zen> <200411052240.iA5MeUgG093249@workhorse.faster-light.net> Message-ID: <20041111025533.GA22874@x47.ripe.net> On 2004-11-05 17:40:30 -0500, Curtis Villamizar wrote: > In message <1099689004.9710.41.camel at zen> > Cengiz Alaettinoglu writes: > > > > Good idea. I have a list already. If someone volunteers, I will pass my > > list... > > The errata was intended for typos and what would normally be > considered minor editorial changes that don't change the meaning of > the RFC. If you want to make changes you still need a new RFC. Right. Still, I guess there are minor editorial changes that can go into errata. Let's review what we have now, find out which of them can go into errata... Cengiz, I can volunteer for that... -engin > Curtis > > > > On Fri, 2004-11-05 at 21:14 +0100, Engin Gunduz wrote: > > > On 2004-11-05 13:44:06 -0500, Larry J. Blunk wrote: > > > > On Friday 05 November 2004 13:05, Jason Lixfeld wrote: > > > > > Trying to reference a peering-set in an inet-rtr: > > > > > > > > > > inet-rtr: router1.example.com > > > > > descr: AS1234 Example Company > > > > > alias: r1.example.com > > > > > local-as: AS1234 > > > > > ifaddr: 198.32.245.52 masklen 24 > > > > > peer: BGP4 prng-example asno(PeerAS) > > > > > tech-c: See MAINT-AS1234 > > > > > mnt-by: MAINT-AS1234 > > > > > changed: noc at example.com 20041105 > > > > > source: INTERNAL > > > > > > > > > > When I submit it, I get a message back complaining of a syntax error: > > > > > > > > > > UPDATE FAILED: [inet-rtr] router1.example.com > > > > > inet-rtr: router1.example.com > > > > > descr: AS1234 Example Company > > > > > alias: r1.example.com > > > > > local-as: AS1234 > > > > > ifaddr: 198.32.245.52 masklen 24 > > > > > peer: BGP4 prng-example asno(PeerAS) > > > > > tech-c: See MAINT-AS1234 > > > > > mnt-by: MAINT-AS1234 > > > > > changed: noc at example.com 20041105 > > > > > source: INTERNAL > > > > > #ERROR: 6: peer: Syntax error > > > > > > > > > > All the material I've read indicates that this syntax should work. > > > > > > > > > > Any ideas? > > > > > > > > Your syntax is okay, it's a problem with the syntax checker > > > > in IRRd (actually, the bug is in the RFC2622 dictionary definition -- > > > > > > Now that we can have errata for RFCs (http://www.rfc-editor.org/errata.html), > > > how about preparing one for RPSL RFCs? > > > -engin > > > > > > > I can blame it on Cengiz :-). I'll try to get out a fixed release soon. > > > > > > > > -Larry Blunk > > > > Merit > > -- > > Cengiz Alaettinoglu > -- Engin Gunduz RIPE NCC Software Engineering Department From cengiz at packetdesign.com Thu Nov 11 06:26:24 2004 From: cengiz at packetdesign.com (Cengiz Alaettinoglu) Date: Wed, 10 Nov 2004 21:26:24 -0800 Subject: [irrtoolset]Syntax errors in inet-rtr In-Reply-To: <20041111025533.GA22874@x47.ripe.net> References: <1099689004.9710.41.camel@zen> <200411052240.iA5MeUgG093249@workhorse.faster-light.net> <20041111025533.GA22874@x47.ripe.net> Message-ID: <1100150784.8233.181.camel@elf> Thanks Engin. I will send them to you probably towards the end of next week (I will have few days of vacation). On Thu, 2004-11-11 at 03:55 +0100, Engin Gunduz wrote: > On 2004-11-05 17:40:30 -0500, Curtis Villamizar wrote: > > In message <1099689004.9710.41.camel at zen> > > Cengiz Alaettinoglu writes: > > > > > > Good idea. I have a list already. If someone volunteers, I will pass my > > > list... > > > > The errata was intended for typos and what would normally be > > considered minor editorial changes that don't change the meaning of > > the RFC. If you want to make changes you still need a new RFC. > > Right. Still, I guess there are minor editorial changes that can > go into errata. Let's review what we have now, find out which > of them can go into errata... > > Cengiz, I can volunteer for that... > -engin > > > > Curtis > > > > > > > On Fri, 2004-11-05 at 21:14 +0100, Engin Gunduz wrote: > > > > On 2004-11-05 13:44:06 -0500, Larry J. Blunk wrote: > > > > > On Friday 05 November 2004 13:05, Jason Lixfeld wrote: > > > > > > Trying to reference a peering-set in an inet-rtr: > > > > > > > > > > > > inet-rtr: router1.example.com > > > > > > descr: AS1234 Example Company > > > > > > alias: r1.example.com > > > > > > local-as: AS1234 > > > > > > ifaddr: 198.32.245.52 masklen 24 > > > > > > peer: BGP4 prng-example asno(PeerAS) > > > > > > tech-c: See MAINT-AS1234 > > > > > > mnt-by: MAINT-AS1234 > > > > > > changed: noc at example.com 20041105 > > > > > > source: INTERNAL > > > > > > > > > > > > When I submit it, I get a message back complaining of a syntax error: > > > > > > > > > > > > UPDATE FAILED: [inet-rtr] router1.example.com > > > > > > inet-rtr: router1.example.com > > > > > > descr: AS1234 Example Company > > > > > > alias: r1.example.com > > > > > > local-as: AS1234 > > > > > > ifaddr: 198.32.245.52 masklen 24 > > > > > > peer: BGP4 prng-example asno(PeerAS) > > > > > > tech-c: See MAINT-AS1234 > > > > > > mnt-by: MAINT-AS1234 > > > > > > changed: noc at example.com 20041105 > > > > > > source: INTERNAL > > > > > > #ERROR: 6: peer: Syntax error > > > > > > > > > > > > All the material I've read indicates that this syntax should work. > > > > > > > > > > > > Any ideas? > > > > > > > > > > Your syntax is okay, it's a problem with the syntax checker > > > > > in IRRd (actually, the bug is in the RFC2622 dictionary definition -- > > > > > > > > Now that we can have errata for RFCs (http://www.rfc-editor.org/errata.html), > > > > how about preparing one for RPSL RFCs? > > > > -engin > > > > > > > > > I can blame it on Cengiz :-). I'll try to get out a fixed release soon. > > > > > > > > > > -Larry Blunk > > > > > Merit > > > -- > > > Cengiz Alaettinoglu > > > From reiserc at in.tum.de Thu Nov 11 10:52:44 2004 From: reiserc at in.tum.de (Christian Reiser) Date: Thu, 11 Nov 2004 10:51:44 +0059 Subject: [irrtoolset]Syntax errors in inet-rtr In-Reply-To: <200411052240.iA5MeUgG093249@workhorse.faster-light.net> References: <200411052240.iA5MeUgG093249@workhorse.faster-light.net> Message-ID: <41933646.4050206@in.tum.de> Curtis Villamizar wrote: > The errata was intended for typos and what would normally be > considered minor editorial changes that don't change the meaning of > the RFC. If you want to make changes you still need a new RFC. I wonder, which changes have be done, and if it would make sense to go for a new RFC. Personally, i would like to have extended bgp community handling within RPSL. Unfortunately this feature has not been included in RPSLng, and the current syntax is not even powerfull enough to clear your own community-space at ingress. Ciao Christian From gba at undef.net Thu Nov 11 17:35:35 2004 From: gba at undef.net (Greg Albrecht) Date: Thu, 11 Nov 2004 08:35:35 -0800 Subject: [irrtoolset]new to RR's, can't read my own export policy? Message-ID: <419394D7.70608@undef.net> again, i'm new, but: whois -h rr.arin.net as14022 shows: export: to as3356 4.24.56.73 at 4.24.56.74 announce RS-BBCM-LAX import: from as3356 4.24.56.73 at 4.24.56.74 accept as3356 whois -h rr.arin.net rs-bbcm-lax shows: route-set: RS-BBCM-LAX members: as20239, as31971 mbrs-by-ref: MNT-BBCM etc... RtConfig, however, shows: ***Error: Unknown class encountered. Warning: AS14022 has no export/mp-export policy for AS3356 4.24.56.74 at 4.24.56.73 my rtconfig config: @RtConfig export AS14022 AS3356 -xs -- Greg Albrecht (gba at undef.net) www.undef.net * 1-415-794-5944 From cengiz at packetdesign.com Fri Nov 12 17:02:43 2004 From: cengiz at packetdesign.com (Cengiz Alaettinoglu) Date: Fri, 12 Nov 2004 08:02:43 -0800 Subject: [irrtoolset]new to RR's, can't read my own export policy? In-Reply-To: <419394D7.70608@undef.net> References: <419394D7.70608@undef.net> Message-ID: <1100275363.1532.42.camel@elf> I think you need to spell out the routers. @RtConfig export AS14022 4.24.56.74 AS3356 4.24.56.73 (Actually, according to the error message they were spelled out but put in the wrong order). On Thu, 2004-11-11 at 08:35 -0800, Greg Albrecht wrote: > again, i'm new, but: > > whois -h rr.arin.net as14022 shows: > export: to as3356 4.24.56.73 at 4.24.56.74 announce RS-BBCM-LAX > import: from as3356 4.24.56.73 at 4.24.56.74 accept as3356 > > whois -h rr.arin.net rs-bbcm-lax shows: > route-set: RS-BBCM-LAX > members: as20239, as31971 > mbrs-by-ref: MNT-BBCM > > etc... > > RtConfig, however, shows: > ***Error: Unknown class encountered. > Warning: AS14022 has no export/mp-export policy for AS3356 4.24.56.74 at > 4.24.56.73 > > my rtconfig config: > @RtConfig export AS14022 AS3356 > > > -xs > From gba at undef.net Fri Nov 12 19:12:39 2004 From: gba at undef.net (Greg Albrecht) Date: Fri, 12 Nov 2004 10:12:39 -0800 Subject: [irrtoolset]new to RR's, can't read my own export policy? In-Reply-To: <1100275363.1532.42.camel@elf> References: <419394D7.70608@undef.net> <1100275363.1532.42.camel@elf> Message-ID: <4194FD17.9030308@undef.net> yeah it's weird. i get the error no matter what, ie: a) weather i put the IPs in the export record b) no matter what order i put the IPs in, if i do put them in. i can't even generate a martian list: @RtConfig access_list filter rs-martians cat r1.rtt|RtConfig -T all -h rr.arin.net -protocol bird -cisco_empty_lists ***Error: Unknown class encountered. Warning: filter matches ANY/NOT ANY -xs Cengiz Alaettinoglu wrote: > I think you need to spell out the routers. > > @RtConfig export AS14022 4.24.56.74 AS3356 4.24.56.73 > > (Actually, according to the error message they were spelled out but put > in the wrong order). > > On Thu, 2004-11-11 at 08:35 -0800, Greg Albrecht wrote: > >>again, i'm new, but: >> >>whois -h rr.arin.net as14022 shows: >>export: to as3356 4.24.56.73 at 4.24.56.74 announce RS-BBCM-LAX >>import: from as3356 4.24.56.73 at 4.24.56.74 accept as3356 >> >>whois -h rr.arin.net rs-bbcm-lax shows: >>route-set: RS-BBCM-LAX >>members: as20239, as31971 >>mbrs-by-ref: MNT-BBCM >> >>etc... >> >>RtConfig, however, shows: >>***Error: Unknown class encountered. >>Warning: AS14022 has no export/mp-export policy for AS3356 4.24.56.74 at >>4.24.56.73 >> >>my rtconfig config: >>@RtConfig export AS14022 AS3356 >> >> >>-xs >> -- Greg Albrecht (gba at undef.net) www.undef.net * 1-415-794-5944 From engin at ripe.net Wed Nov 17 14:00:12 2004 From: engin at ripe.net (Engin Gunduz) Date: Wed, 17 Nov 2004 14:00:12 +0100 Subject: [irrtoolset]peval & whois.ripe.net In-Reply-To: <20041108124637.S99951@bardisk.pilsnet.sunet.se> References: <20041108124637.S99951@bardisk.pilsnet.sunet.se> Message-ID: <20041117130011.GC12979@x47.ripe.net> Dear Fredrik, Sorry for the late answer. I hope your problem has already been solved when we have put the new hardware into production, which is much faster. This should have solved the long query response time problem. Regards, -- Engin Gunduz RIPE NCC Software Engineering Departmen On 2004-11-08 12:55:51 +0100, Fredrik Widell wrote: > Hi all, > > currently (and for the last 1-2 weeks) I am utterly unable > to fetch/make filterlists for peers with large as-sets, > to mee it seems whois.ripe.net is quite unresponsive, and > sometimes even delivers the wrong results with peval, > the example I have most trouble with atm below: > > peval -h whois.ripe.net -protocol ripe -no-as "AS702 AS702:RS-EURO > AS702:RS-CUSTOMER" > > mostly, this justs exits with a "141 pipe broken", but, sometimes > the result is ((AS702)) which is very far from the truth. > > So, can I still trust ripe-dbm to create my filterlists? or should > I get other means to make my filters? > > > > -- > > Regards > > /Fredrik > > ------------------------------------------------------- > KTHNOC, KTH, S-100 44 Stockholm, Sweden +46 8 790 65 17 > ------------------------------------------------------- From fredrik at sunet.se Thu Nov 18 09:36:53 2004 From: fredrik at sunet.se (Fredrik Widell) Date: Thu, 18 Nov 2004 09:36:53 +0100 (CET) Subject: [irrtoolset]peval & whois.ripe.net In-Reply-To: <20041117130011.GC12979@x47.ripe.net> References: <20041108124637.S99951@bardisk.pilsnet.sunet.se> <20041117130011.GC12979@x47.ripe.net> Message-ID: <20041118093402.F23699@bardisk.pilsnet.sunet.se> On Wed, 17 Nov 2004, Engin Gunduz wrote: > Dear Fredrik, > Sorry for the late answer. > > I hope your problem has already been solved when we have > put the new hardware into production, which is much faster. > This should have solved the long query response time problem. Yes, absolutely, but I still wonder why the expansion of AS702:RS-CUSTOMER actually was totally wrong, it would have been better with no answer at all, will this happen again in a couple of years when it is time to change the hw for the whois-server? it trashes peerings in a very bad manner if/when it happens, so I'm just curious. Otherwise the current whois-server is fast as **** :) > > Regards, > > -- > Engin Gunduz > RIPE NCC Software Engineering Departmen > > On 2004-11-08 12:55:51 +0100, Fredrik Widell wrote: >> Hi all, >> >> currently (and for the last 1-2 weeks) I am utterly unable >> to fetch/make filterlists for peers with large as-sets, >> to mee it seems whois.ripe.net is quite unresponsive, and >> sometimes even delivers the wrong results with peval, >> the example I have most trouble with atm below: >> >> peval -h whois.ripe.net -protocol ripe -no-as "AS702 AS702:RS-EURO >> AS702:RS-CUSTOMER" >> >> mostly, this justs exits with a "141 pipe broken", but, sometimes >> the result is ((AS702)) which is very far from the truth. >> >> So, can I still trust ripe-dbm to create my filterlists? or should >> I get other means to make my filters? >> >> >> >> -- >> >> Regards >> >> /Fredrik >> >> ------------------------------------------------------- >> KTHNOC, KTH, S-100 44 Stockholm, Sweden +46 8 790 65 17 >> ------------------------------------------------------- > -- Mvh /Fredrik ------------------------------------------------------- KTHNOC, KTH, S-100 44 Stockholm, Sweden +46 8 790 65 17 ------------------------------------------------------- From engin at ripe.net Thu Nov 18 10:43:33 2004 From: engin at ripe.net (Engin Gunduz) Date: Thu, 18 Nov 2004 10:43:33 +0100 Subject: [irrtoolset]peval & whois.ripe.net In-Reply-To: <20041118093402.F23699@bardisk.pilsnet.sunet.se> References: <20041108124637.S99951@bardisk.pilsnet.sunet.se> <20041117130011.GC12979@x47.ripe.net> <20041118093402.F23699@bardisk.pilsnet.sunet.se> Message-ID: <20041118094333.GD460@x47.ripe.net> Fredrik, On 2004-11-18 09:36:53 +0100, Fredrik Widell wrote: > On Wed, 17 Nov 2004, Engin Gunduz wrote: > > >Dear Fredrik, > >Sorry for the late answer. > > > >I hope your problem has already been solved when we have > >put the new hardware into production, which is much faster. > >This should have solved the long query response time problem. > > > Yes, absolutely, but I still wonder why the expansion of > AS702:RS-CUSTOMER actually was totally wrong, it would have > been better with no answer at all, will this happen again > in a couple of years when it is time to change the hw for > the whois-server? it trashes peerings in a very bad manner > if/when it happens, so I'm just curious. Otherwise the > current whois-server is fast as **** :) I guess what happened was that the old harware was causing queries to time out and when peval does multiple queries some of those fell victim to time-outs, which resulted in incorrect expansion of as-sets. We are sorry for the inconvenience it caused. We will do out best to prevent this in the future. Regards, -- Engin Gunduz RIPE NCC Software Engineering Department > >Regards, > > > >-- > >Engin Gunduz > >RIPE NCC Software Engineering Departmen > > > >On 2004-11-08 12:55:51 +0100, Fredrik Widell wrote: > >>Hi all, > >> > >>currently (and for the last 1-2 weeks) I am utterly unable > >>to fetch/make filterlists for peers with large as-sets, > >>to mee it seems whois.ripe.net is quite unresponsive, and > >>sometimes even delivers the wrong results with peval, > >>the example I have most trouble with atm below: > >> > >>peval -h whois.ripe.net -protocol ripe -no-as "AS702 AS702:RS-EURO > >>AS702:RS-CUSTOMER" > >> > >>mostly, this justs exits with a "141 pipe broken", but, sometimes > >>the result is ((AS702)) which is very far from the truth. > >> > >>So, can I still trust ripe-dbm to create my filterlists? or should > >>I get other means to make my filters? > >> > >> > >> > >>-- > >> > >>Regards > >> > >> /Fredrik > >> > >>------------------------------------------------------- > >>KTHNOC, KTH, S-100 44 Stockholm, Sweden +46 8 790 65 17 > >>------------------------------------------------------- > > > > -- > > Mvh > > /Fredrik > > ------------------------------------------------------- > KTHNOC, KTH, S-100 44 Stockholm, Sweden +46 8 790 65 17 > ------------------------------------------------------- From ljb at merit.edu Fri Nov 19 07:02:52 2004 From: ljb at merit.edu (Larry J. Blunk) Date: Fri, 19 Nov 2004 01:02:52 -0500 (EST) Subject: [irrtoolset]Syntax errors in inet-rtr In-Reply-To: <375B4788-2F55-11D9-BA78-000A95D6AB8E@lixfeld.ca> References: <375B4788-2F55-11D9-BA78-000A95D6AB8E@lixfeld.ca> Message-ID: IRRd 2.2.1 has been released on www.irrd.net and fixes the bug mentioned below. Further, compatibility with the RIPE server has been improved so that you can now use the "-protocol ripe" option with IRRToolSet commands. In fact, you'll need to use this with IRRToolSet 4.8.2 due to some issues in IRRToolSet with respect to it's implementation of RADB commands. -Larry Blunk Merit On Fri, 5 Nov 2004, Jason Lixfeld wrote: > Trying to reference a peering-set in an inet-rtr: > > inet-rtr: router1.example.com > descr: AS1234 Example Company > alias: r1.example.com > local-as: AS1234 > ifaddr: 198.32.245.52 masklen 24 > peer: BGP4 prng-example asno(PeerAS) > tech-c: See MAINT-AS1234 > mnt-by: MAINT-AS1234 > changed: noc at example.com 20041105 > source: INTERNAL > > When I submit it, I get a message back complaining of a syntax error: > > UPDATE FAILED: [inet-rtr] router1.example.com > inet-rtr: router1.example.com > descr: AS1234 Example Company > alias: r1.example.com > local-as: AS1234 > ifaddr: 198.32.245.52 masklen 24 > peer: BGP4 prng-example asno(PeerAS) > tech-c: See MAINT-AS1234 > mnt-by: MAINT-AS1234 > changed: noc at example.com 20041105 > source: INTERNAL > #ERROR: 6: peer: Syntax error > > All the material I've read indicates that this syntax should work. > > Any ideas? > > From daniel.sanchez at cern.ch Wed Nov 24 15:28:07 2004 From: daniel.sanchez at cern.ch (Daniel Sanchez) Date: Wed, 24 Nov 2004 15:28:07 +0100 Subject: [irrtoolset]Rtconfig problem Message-ID: <41A49A77.9020401@cern.ch> Dear Mr or Miss, I am trying to set up RtConfig at CERN, to replace a local tool. In particular, I want to use an override file including local RPSL objects. However when running RtConfig with the -f option, it does not seem to take into consideration the objects in the override file, except for aut-num objects. As far as I remember, at the LIR course (here in Geneva, October 2004) we were told that any RPSL object could be put into the override file. Questions: - Do you confirm that only aut-num objects are accepted by RtConfig in an override file to be used with the -f option? - If so, what do you recommend if you want RtConfig to process local RPSL objects, which, for practical reasons, cannot be put into the RIPE data base? - Are there examples of RtConfig usage anywhere I can take as guidelines? yours sincerely, Daniel Sanchez