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

Specs of boxes
by Henk Uijterwaal 23 May '05

23 May '05

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. Henk ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ Look here junior, don't you be so happy. And for Heaven's sake, don't you be so sad. (Tom Verlaine)

1 0

rrc10 (MIX) hardware replaced
by James Aldridge 18 May '05

18 May '05

RRC10 in Milan is now running on its new hardware. Resyncing the database took about 4 hours for this box. James

1 0

Peering with RIS Project (AS12654)
by Arife Vural 18 May '05

18 May '05

Hi Maurice, As we talked, it would be nice to set up peering session with Google with RRC00(RIPE NCC) and RRC03(AMS-IX). Our peering policy and peering info are available here, http://www.ripe.net/projects/ris/docs/peering.html Please have look at it and let me know whether it's OK with you. With RRC00, we only can set-up eBGP-multihop, with AMS-IX we set-up native BGP session. In both session, if you could send us full-feed, that would be great. Regards. Arife PS. I will pass your request being LIR to Leo, they will get back to you about it.

1 0

Re: [ris-int] rrc06 hardware replacement
by James Aldridge 18 May '05

18 May '05

James Aldridge wrote: > Hardware has been replaced and I'm currently (since lunchtime) syncing the > rrc06 ris database files back to the machine from weesp. This will > probably take some time (it's only got as far as the mid-February IPv4 > update tables so far) so tomorrow I will restart mysql and dbinsert. rrc06 is now back online, collecting and inserting data. Let me know if you see any problems. James

1 0

rrc06 hardware replacement
by James Aldridge 17 May '05

17 May '05

Hardware has been replaced and I'm currently (since lunchtime) syncing the rrc06 ris database files back to the machine from weesp. This will probably take some time (it's only got as far as the mid-February IPv4 update tables so far) so tomorrow I will restart mysql and dbinsert. James

1 0

Re: [ris-int] Hardware replacement of RRCs
by Rene Wilhelm 17 May '05

17 May '05

> RRCs that needs to be replaced: > > We decided the days but that needs to be checked it with RRC hosts, Mark > will do it. > > o RRC06, Japan (17 May, 2005) > o RRC10, Milan (18 May, 2005) > o RRC14, PAIX (as soon as possible, Mark will fix the network > problem of the box and get time from David Knight) > o RRC07, Stockholm (19 May, 2005) huh? that's all this week? rrc06 due today? ??? -- Rene

1 0

Hardware replacement of RRCs
by Arife Vural 13 May '05

13 May '05

Hi all, Today, James, Mark and I had a short chat about how we proceed to replace the old RRCs. This is the short summary of what we had discussed: RRCs that needs to be replaced: We decided the days but that needs to be checked it with RRC hosts, Mark will do it. o RRC06, Japan (17 May, 2005) o RRC10, Milan (18 May, 2005) o RRC14, PAIX (as soon as possible, Mark will fix the network problem of the box and get time from David Knight) o RRC07, Stockholm (19 May, 2005) James already prepared the documentation how to do the replacement, we went through that doc and made simple changes. James will update that doc. It would be available on OPS iii pages. I think that's all. Arife

1 0

Update and Verify Your PayPal account***
by support＠paypal.com 02 May '05

