- Ris-int - mailman.ripe.net

Re: updated libbgpdump
by Arife Vural 09 Jun '05

09 Jun '05

Hi Larry, Thanks getting back to me quickly. This week I will look at the changes you made and submit to CVS, also my plan is to put this lib into our public CVS. I will let you know about the progress. Regards. Arife On Tue, May 24, 2005 at 05:19:07PM -0400, Larry J. Blunk wrote: > Hi all, > Good to see you at NANOG. I've attached our updates to > the libbgpdump code. Here's a list of our changes -- > > 1) Fixed memleak in bgpdump_free_mp_info() > 2) Created new_bgpdump_open_dump() library interface with > option flags to control desired level of parsing of data. > 3) Improved efficiency of mstream code (added macros). > 4) Added support for older MRTD format BGP messages (used > for early RIPE RIS collection). > 5) Added length field sanity check for corrupted data. > 6) Improved tracking of truncated messages (Zebra bug). > > > -Larry Blunk > Merit > >

2 2

Re: [ris-int] RIS hijacking 195.80.239.0/24 NCC#2002092793
by Rene Wilhelm 08 Jun '05

08 Jun '05

Hi Arife, Last friday I wrote: > Something still seems wrong, riswhois still sees the prefix in the dumps > and presumably looking glass will also report them. (no time to check > those right now): Checking looking glasses today, 195.80.239.0/24 is no longer seen. RISwhois still sees it, but that's due to rrc12 raw data not making it to halfweg.ripe.net since thursday May 26th. (subject of another ris(a)ripe.net ticket) However, the debogon prefixes 87.192.0.0/16 and 87.255.248.0/21 are still seen in the RRC looking glasses: http://www.ris.ripe.net/cgi-bin/lg/index.cgi?rrc=RRC051&query=1&arg=87.192.… http://www.ris.ripe.net/cgi-bin/lg/index.cgi?rrc=RRC051&query=1&arg=87.255.… http://www.ris.ripe.net/cgi-bin/lg/index.cgi?rrc=RRC001&query=1&arg=87.255.… http://www.ris.ripe.net/cgi-bin/lg/index.cgi?rrc=RRC001&query=1&arg=87.192.… If you or James or someone else took specific action to make 195.80.239.0/24 go away, you may want to do the same for these prefixes under 87/8. Cheers, -- Rene

4 9

Urgent Notification
by Paypal Security Center 08 Jun '05

08 Jun '05

1 0

TKO Notice: ***Urgent Safeharbor Department Notice***
by aw-confirm＠eBay.com 07 Jun '05

07 Jun '05

1 0

Urgent Notification
by Paypal Security Center 03 Jun '05

03 Jun '05

1 0

Urgent Notification
by Paypal Security Center 31 May '05

31 May '05

1 0

Re: [ripe-ttraffic #128104] Re: [ris-int] Specs of boxes
by Emil Gorter 30 May '05

30 May '05

On Mon, 30 May 2005 12:18:23 +0200, James Aldridge <james(a)ripe.net> wrote: > - Dell PowerEdge 1850 > + 2 x 146 GB Disk > + PERC4 RAID controller > I'm not 100% certain of the exact RAID setup... Emil will probably now more > as his name's on the purchase order (#200503032). It's pre-configured RAID1. You can't do much else since the PE1850 has only two disk bays. Cheers, E m i l .

1 0

Re: [ris-int] Specs of boxes
by James Aldridge 30 May '05

30 May '05

Henk Uijterwaal wrote: > Hi, > > Does anybody have the exact specs of the latest TB's and RRC's that we > bought? Exact as in sufficient to go to the Dell site, click, order. > I'm discussing installation of boxes with LACNIC and they want to figure > out if it is cheaper to buy the boxes in Brazil. I have already told them > that we'll only do this if they buy exactly what we tell them to. The latest RRCs (the replacements for rrc{06,07,10,14}) are: - Dell PowerEdge 1850 + Dual 3GHz CPU (1MB cache) + 2 x 1GB RAM + 2 x 146 GB Disk + PERC4 RAID controller + 2nd PSU I'm not 100% certain of the exact RAID setup... Emil will probably now more as his name's on the purchase order (#200503032). James

1 0

RIS hijacking 195.80.239.0/24 ? [was: NCC#2002092793 RIS Beacon /20]
by Rene Wilhelm 27 May '05

27 May '05

Hi Mike, > You returned 195.80.224/20 in February so we wanted to start using the range > for our customers now. > > However for some reasons you started using it again for RIS. > > whois -h riswhois -M 195.80.224/20 > > route: 195.80.239.0/24 > origin: AS12654 > descr: RIPE-NCC-RIS-AS RIPE NCC RIS Project. > lastupd-frst: 2005-05-19 11:33Z 80.81.192.30@rrc12 > lastupd-last: 2005-05-19 12:33Z 80.81.192.126@rrc12 > seen-at: rrc12 > num-rispeers: 2 > source: RISWHOIS > > > So, what are you plans now? I think this announcement somehow came back by mistake. RIS is not allowed to use the address range as it has been returned to you officially. The RIS operators should be able to find out what exactly is happening, I'm cc-ing them (as well as the internal ris-int list) on this mail. RIS folk: Though querying the RIS DB for this range via the risearch.html CGI yields zero results, the looking-glass pages do see 195.80.239.0/24 being announced to rrc12 by 2 peers at the DE-CIX. http://www.ris.ripe.net/cgi-bin/lg/index.cgi?rrc=RRC121&query=1&arg=195.80.… Regards, -- Rene

2 3

Re: [ris-int] Re: updated libbgpdump
by Rene Wilhelm 25 May '05

25 May '05

On Tue, May 24, 2005 at 05:19:07PM -0400, Larry J. Blunk wrote: > 4) Added support for older MRTD format BGP messages (used > for early RIPE RIS collection). Ah, I already wondered why my libbgpdump based ASN counting program didn't work for data prior to august 2000; this explains! -- Rene

1 0