[ris-int] RISwhois inverse qeury request.
Tue Jul 5 22:42:26 CEST 2005
Hi Rene, We briefly discussed this issue on Monday. If you would have time to do those changes, please feel free to modify RISwhois, and do not forget to update NCC CVS. Arife On Fri, Jul 01, 2005 at 06:47:53PM +0200, Rene Wilhelm wrote: > This was on my wish list, and has now been requested by an external user. > > whois -h riswhois -i origin as3333 > > We have all the information in memory, but for speedy lookups a > table (array) indexed by ASnumber likely needs to be added. > > It would certainly be a usefull addition to RISwhois. > > -- Rene > > > > ------- Forwarded Message > > From: Vincent Gillet <vgi at utopia.opentransit.net> > Date: Fri, 1 Jul 2005 18:32:26 +0200 > To: ris at ripe.net > > Hi, > > I use rather often RISwhois. > > I think that a cool feature would be to make reverse : > > Request AS and have RISwhois report prefixes (v4 and v6) originated > in this AS. > > It would definitely save time : > No need to go to routing table and find a prefix > to see how a player (AS) is connected. > > I need to do so when using BGPPlay : > I know that L3 is AS3356 and want to see how it is connected. > Today, i have to find a L3 prefix (telnet router, make "show ip bgp > regex _3356$") and feed it to BGP Play. > > "reverse RISWhois" would save telnet (or looking-glass) step. > > My .02$ > > Vincent. > > > ------- End of Forwarded Message
[ Ris-int Archive ]