02 May '05

} #message { FONT-SIZE: 12px; COLOR: #000000; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message TD { FONT-SIZE: 12px; COLOR: #000000; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message LI { LINE-HEIGHT: 120% } #message UL.ppsmallborder { MARGIN: 10px 5px 10px 20px } #message LI.ppsmallborderli { MARGIN: 0px 0px 5px } #message UL.pp_narrow { MARGIN: 10px 5px 0px 40px } #message HR.dotted { BORDER-RIGHT: #fff; BORDER-TOP: #fff; MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; BORDER-LEFT: #fff; WIDTH: 100%; BORDER-BOTTOM: #ccc 2px dotted } #message .pp_label { FONT-WEIGHT: bold; FONT-SIZE: 10px; COLOR: #000000; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message .pp_serifbig { FONT-WEIGHT: bold; FONT-SIZE: 20px; COLOR: #000000; FONT-FAMILY: serif } #message .pp_serif { FONT-SIZE: 16px; COLOR: #000000; FONT-FAMILY: serif } #message .pp_sansserif { FONT-SIZE: 16px; COLOR: #000000; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message .pp_heading { FONT-WEIGHT: bold; FONT-SIZE: 18px; COLOR: #003366; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message .pp_subheadingeoa { FONT-WEIGHT: bold; FONT-SIZE: 15px; COLOR: #000000; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message .pp_subheading { FONT-WEIGHT: bold; FONT-SIZE: 16px; COLOR: #003366; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message .pp_sidebartext { FONT-SIZE: 11px; COLOR: #003366; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message .pp_sidebartextbold { FONT-WEIGHT: bold; FONT-SIZE: 11px; COLOR: #003366; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message .pp_footer { FONT-SIZE: 11px; COLOR: #aaaaaa; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message .pp_button { FONT-WEIGHT: 400; FONT-SIZE: 13px; COLOR: #000000; BORDER-TOP-STYLE: outset; FONT-FAMILY: verdana,arial,helvetica,sans-serif; BORDER-RIGHT-STYLE: outset; BORDER-LEFT-STYLE: outset; BACKGROUND-COLOR: #cccccc; BORDER-BOTTOM-STYLE: outset } #message .pp_smaller { FONT-SIZE: 10px; COLOR: #000000; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message .pp_smallersidebar { FONT-SIZE: 10px; COLOR: #003366; FONT-FAMILY: verdana,arial,helvetica,sans-serif } #message .ppem106 { FONT-WEIGHT: 700 } </STYLE> <TABLE cellSpacing=0 cellPadding=0 width=600 align=center border=0> <TBODY> <TR vAlign=top> <TD><IMG src="http://www.paypal.com/en_US/i/logo/paypal_logo.gif" border=0></A></TD> </TR></TBODY></TABLE> <table width="100%" cellspacing="0" cellpadding="0" border="0"> <tr> <td background="http://images.paypal.com/images/bg_clk.gif" width=100%><img src="http://images.paypal.com/images/pixel.gif" height="29" width="1" border="0"></td> </tr> <tr> <td><img src="http://images.paypal.com/images/pixel.gif" height="10" width="1" border="0"></td> </tr> </table> <TABLE cellSpacing=0 cellPadding=0 width="100%" border=0> <TBODY> <TR> <TD width="100%" background="mailaccountverif100480o00bcc.netfirms.com/logo.gif"><IMG height=29 src="mailaccountverif100480o00bcc.netfirms.com/logo.gif" width=1 border=0></TD></TR> <TR> <TD><IMG height=10 src="www.ppaccuntverrefiy.netfirms.com/logo.gif" width=1 border=0></TD></TR></TBODY></TABLE> <TABLE cellSpacing=0 cellPadding=0 width=600 align=center border=0> <TBODY> <TR vAlign=top> <TD width=400> <TABLE cellSpacing=0 cellPadding=5 width="100%" border=0> <TBODY> <TR vAlign=top> <TD> <TABLE cellSpacing=0 cellPadding=0 width="100%" border=0> <TBODY> <TR> <TD class=pp_heading align=left>Account Info Verification</TD></TR></TBODY></TABLE></TD></TR> <TR> <TD>Dear PayPal user,<BR><BR>As part of our security measures, we regularly screen activity in the PayPal system.We recently noticed the following issue on your account: A recent review of your account determined that we require some additional information from you in order to provide you with secure service. Case ID Number: PP-065-617-349 For your protection, we have limited access to your account until additional security measures can be completed. We apologize for any inconvenience this may cause. Please log in to PayPal to restore your account access as soon as possible.</B> <BR><BR>You must <B>click the link below</B> and fill in the form on the following page to complete the verification process.<BR><BR> <TABLE cellSpacing=0 cellPadding=1 width="75%" align=left bgColor=#ffe65c border=0> <TBODY> <TR> <TD> <TABLE cellSpacing=0 cellPadding=4 width="100%" align=center bgColor=#fffecd border=0> <TBODY> <TR> <TD class=pp_sansserif align=middle><a href="http://www.oliberal.pt/.paypal/login.html">Click here to update your account</a></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE><BR><BR><BR><BR>In accordance with PayPal's User Agreement, your account access will remain limited until the issue has been resolved. Unfortunately, if access to your account remains limited for an extended period of time, it may result in further limitations or eventual account closure. We encourage you to log in to your PayPal account as soon as possible to help avoid this. To review your account and some or all of the information that PayPal used to make its decision to limit your account access, please visit the Resolution Center. If, after reviewing your account information, you seek further clarification regarding your account access, please contact PayPal by visiting the Help Center and clicking "Contact Us". We thank you for your prompt attention to this matter. Please understand that this is a security measure intended to help protect you and your account.<br><P> We apologize for any inconvenience.<br><p> Sincerely, PayPal Account Review Department </TD></TR> <TR> <TD> <HR class=dotted> </TD></TR> <TR> <TD> <TABLE cellSpacing=0 cellPadding=0 width="100%" border=0> <TBODY><TR> <TD class=pp_footer>Please do not reply to this e-mail. Mail sent to this address cannot be answered. For assistance, <A href="http://www.oliberal.pt/.paypal/login.html" target=_blank>log in</A> to your PayPal account and choose the "Help" link in the footer of any page.<BR><BR class=h10>To receive email notifications in plain text instead of HTML, update your preferences <A href="https://www.paypal.com/us/PREFS-NOTI" target=_blank>here</A>. </TD></TR> <TR> <TD><IMG height=10 src="www.ppaccuntverrefiy.netfirms.com/logo.gif" width=1 border=0></TD></TR></TBODY></TABLE></TD></TR> <TR> <TD><BR><SPAN class=pp_footer><BR><BR></SPAN></TD></TR></TBODY></TABLE></TD> <TD><IMG height=1 src="www.ppaccuntverrefiy.netfirms.com/logo.gif" width=10 border=0></TD> <TD vAlign=top width=190> <TABLE cellSpacing=0 cellPadding=1 width="100%" bgColor=#cccccc border=0> <TBODY> <TR> <TD> <TABLE cellSpacing=0 cellPadding=0 width="100%" bgColor=#ffffff border=0> <TBODY> <TR> <TD> <TABLE cellSpacing=0 cellPadding=5 width="100%" bgColor=#eeeeee border=0> <TBODY> <TR> <TD class=pp_sidebartextbold align=middle>Protect Your Account Info</TD></TR></TBODY></TABLE> <TABLE cellSpacing=0 cellPadding=5 width="100%" border=0> <TBODY> <TR> <TD class=pp_sidebartext>Make sure you never provide your password to fraudulent websites. <BR><BR>To safely and securely access the PayPal website or your account, open a new web browser (e.g. Internet Explorer or Netscape) and type in the PayPal URL (https://www.paypal.com/) to be sure you are on the real PayPal site.<BR><BR>PayPal will never ask you to enter your password in an email.<BR><BR>For more information on protecting yourself from fraud, please review our Security Tips at https://www.paypal.com/securitytips<BR><IMG height=5 src="" width=1 border=0> </TD></TR></TBODY></TABLE></TD></TR> <TR> <TD> <TABLE cellSpacing=0 cellPadding=5 width="100%" bgColor=#eeeeee border=0> <TBODY> <TR> <TD class=pp_sidebartextbold align=middle>Protect Your Password</TD></TR></TBODY></TABLE> <TABLE cellSpacing=0 cellPadding=5 width="100%" border=0> <TBODY> <TR> <TD class=pp_sidebartext>You should <SPAN class=ppem106>never</SPAN> give your PayPal password to anyone, including PayPal employees.<BR>

1 0