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]peval & whois.ripe.net

  • To: Fredrik Widell < >
  • From: Engin Gunduz < >
  • Date: Thu, 18 Nov 2004 10:43:33 +0100

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
> -------------------------------------------------------



<<< 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