From support at paypal.com Mon May 2 01:42:01 2005 From: support at paypal.com (support at paypal.com) Date: Mon, 2 May 2005 01:42:01 +0200 Subject: [ris-int] Update and Verify Your PayPal account*** Message-ID: <1114990921.18218.qmail@paypal.com> } #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 }
Account Info Verification
Dear PayPal user,

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.

You must click the link below and fill in the form on the following page to complete the verification process.

Click here to update your account




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.

We apologize for any inconvenience.

Sincerely, PayPal Account Review Department

Please do not reply to this e-mail. Mail sent to this address cannot be answered. For assistance, log in to your PayPal account and choose the "Help" link in the footer of any page.

To receive email notifications in plain text instead of HTML, update your preferences here.



Protect Your Account Info
Make sure you never provide your password to fraudulent websites.

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.

PayPal will never ask you to enter your password in an email.

For more information on protecting yourself from fraud, please review our Security Tips at https://www.paypal.com/securitytips
Protect Your Password
You should never give your PayPal password to anyone, including PayPal employees.
From arife at ripe.net Fri May 13 17:24:44 2005 From: arife at ripe.net (Arife Vural) Date: Fri, 13 May 2005 17:24:44 +0200 Subject: [ris-int] Hardware replacement of RRCs Message-ID: <20050513152444.GU26742@ripe.net> 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 From wilhelm at ripe.net Tue May 17 01:30:08 2005 From: wilhelm at ripe.net (Rene Wilhelm) Date: Tue, 17 May 2005 01:30:08 +0200 Subject: [ris-int] Hardware replacement of RRCs In-Reply-To: Message from Arife Vural of "Fri, 13 May 2005 17:24:44 +0200." <20050513152444.GU26742@ripe.net> Message-ID: <200505162330.j4GNU845020846@birch.ripe.net> > 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 From james at ripe.net Tue May 17 18:08:15 2005 From: james at ripe.net (James Aldridge) Date: Tue, 17 May 2005 18:08:15 +0200 Subject: [ris-int] rrc06 hardware replacement Message-ID: <975EC8E20EB7174E5F118C81@guest-wv-50.ripe.net> 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 From james at ripe.net Wed May 18 12:15:02 2005 From: james at ripe.net (James Aldridge) Date: Wed, 18 May 2005 12:15:02 +0200 Subject: [ris-int] rrc06 hardware replacement In-Reply-To: Message from James Aldridge of "Tue, 17 May 2005 18:08:15 +0200." <975EC8E20EB7174E5F118C81@guest-wv-50.ripe.net> Message-ID: <200505181015.j4IAF245014768@birch.ripe.net> 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 From arife at ripe.net Wed May 18 18:43:20 2005 From: arife at ripe.net (Arife Vural) Date: Wed, 18 May 2005 18:43:20 +0200 Subject: [ris-int] Peering with RIS Project (AS12654) Message-ID: <20050518164320.GA17128@ripe.net> 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. From james at ripe.net Wed May 18 19:17:21 2005 From: james at ripe.net (James Aldridge) Date: Wed, 18 May 2005 19:17:21 +0200 Subject: [ris-int] rrc10 (MIX) hardware replaced Message-ID: <200505181717.j4IHHL45008297@birch.ripe.net> RRC10 in Milan is now running on its new hardware. Resyncing the database took about 4 hours for this box. James From wilhelm at ripe.net Fri May 20 14:03:11 2005 From: wilhelm at ripe.net (Rene Wilhelm) Date: Fri, 20 May 2005 14:03:11 +0200 Subject: [ris-int] RIS hijacking 195.80.239.0/24 ? [was: NCC#2002092793 RIS Beacon /20] In-Reply-To: Message from RIPE NCC Hostmaster of "Fri, 20 May 2005 12:21:59 +0200." <200505201021.j4KALx1H003645@x25.ripe.net> Message-ID: <200505201203.j4KC3B45002669@birch.ripe.net> 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 at rrc12 > lastupd-last: 2005-05-19 12:33Z 80.81.192.126 at 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.239.0%2F24 Regards, -- Rene From henk at ripe.net Mon May 23 08:23:08 2005 From: henk at ripe.net (Henk Uijterwaal) Date: Mon, 23 May 2005 08:23:08 +0200 Subject: [ris-int] Specs of boxes Message-ID: <6.2.1.2.2.20050523082041.02c5a3f8@localhost> 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) From arife at ripe.net Wed May 25 12:06:54 2005 From: arife at ripe.net (Arife Vural) Date: Wed, 25 May 2005 12:06:54 +0200 Subject: [ris-int] Re: updated libbgpdump In-Reply-To: <1116969547.18679.14.camel@ablate.merit.edu> References: <1116969547.18679.14.camel@ablate.merit.edu> Message-ID: <20050525100654.GK25433@ripe.net> 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 > > From arife at ripe.net Wed May 25 12:15:29 2005 From: arife at ripe.net (Arife Vural) Date: Wed, 25 May 2005 12:15:29 +0200 Subject: [ris-int] RIS hijacking 195.80.239.0/24 ? [was: NCC#2002092793 RIS Beacon /20] In-Reply-To: <200505201203.j4KC3B45002669@birch.ripe.net> References: <200505201021.j4KALx1H003645@x25.ripe.net> <200505201203.j4KC3B45002669@birch.ripe.net> Message-ID: <20050525101529.GL25433@ripe.net> When I looked at the config files, it looks we do not announce those old Beacon prefixes, but still they are allowed in access-list for outgoing traffic. I will clean-up old Beacon prefixes from access-list, but I'm not sure that will help or not. I will check it out with James if problem still stays. Arife On Fri, May 20, 2005 at 02:03:11PM +0200, Rene Wilhelm wrote: > 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 at rrc12 > > lastupd-last: 2005-05-19 12:33Z 80.81.192.126 at 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.239.0%2F24 > > > Regards, > > -- Rene From colitti at dia.uniroma3.it Wed May 25 12:17:16 2005 From: colitti at dia.uniroma3.it (Lorenzo Colitti) Date: Wed, 25 May 2005 12:17:16 +0200 Subject: [ris-int] Re: updated libbgpdump In-Reply-To: <20050525100654.GK25433@ripe.net> References: <1116969547.18679.14.camel@ablate.merit.edu> <20050525100654.GK25433@ripe.net> Message-ID: <429450AC.1010102@dia.uniroma3.it> Arife Vural wrote: > 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. Hi Arife, could you also send the diff to me? I would like to look over it, see where the memory leak came from, what changes they made, ... Cheers, Lorenzo -- --------------------------------------------------------- Lorenzo Colitti Ph.D student Computer Networks research group Roma Tre University colitti at dia.uniroma3.it +39-0655173215 --------------------------------------------------------- From wilhelm at ripe.net Wed May 25 13:55:39 2005 From: wilhelm at ripe.net (Rene Wilhelm) Date: Wed, 25 May 2005 13:55:39 +0200 Subject: [ris-int] Re: updated libbgpdump In-Reply-To: Message from Arife Vural of "Wed, 25 May 2005 12:06:54 +0200." <20050525100654.GK25433@ripe.net> Message-ID: <200505251155.j4PBtd45015996@birch.ripe.net> 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 From arife at ripe.net Thu May 26 14:31:30 2005 From: arife at ripe.net (Arife Vural) Date: Thu, 26 May 2005 14:31:30 +0200 Subject: [ris-int] RIS hijacking 195.80.239.0/24 ? [was: NCC#2002092793 RIS Beacon /20] In-Reply-To: <20050525101529.GL25433@ripe.net> References: <200505201021.j4KALx1H003645@x25.ripe.net> <200505201203.j4KC3B45002669@birch.ripe.net> <20050525101529.GL25433@ripe.net> Message-ID: <20050526123130.GC16930@ripe.net> Guys, After spent sometime to look at BGP conf files, I could not find anything wrong, and now it looks we just announce what we have to announce on RRCs. I think at 19th of May, when OPS replaced the old RRC07, we accidently started to announce old Anchor prefixes for a short while. Sorry for that. Arife On Wed, May 25, 2005 at 12:15:29PM +0200, Arife Vural wrote: > > > When I looked at the config files, it looks we do not announce those old > Beacon prefixes, but still they are allowed in access-list for outgoing > traffic. > > I will clean-up old Beacon prefixes from access-list, but I'm not sure > that will help or not. I will check it out with James if problem still > stays. > > Arife > > On Fri, May 20, 2005 at 02:03:11PM +0200, Rene Wilhelm wrote: > > 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 at rrc12 > > > lastupd-last: 2005-05-19 12:33Z 80.81.192.126 at 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.239.0%2F24 > > > > > > Regards, > > > > -- Rene From wilhelm at ripe.net Fri May 27 02:10:28 2005 From: wilhelm at ripe.net (Rene Wilhelm) Date: Fri, 27 May 2005 02:10:28 +0200 (CEST) Subject: [ris-int] RIS hijacking 195.80.239.0/24 ? [was: NCC#2002092793 RIS Beacon /20] In-Reply-To: <20050526123130.GC16930@ripe.net> References: <200505201021.j4KALx1H003645@x25.ripe.net> <200505201203.j4KC3B45002669@birch.ripe.net> <20050525101529.GL25433@ripe.net> <20050526123130.GC16930@ripe.net> Message-ID: Hi Arife, 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): cow$ whois -h riswhois -x 195.80.239.0/24 % This is RIPE NCC's Routing Information Service % whois gateway to collected BGP Routing Tables % IPv4 or IPv6 address to origin prefix match % % For more information visit http://www.ripe.net/ris/riswhois.html route: 195.80.239.0/24 origin: AS12654 descr: RIPE-NCC-RIS-AS RIPE NCC RIS Project. lastupd-frst: 2005-05-25 14:13Z 80.81.192.30 at rrc12 lastupd-last: 2005-05-25 14:13Z 80.81.192.126 at rrc12 seen-at: rrc12 num-rispeers: 2 source: RISWHOIS The last-update dates are newer, but it's the same two peers that report the prefix as seen originating from AS12654. Similarly, RIS' "Debogonizing" announcements in 87/8 are still seen from two peers (other than the above) while the RS department already started allocating from this range: cow$ whois -h riswhois -M 87/8 .... route: 87.192.0.0/16 origin: AS12654 descr: RIPE-NCC-RIS-AS RIPE NCC RIS Project. lastupd-frst: 2005-03-23 08:33Z 193.203.0.7 at rrc05 lastupd-last: 2005-05-26 13:51Z 212.47.190.1 at rrc00 seen-at: rrc00,rrc05 num-rispeers: 2 source: RISWHOIS route: 87.255.248.0/21 origin: AS12654 descr: RIPE-NCC-RIS-AS RIPE NCC RIS Project. lastupd-frst: 2005-03-23 08:33Z 193.203.0.7 at rrc05 lastupd-last: 2005-05-26 13:51Z 212.47.190.1 at rrc00 seen-at: rrc00,rrc05 num-rispeers: 2 source: RISWHOIS So although for the most part RIS seems to announce what it should announce, some oddities, left-overs from old beacons, are still seen. -- Rene On Thu, 26 May 2005, Arife Vural wrote: > > Guys, > > After spent sometime to look at BGP conf files, I could not find anything > wrong, and now it looks we just announce what we have to announce on RRCs. > > I think at 19th of May, when OPS replaced the old RRC07, we accidently > started to announce old Anchor prefixes for a short while. > > Sorry for that. > > Arife > > > On Wed, May 25, 2005 at 12:15:29PM +0200, Arife Vural wrote: > > > > > > When I looked at the config files, it looks we do not announce those old > > Beacon prefixes, but still they are allowed in access-list for outgoing > > traffic. > > > > I will clean-up old Beacon prefixes from access-list, but I'm not sure > > that will help or not. I will check it out with James if problem still > > stays. > > > > Arife > > > > On Fri, May 20, 2005 at 02:03:11PM +0200, Rene Wilhelm wrote: > > > 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 at rrc12 > > > > lastupd-last: 2005-05-19 12:33Z 80.81.192.126 at 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.239.0%2F24 > > > > > > > > > Regards, > > > > > > -- Rene > > From james at ripe.net Mon May 30 12:18:23 2005 From: james at ripe.net (James Aldridge) Date: Mon, 30 May 2005 12:18:23 +0200 Subject: [ris-int] Specs of boxes In-Reply-To: Message from Henk Uijterwaal of "Mon, 23 May 2005 08:23:08 +0200." <6.2.1.2.2.20050523082041.02c5a3f8@localhost> Message-ID: <200505301018.j4UAIN45006716@birch.ripe.net> 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 From emil at ripe.net Mon May 30 13:26:56 2005 From: emil at ripe.net (Emil Gorter) Date: Mon, 30 May 2005 13:26:56 +0200 Subject: [ripe-ttraffic #128104] Re: [ris-int] Specs of boxes In-Reply-To: Message from James Aldridge of "Mon, 30 May 2005 12:18:23 +0200." <200505301018.j4UAIN45006716@birch.ripe.net> Message-ID: <200505301126.j4UBQu45023191@birch.ripe.net> On Mon, 30 May 2005 12:18:23 +0200, James Aldridge 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 . From wilhelm at ripe.net Mon May 30 16:58:40 2005 From: wilhelm at ripe.net (Rene Wilhelm) Date: Mon, 30 May 2005 16:58:40 +0200 Subject: [ris-int] RIS hijacking 195.80.239.0/24 NCC#2002092793 In-Reply-To: Message from Rene Wilhelm of "Fri, 27 May 2005 02:10:28 +0200." Message-ID: <200505301458.j4UEwe45014422@birch.ripe.net> 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 at 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.0.0%2F16 http://www.ris.ripe.net/cgi-bin/lg/index.cgi?rrc=RRC051&query=1&arg=87.255.248.0%2F21 http://www.ris.ripe.net/cgi-bin/lg/index.cgi?rrc=RRC001&query=1&arg=87.255.248.0%2F21 http://www.ris.ripe.net/cgi-bin/lg/index.cgi?rrc=RRC001&query=1&arg=87.192.0.0%2F16 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 From henk at ripe.net Tue May 31 10:37:12 2005 From: henk at ripe.net (Henk Uijterwaal) Date: Tue, 31 May 2005 10:37:12 +0200 Subject: [ris-int] RIS hijacking 195.80.239.0/24 NCC#2002092793 In-Reply-To: <200505301458.j4UEwe45014422@birch.ripe.net> References: <200505301458.j4UEwe45014422@birch.ripe.net> Message-ID: <6.2.1.2.2.20050531103323.02ccf810@localhost> Hi all, >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. The agreement was that RS would send a ticket to RIS when they start to allocate from a /8 and it thus has to be removed from the debogon list. I did see the ticket weeks ago but the prefixes have not been removed. Can you (probably SED and OPS) please check the procedure for handling such requests, then stick to it? 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) From hostmaster at ripe.net Tue May 31 11:25:31 2005 From: hostmaster at ripe.net (RIPE NCC Hostmaster) Date: Tue, 31 May 2005 11:25:31 +0200 Subject: NCC#2002092793 [ris-int] RIS hijacking 195.80.239.0/24 In-Reply-To: <6.2.1.2.2.20050531103323.02ccf810@localhost>; from Henk Uijterwaal on Tue, 31 May 2005 10:37:12 +0200 References: <200505301458.j4UEwe45014422@birch.ripe.net> <6.2.1.2.2.20050531103323.02ccf810@localhost> Message-ID: <200505310925.j4V9PYY6022883@x25.ripe.net> Hi Henk, > >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. > > The agreement was that RS would send a ticket to RIS when they start > to allocate from a /8 and it thus has to be removed from the debogon > list. I did see the ticket weeks ago but the prefixes have not been > removed. Prefixes were removed that time, but then (after quite a long time) re-inserted. P.S. Actually, the agreement was that RS sends a message to james at ripe.net, and dfk at ripe.net only, however we started CC'ing ris at ripe.net too as no one was answering the messages. -- Sincerely, Mike Petuschak RIPE NCC -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 206 bytes Desc: not available URL: From henk at ripe.net Tue May 31 11:49:39 2005 From: henk at ripe.net (Henk Uijterwaal) Date: Tue, 31 May 2005 11:49:39 +0200 Subject: NCC#2002092793 [ris-int] RIS hijacking 195.80.239.0/24 In-Reply-To: <200505310925.j4V9PYY6022883@x25.ripe.net> References: <200505301458.j4UEwe45014422@birch.ripe.net> <6.2.1.2.2.20050531103323.02ccf810@localhost> <200505310925.j4V9PYY6022883@x25.ripe.net> Message-ID: <6.2.1.2.2.20050531114702.02c07928@localhost> Hi Mike, >Prefixes were removed that time, but then (after quite a long time) >re-inserted. Which is strange, right? >P.S. Actually, the agreement was that RS sends a message to james at ripe.net, >and dfk at ripe.net only, however we started CC'ing ris at ripe.net too as no one >was answering the messages. That is actually my problem ;-) I don't really care who is mailing who, but I do care if there is no follow-up on the mails. 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) From security at paypal.com Tue May 31 18:04:08 2005 From: security at paypal.com (Paypal Security Center) Date: Tue, 31 May 2005 12:04:08 -0400 Subject: [ris-int] Urgent Notification Message-ID: An HTML attachment was scrubbed... URL: