From arife at ripe.net Wed Sep 1 00:29:53 2004 From: arife at ripe.net (Arife Vural) Date: Wed, 1 Sep 2004 00:29:53 +0200 Subject: [ris-int] Re: RIS box @ MAE-West In-Reply-To: <200408311118.55380.Peter_Losher@isc.org> References: <0I390034HO45ZI@pmismtp02.mcilink.com> <200408310207.09924.Peter_Losher@isc.org> <20040831091651.GB29813@ripe.net> <200408311118.55380.Peter_Losher@isc.org> Message-ID: <20040831222953.GA20545@ripe.net> > > BTW, what do you want the PTR record for the management address to be? rrc141.ripe.net, please. arife From matthew at ripe.net Wed Sep 1 02:06:42 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 31 Aug 2004 20:06:42 -0400 Subject: [ris-int] http://www4.ripe.net/ris/ In-Reply-To: <20040830112125.GI532@ripe.net> Message-ID: <001101c48fb7$9fdeea70$0e2aefcc@rockstar> I won't be able to make pre-13 Sept. :( Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Arife Vural > Sent: 30 August 2004 07:21 > To: Matthew Williams > Cc: ris-int at ripe.net > Subject: Re: [ris-int] http://www4.ripe.net/ris/ > > > > > Did a little more work there. Pls check it out. > > > > We should probably plan one more meeting (dedicated afternoon?) for > > going through the final stuff. > > Sure. Could you set it on Ctime? > > Arife > From Peter_Losher at isc.org Wed Sep 1 03:03:44 2004 From: Peter_Losher at isc.org (Peter Losher) Date: Tue, 31 Aug 2004 18:03:44 -0700 Subject: [ris-int] Re: RIS box @ MAE-West In-Reply-To: <20040831222953.GA20545@ripe.net> References: <0I390034HO45ZI@pmismtp02.mcilink.com> <200408311118.55380.Peter_Losher@isc.org> <20040831222953.GA20545@ripe.net> Message-ID: <200408311803.56088.Peter_Losher@isc.org> On Tuesday 31 August 2004 03:29 pm, Arife Vural wrote: > > BTW, what do you want the PTR record for the management address to be? > > rrc141.ripe.net, please. Here is your new network info IP: 204.152.184.27/27 Gateway: 204.152.184.1 The in-addr.arpa record for 204.152.184.27 is being propagated now. Let me know if you need a local resolver, etc. Also, would you like to enable IPv6 on this box? Best Wishes - Peter -- Peter_Losher at isc.org | ISC | OpenPGP 0xE8048D08 | "The bits must flow" -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available URL: From arife at ripe.net Wed Sep 1 11:25:53 2004 From: arife at ripe.net (Arife Vural) Date: Wed, 1 Sep 2004 11:25:53 +0200 Subject: [ris-int] http://www4.ripe.net/ris/ In-Reply-To: <001101c48fb7$9fdeea70$0e2aefcc@rockstar> References: <20040830112125.GI532@ripe.net> <001101c48fb7$9fdeea70$0e2aefcc@rockstar> Message-ID: <20040901092553.GB19621@ripe.net> > I won't be able to make pre-13 Sept. :( I will go through RIS pages before 13 Sep once more and fix the things that does not look right. I do not think there is much things that needs to be changed, though. After you get back, we will go through together in more detail. Arife From arife at ripe.net Wed Sep 1 11:31:03 2004 From: arife at ripe.net (Arife Vural) Date: Wed, 1 Sep 2004 11:31:03 +0200 Subject: [ris-int] Re: RIS box @ MAE-West In-Reply-To: <200408311803.56088.Peter_Losher@isc.org> References: <0I390034HO45ZI@pmismtp02.mcilink.com> <200408311118.55380.Peter_Losher@isc.org> <20040831222953.GA20545@ripe.net> <200408311803.56088.Peter_Losher@isc.org> Message-ID: <20040901093103.GC19621@ripe.net> > Here is your new network info > > IP: 204.152.184.27/27 > Gateway: 204.152.184.1 > > The in-addr.arpa record for 204.152.184.27 is being propagated now. Thanks. > > Let me know if you need a local resolver, etc. Also, would you like to enable That would be nice if you have local resolver and ntp server on the same LAN. > IPv6 on this box? Yes, that would be nice as well. Can we use the same interface we use for IPv4 or do we need seperate network card for IPv6? Regards. Arife From arife at ripe.net Wed Sep 1 12:10:52 2004 From: arife at ripe.net (Arife Vural) Date: Wed, 1 Sep 2004 12:10:52 +0200 Subject: [ris-int] RIPE NCC RIS box (RRC08) is leaving MAE-West at 3rd of Sep, 2004 18.00 CEST. Message-ID: <20040901101052.GD19621@ripe.net> Dear All, Our Remote Route Collector will be disconnected from MAE-West as of 3rd Sep, 2004 18.00 CEST. Please do not forget to update your configs. Our peering info, IP address: 198.32.200.157 AS number: 12654 We will be available at PAIX so soon. If you are available there and like to peer with RIS, please send your details to rispeering at ripe.net. We will get back to you as soon as the RIS box is online at PAIX. Kind regards. Arife From arife at ripe.net Wed Sep 1 12:18:16 2004 From: arife at ripe.net (Arife Vural) Date: Wed, 1 Sep 2004 12:18:16 +0200 Subject: [ris-int] RIPE NCC RIS box (RRC08) is leaving MAE-West at 3rd of Sep, 2004 18.00 CEST. Message-ID: <20040901101816.GE19621@ripe.net> Dear All, Our Remote Route Collector will be disconnected from MAE-West as of 3rd Sep, 2004 18.00 CEST. We will relocate the RIS box at PAIX. We hope we would get more interest at PAIX. We are planning to put RIS box online sometime next week. When it's online, we will send an announcement to the list. Kind regards. Arife From matthew at ripe.net Thu Sep 2 00:28:51 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 1 Sep 2004 18:28:51 -0400 Subject: [ris-int] http://www4.ripe.net/ris/ In-Reply-To: <20040901092553.GB19621@ripe.net> Message-ID: <006f01c49073$14cf8680$212aefcc@rockstar> > After you get back, we will go through together in more detail. Sounds great :) Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Arife Vural > Sent: 01 September 2004 05:26 > To: Matthew Williams > Cc: ris-int at ripe.net > Subject: Re: [ris-int] http://www4.ripe.net/ris/ > > > > > I won't be able to make pre-13 Sept. :( > > I will go through RIS pages before 13 Sep once more and fix the > things that does not look right. I do not think there is much > things that needs to be changed, though. > > After you get back, we will go through together in more detail. > > Arife > From Peter_Losher at isc.org Thu Sep 2 02:48:07 2004 From: Peter_Losher at isc.org (Peter Losher) Date: Wed, 1 Sep 2004 17:48:07 -0700 Subject: [ris-int] Re: RIS box @ MAE-West In-Reply-To: <20040901093103.GC19621@ripe.net> References: <0I390034HO45ZI@pmismtp02.mcilink.com> <200408311803.56088.Peter_Losher@isc.org> <20040901093103.GC19621@ripe.net> Message-ID: <200409011748.10671.Peter_Losher@isc.org> On Wednesday 01 September 2004 02:31 am, Arife Vural wrote: > That would be nice if you have local resolver and ntp server on the > same LAN. Sure, the local resolver is 204.152.184.67, and you can use clock.isc.org to sync your clock using ntp. > Yes, that would be nice as well. Can we use the same interface we use for > IPv4 or do we need seperate network card for IPv6? No, you can use the same NIC for both IPv4 and IPv6. (we do it here all the time) We have started to go away from the standard EUI64 addressing for IPv6, so if you are running FreeBSD on that box, I can give you instructions on how to set the link local address so we can still use normal router advertisements to apply the prefix to it. Best Wishes - Peter -- Peter_Losher at isc.org | ISC | OpenPGP 0xE8048D08 | "The bits must flow" -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available URL: From gerard at ripe.net Thu Sep 2 09:32:24 2004 From: gerard at ripe.net (Gerard Leurs) Date: Thu, 2 Sep 2004 09:32:24 +0200 Subject: [ris-int] decommisioning abcoude Message-ID: <200409020732.i827WOh2008983@x44.ripe.net> Dear RIS team. Can you tell me if it is possible to start decommissioning abcoude? Some backgroundinfo: we are in the process of getting rid of all sparcs. By the end of this month only 5 sparcs will be in the SUN-support contract. And abcoude is not one of them, as it is a 2nd backup for weesp/halfweg. Thanks, Gerard. From arife at ripe.net Thu Sep 2 10:43:47 2004 From: arife at ripe.net (Arife Vural) Date: Thu, 2 Sep 2004 10:43:47 +0200 Subject: [ris-int] decommisioning abcoude In-Reply-To: <200409020732.i827WOh2008983@x44.ripe.net> References: <200409020732.i827WOh2008983@x44.ripe.net> Message-ID: <20040902084347.GC20397@ripe.net> Good morning Gerard, > Can you tell me if it is possible to start decommissioning abcoude? > No, not by now. We are thinking to replace abcoude's hardware with Dell and continue to keep it as DB backup server or do some load balancing for DB queries. Until then, I prefer to leave abcoude running as DB backup server f or weesp. If it dies, we have the copy of data on weesp. That would not cause any trouble for us. Arife > Some backgroundinfo: we are in the process of getting rid of all > sparcs. By the end of this month only 5 sparcs will be in the > SUN-support contract. And abcoude is not one of them, as it is > a 2nd backup for weesp/halfweg. > > Thanks, > Gerard. From arife at ripe.net Thu Sep 2 11:16:32 2004 From: arife at ripe.net (Arife Vural) Date: Thu, 2 Sep 2004 11:16:32 +0200 Subject: [ris-int] let bug in bash and data collection Message-ID: <20040902091631.GG20397@ripe.net> FYI: Yesterday, begining of month, script that creates the rawdata dir on RRCs did not work because of let bug [1] in bash and rawdata was not collected on RRCs from 20040901 00:00 to 20040901 08:20 UTC. I fixed it when I noticed the problem in the morning yesterday. Arife [1] In bash the following lines does not work if x value is 8. let x=x+1 From james at ripe.net Thu Sep 2 12:37:48 2004 From: james at ripe.net (James Aldridge) Date: Thu, 02 Sep 2004 12:37:48 +0200 Subject: [ris-int] decommisioning abcoude In-Reply-To: <20040902084347.GC20397@ripe.net> References: <200409020732.i827WOh2008983@x44.ripe.net> <20040902084347.GC20397@ripe.net> Message-ID: <805FED14B87AF8CCFA5B54A1@[192.168.2.1]> --On Thursday, 2 September, 2004 10:43 +0200 Arife Vural wrote: >> Can you tell me if it is possible to start decommissioning abcoude? >> > > No, not by now. We are thinking to replace abcoude's hardware with > Dell and continue to keep it as DB backup server or do some load > balancing for DB queries. > > Until then, I prefer to leave abcoude running as DB backup server f > or weesp. If it dies, we have the copy of data on weesp. That would > not cause any trouble for us. Hmmmm... wasn't weesp already bought as abcoude's replacement (with a note that halfweg might need upgrading or replacing in 2004)? All that's left on abcoude is the Mammoth tape drive which, I guess, should be moved to weesp, and the RAID system. James From arife at ripe.net Thu Sep 2 12:46:33 2004 From: arife at ripe.net (Arife Vural) Date: Thu, 2 Sep 2004 12:46:33 +0200 Subject: [ris-int] decommisioning abcoude In-Reply-To: <805FED14B87AF8CCFA5B54A1@[192.168.2.1]> References: <200409020732.i827WOh2008983@x44.ripe.net> <20040902084347.GC20397@ripe.net> <805FED14B87AF8CCFA5B54A1@[192.168.2.1]> Message-ID: <20040902104633.GJ20397@ripe.net> > Hmmmm... wasn't weesp already bought as abcoude's replacement (with a note > that halfweg might need upgrading or replacing in 2004)? Yes, that was the intention. As Gerard suggest let's discuss it on Monday meeting whether we like to have backup DB server or not. > All that's left on abcoude is the Mammoth tape drive which, I guess, should > be moved to weesp, and the RAID system. Mammoth is already attached to halfweg. Arife From shane at ripe.net Thu Sep 2 15:28:55 2004 From: shane at ripe.net (Shane Kerr) Date: Thu, 02 Sep 2004 15:28:55 +0200 Subject: [ris-int] Re: [sed] let bug in bash and data collection In-Reply-To: <20040902091631.GG20397@ripe.net> References: <20040902091631.GG20397@ripe.net> Message-ID: <41372017.8050007@ripe.net> Arife Vural wrote: > FYI: Yesterday, begining of month, script that creates the rawdata dir > on RRCs did not work because of let bug [1] in bash and rawdata was not > collected on RRCs from 20040901 00:00 to 20040901 08:20 UTC. > > I fixed it when I noticed the problem in the morning yesterday. > > Arife > > [1] In bash the following lines does not work if x value is 8. > > let x=x+1 Surely you mean if the value is "08": x17:shane:~ $ let x=6 x17:shane:~ $ echo $x 6 x17:shane:~ $ let x=x+1 x17:shane:~ $ echo $x 7 x17:shane:~ $ let x=x+1 x17:shane:~ $ echo $x 8 x17:shane:~ $ let x=x+1 x17:shane:~ $ echo $x 9 x17:shane:~ $ let x=07+1 x17:shane:~ $ echo $x 8 x17:shane:~ $ let x=08+1 bash: let: x=08: value too great for base (error token is "08") This isn't a bug, it's a feature! For details, use "man strtol" and see the description for the special base value 0... -- Shane Kerr RIPE NCC From henk at ripe.net Thu Sep 2 17:33:37 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Thu, 2 Sep 2004 17:33:37 +0200 (CEST) Subject: [ris-int] decommisioning abcoude In-Reply-To: <805FED14B87AF8CCFA5B54A1@[192.168.2.1]> References: <200409020732.i827WOh2008983@x44.ripe.net> <20040902084347.GC20397@ripe.net> <805FED14B87AF8CCFA5B54A1@[192.168.2.1]> Message-ID: On Thu, 2 Sep 2004, James Aldridge wrote: > --On Thursday, 2 September, 2004 10:43 +0200 Arife Vural > wrote: > >> Can you tell me if it is possible to start decommissioning abcoude? > >> > > > > No, not by now. We are thinking to replace abcoude's hardware with > > Dell and continue to keep it as DB backup server or do some load > > balancing for DB queries. > > > > Until then, I prefer to leave abcoude running as DB backup server f > > or weesp. If it dies, we have the copy of data on weesp. That would > > not cause any trouble for us. > > Hmmmm... wasn't weesp already bought as abcoude's replacement (with a note > that halfweg might need upgrading or replacing in 2004)? That was my impression as well. IIRC, we left Abcoude on because it didn't do any harm, not becasue we need it. Henk > > All that's left on abcoude is the Mammoth tape drive which, I guess, should > be moved to weesp, and the RAID system. > > James > ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From joe.pucik at mci.com Thu Sep 2 17:42:10 2004 From: joe.pucik at mci.com (Joe Pucik) Date: Thu, 02 Sep 2004 08:42:10 -0700 Subject: [ris-int] Re: RIS box @ MAE-West In-Reply-To: <20040831091651.GB29813@ripe.net> Message-ID: <0I3F0062R7MBKR@pmismtp03.mcilink.com> Arife & Peter, The route collector (RRC08) was just turned down. I'll unrack this morning and then wait to hear from your team about the pickup. Joe Pucik Sr. Engineer MCI, MAE Engineering 408-975-2249 -----Original Message----- From: Arife Vural [mailto:arife at ripe.net] Sent: Tuesday, August 31, 2004 2:17 AM To: Peter Losher Cc: Joe Pucik; Thomas.Bechly at mci.com; ris-int at ripe.net; 'David Stephens' Subject: Re: [ris-int] Re: RIS box @ MAE-West > > That sounds good to me, I will shutdown the box at 9AM (Pacific) and > > then you can disconnect the box anytime that suits both of you guys. > > Sweet, that would be perfect :) Still awake :-) > > > BTW, Peter, until now I have not got any IP config info from Paul > > Vixie. Do you think you can help us to provide IP config at PAIX? It > > would be nice if we can do the changes before moving the box. > > That info will come from me, I'll get you the new network info later > today so you can preconfigure the box for management transit before > shutting it down. (Paul is still working on the PAIX switch port) OK, great. I will send an announcement to our peers today or tomorrow about moving the box. Arife From arife at ripe.net Thu Sep 2 17:50:36 2004 From: arife at ripe.net (Arife Vural) Date: Thu, 2 Sep 2004 17:50:36 +0200 Subject: [ris-int] Re: RIS box @ MAE-West In-Reply-To: <0I3F0062R7MBKR@pmismtp03.mcilink.com> References: <20040831091651.GB29813@ripe.net> <0I3F0062R7MBKR@pmismtp03.mcilink.com> Message-ID: <20040902155036.GL20397@ripe.net> Hi Joe, We are planning to unplug it tomorrow. 3rd of Sep, at 9.00 Pacific. If you have not move out from the rack, could you power on it and shutdown tomorrow? Arife On Thu, Sep 02, 2004 at 08:42:10AM -0700, Joe Pucik wrote: > Arife & Peter, > > The route collector (RRC08) was just turned down. I'll unrack > this morning and then wait to hear from your team about the > pickup. > > Joe Pucik > Sr. Engineer > MCI, MAE Engineering > 408-975-2249 > > > -----Original Message----- > From: Arife Vural [mailto:arife at ripe.net] > Sent: Tuesday, August 31, 2004 2:17 AM > To: Peter Losher > Cc: Joe Pucik; Thomas.Bechly at mci.com; ris-int at ripe.net; 'David > Stephens' > Subject: Re: [ris-int] Re: RIS box @ MAE-West > > > > > That sounds good to me, I will shutdown the box at 9AM > (Pacific) and > > > then you can disconnect the box anytime that suits both of > you guys. > > > > Sweet, that would be perfect :) > > Still awake :-) > > > > > > BTW, Peter, until now I have not got any IP config info from > Paul > > > Vixie. Do you think you can help us to provide IP config at > PAIX? It > > > would be nice if we can do the changes before moving the box. > > > > That info will come from me, I'll get you the new network info > later > > today so you can preconfigure the box for management transit > before > > shutting it down. (Paul is still working on the PAIX switch > port) > > OK, great. I will send an announcement to our peers today or > tomorrow > about moving the box. > > Arife From joe.pucik at mci.com Thu Sep 2 18:13:21 2004 From: joe.pucik at mci.com (Joe Pucik) Date: Thu, 02 Sep 2004 09:13:21 -0700 Subject: [ris-int] Re: RIS box @ MAE-West In-Reply-To: <20040902155036.GL20397@ripe.net> Message-ID: <0I3F007ES92BZU@pmismtp01.mcilink.com> No problem Joe -----Original Message----- From: Arife Vural [mailto:arife at ripe.net] Sent: Thursday, September 02, 2004 8:51 AM To: Joe Pucik Cc: 'Peter Losher'; Thomas.Bechly at mci.com; ris-int at ripe.net; 'David Stephens' Subject: Re: [ris-int] Re: RIS box @ MAE-West Hi Joe, We are planning to unplug it tomorrow. 3rd of Sep, at 9.00 Pacific. If you have not move out from the rack, could you power on it and shutdown tomorrow? Arife On Thu, Sep 02, 2004 at 08:42:10AM -0700, Joe Pucik wrote: > Arife & Peter, > > The route collector (RRC08) was just turned down. I'll unrack > this morning and then wait to hear from your team about the > pickup. > > Joe Pucik > Sr. Engineer > MCI, MAE Engineering > 408-975-2249 > > > -----Original Message----- > From: Arife Vural [mailto:arife at ripe.net] > Sent: Tuesday, August 31, 2004 2:17 AM > To: Peter Losher > Cc: Joe Pucik; Thomas.Bechly at mci.com; ris-int at ripe.net; 'David > Stephens' > Subject: Re: [ris-int] Re: RIS box @ MAE-West > > > > > That sounds good to me, I will shutdown the box at 9AM > (Pacific) and > > > then you can disconnect the box anytime that suits both of > you guys. > > > > Sweet, that would be perfect :) > > Still awake :-) > > > > > > BTW, Peter, until now I have not got any IP config info from > Paul > > > Vixie. Do you think you can help us to provide IP config at > PAIX? It > > > would be nice if we can do the changes before moving the box. > > > > That info will come from me, I'll get you the new network info > later > > today so you can preconfigure the box for management transit > before > > shutting it down. (Paul is still working on the PAIX switch > port) > > OK, great. I will send an announcement to our peers today or > tomorrow > about moving the box. > > Arife From arife at ripe.net Thu Sep 2 18:27:51 2004 From: arife at ripe.net (Arife Vural) Date: Thu, 2 Sep 2004 18:27:51 +0200 Subject: [ris-int] Re: RIS box @ MAE-West In-Reply-To: <0I3F007ES92BZU@pmismtp01.mcilink.com> References: <20040902155036.GL20397@ripe.net> <0I3F007ES92BZU@pmismtp01.mcilink.com> Message-ID: <20040902162751.GM20397@ripe.net> > No problem Thanks a lot. That will give me a chance to make IP address changes. Arife From Peter_Losher at isc.org Thu Sep 2 22:20:19 2004 From: Peter_Losher at isc.org (Peter Losher) Date: Thu, 2 Sep 2004 13:20:19 -0700 Subject: [ris-int] Re: RIS box @ MAE-West In-Reply-To: <20040902155036.GL20397@ripe.net> References: <20040831091651.GB29813@ripe.net> <0I3F0062R7MBKR@pmismtp03.mcilink.com> <20040902155036.GL20397@ripe.net> Message-ID: <200409021320.35725.Peter_Losher@isc.org> On Thursday 02 September 2004 08:50 am, Arife Vural wrote: > We are planning to unplug it tomorrow. 3rd of Sep, at 9.00 > Pacific. If you have not move out from the rack, could you > power on it and shutdown tomorrow? Can I pick up the system at around noon tomorrow (Friday)? -Peter -- Peter_Losher at isc.org | ISC | OpenPGP 0xE8048D08 | "The bits must flow" -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available URL: From arife at ripe.net Thu Sep 2 22:43:31 2004 From: arife at ripe.net (Arife Vural) Date: Thu, 2 Sep 2004 22:43:31 +0200 Subject: [ris-int] Re: RIS box @ MAE-West In-Reply-To: <0I3F007ES92BZU@pmismtp01.mcilink.com> References: <20040902155036.GL20397@ripe.net> <0I3F007ES92BZU@pmismtp01.mcilink.com> Message-ID: <20040902204331.GA4545@ripe.net> Hi Joe, rrc08 is still unreachable. Did you have chance to power on? Regards. Arife From joe.pucik at mci.com Thu Sep 2 22:59:27 2004 From: joe.pucik at mci.com (Joe Pucik) Date: Thu, 02 Sep 2004 13:59:27 -0700 Subject: [ris-int] Re: RIS box @ MAE-West In-Reply-To: <20040902204331.GA4545@ripe.net> Message-ID: <0I3F006QTMB5K6@pmismtp02.mcilink.com> It looks like the Linux OS did not load properly before. I've just rebooted and watching for the Linux 2.4.26-3 load to complete. More to come. Joe Pucik -----Original Message----- From: Arife Vural [mailto:arife at ripe.net] Sent: Thursday, September 02, 2004 1:44 PM To: Joe Pucik Cc: 'Peter Losher'; Thomas.Bechly at mci.com; ris-int at ripe.net; 'David Stephens' Subject: Re: [ris-int] Re: RIS box @ MAE-West Hi Joe, rrc08 is still unreachable. Did you have chance to power on? Regards. Arife From joe.pucik at mci.com Thu Sep 2 23:07:03 2004 From: joe.pucik at mci.com (Joe Pucik) Date: Thu, 02 Sep 2004 14:07:03 -0700 Subject: [ris-int] Re: RIS box @ MAE-West Message-ID: <0I3F006C9MNTQP@pmismtp03.mcilink.com> Arife, RRC08 is still trying to load Linux. Seems to be stuck in the load process. This is the 2nd reboot. Joe Pucik -----Original Message----- From: Joe Pucik [mailto:joe.pucik at mci.com] Sent: Thursday, September 02, 2004 1:59 PM To: 'Arife Vural' Cc: 'Peter Losher'; 'Thomas.Bechly at mci.com'; 'ris-int at ripe.net'; 'David Stephens' Subject: RE: [ris-int] Re: RIS box @ MAE-West It looks like the Linux OS did not load properly before. I've just rebooted and watching for the Linux 2.4.26-3 load to complete. More to come. Joe Pucik -----Original Message----- From: Arife Vural [mailto:arife at ripe.net] Sent: Thursday, September 02, 2004 1:44 PM To: Joe Pucik Cc: 'Peter Losher'; Thomas.Bechly at mci.com; ris-int at ripe.net; 'David Stephens' Subject: Re: [ris-int] Re: RIS box @ MAE-West Hi Joe, rrc08 is still unreachable. Did you have chance to power on? Regards. Arife From joe.pucik at mci.com Thu Sep 2 23:26:03 2004 From: joe.pucik at mci.com (Joe Pucik) Date: Thu, 02 Sep 2004 14:26:03 -0700 Subject: [ris-int] Re: RIS box @ MAE-West Message-ID: <0I3F00998NJIIN@pmismtp01.mcilink.com> Arife, RRC08 is still not completing the loading of Linux. I've rebooted a 3rd time with the same result. Any suggestions? Joe Pucik -----Original Message----- From: Joe Pucik [mailto:joe.pucik at mci.com] Sent: Thursday, September 02, 2004 2:07 PM To: 'Arife Vural' Cc: 'Peter Losher'; 'ris-int at ripe.net' Subject: RE: [ris-int] Re: RIS box @ MAE-West Arife, RRC08 is still trying to load Linux. Seems to be stuck in the load process. This is the 2nd reboot. Joe Pucik -----Original Message----- From: Joe Pucik [mailto:joe.pucik at mci.com] Sent: Thursday, September 02, 2004 1:59 PM To: 'Arife Vural' Cc: 'Peter Losher'; 'Thomas.Bechly at mci.com'; 'ris-int at ripe.net'; 'David Stephens' Subject: RE: [ris-int] Re: RIS box @ MAE-West It looks like the Linux OS did not load properly before. I've just rebooted and watching for the Linux 2.4.26-3 load to complete. More to come. Joe Pucik -----Original Message----- From: Arife Vural [mailto:arife at ripe.net] Sent: Thursday, September 02, 2004 1:44 PM To: Joe Pucik Cc: 'Peter Losher'; Thomas.Bechly at mci.com; ris-int at ripe.net; 'David Stephens' Subject: Re: [ris-int] Re: RIS box @ MAE-West Hi Joe, rrc08 is still unreachable. Did you have chance to power on? Regards. Arife From arife at ripe.net Thu Sep 2 23:39:11 2004 From: arife at ripe.net (Arife Vural) Date: Thu, 2 Sep 2004 23:39:11 +0200 Subject: [ris-int] Re: RIS box @ MAE-West In-Reply-To: <0I3F00998NJIIN@pmismtp01.mcilink.com> References: <0I3F00998NJIIN@pmismtp01.mcilink.com> Message-ID: <20040902213911.GA16881@ripe.net> Does it give any error or in which step it stops? BTW, do you have the installation CD? If we can not reboot it, Peter can do fresh installation at PAIX? Arife On Thu, Sep 02, 2004 at 02:26:03PM -0700, Joe Pucik wrote: > > Arife, > > RRC08 is still not completing the loading of Linux. I've rebooted > a 3rd time with the same result. > > Any suggestions? > > Joe Pucik > > -----Original Message----- > From: Joe Pucik [mailto:joe.pucik at mci.com] > Sent: Thursday, September 02, 2004 2:07 PM > To: 'Arife Vural' > Cc: 'Peter Losher'; 'ris-int at ripe.net' > Subject: RE: [ris-int] Re: RIS box @ MAE-West > > Arife, > > RRC08 is still trying to load Linux. Seems to be stuck in the > load process. This is the 2nd reboot. > > > Joe Pucik > > > -----Original Message----- > From: Joe Pucik [mailto:joe.pucik at mci.com] > Sent: Thursday, September 02, 2004 1:59 PM > To: 'Arife Vural' > Cc: 'Peter Losher'; 'Thomas.Bechly at mci.com'; 'ris-int at ripe.net'; > 'David Stephens' > Subject: RE: [ris-int] Re: RIS box @ MAE-West > > > It looks like the Linux OS did not load properly before. > > I've just rebooted and watching for the Linux 2.4.26-3 load to > complete. More to come. > > Joe Pucik > > > -----Original Message----- > From: Arife Vural [mailto:arife at ripe.net] > Sent: Thursday, September 02, 2004 1:44 PM > To: Joe Pucik > Cc: 'Peter Losher'; Thomas.Bechly at mci.com; ris-int at ripe.net; > 'David Stephens' > Subject: Re: [ris-int] Re: RIS box @ MAE-West > > > Hi Joe, > > rrc08 is still unreachable. Did you have chance to power > on? > > Regards. > Arife From joe.pucik at mci.com Fri Sep 3 00:05:00 2004 From: joe.pucik at mci.com (Joe Pucik) Date: Thu, 02 Sep 2004 15:05:00 -0700 Subject: [ris-int] Re: RIS box @ MAE-West In-Reply-To: <20040902213911.GA16881@ripe.net> Message-ID: <0I3F00265PCEI4@pmismtp05.mcilink.com> Arife, The load never got that far. ;( Yes, I have the RIPENCC RIS Installation CD dated 2004-06-09. I may not have the 1-2 page doc that came with it. Joe Pucik -----Original Message----- From: Arife Vural [mailto:arife at ripe.net] Sent: Thursday, September 02, 2004 2:39 PM To: Joe Pucik Cc: 'Peter Losher'; ris-int at ripe.net Subject: Re: [ris-int] Re: RIS box @ MAE-West Does it give any error or in which step it stops? BTW, do you have the installation CD? If we can not reboot it, Peter can do fresh installation at PAIX? Arife On Thu, Sep 02, 2004 at 02:26:03PM -0700, Joe Pucik wrote: > > Arife, > > RRC08 is still not completing the loading of Linux. I've rebooted > a 3rd time with the same result. > > Any suggestions? > > Joe Pucik > > -----Original Message----- > From: Joe Pucik [mailto:joe.pucik at mci.com] > Sent: Thursday, September 02, 2004 2:07 PM > To: 'Arife Vural' > Cc: 'Peter Losher'; 'ris-int at ripe.net' > Subject: RE: [ris-int] Re: RIS box @ MAE-West > > Arife, > > RRC08 is still trying to load Linux. Seems to be stuck in the > load process. This is the 2nd reboot. > > > Joe Pucik > > > -----Original Message----- > From: Joe Pucik [mailto:joe.pucik at mci.com] > Sent: Thursday, September 02, 2004 1:59 PM > To: 'Arife Vural' > Cc: 'Peter Losher'; 'Thomas.Bechly at mci.com'; 'ris-int at ripe.net'; > 'David Stephens' > Subject: RE: [ris-int] Re: RIS box @ MAE-West > > > It looks like the Linux OS did not load properly before. > > I've just rebooted and watching for the Linux 2.4.26-3 load to > complete. More to come. > > Joe Pucik > > > -----Original Message----- > From: Arife Vural [mailto:arife at ripe.net] > Sent: Thursday, September 02, 2004 1:44 PM > To: Joe Pucik > Cc: 'Peter Losher'; Thomas.Bechly at mci.com; ris-int at ripe.net; > 'David Stephens' > Subject: Re: [ris-int] Re: RIS box @ MAE-West > > > Hi Joe, > > rrc08 is still unreachable. Did you have chance to power > on? > > Regards. > Arife From arife at ripe.net Fri Sep 3 10:08:06 2004 From: arife at ripe.net (Arife Vural) Date: Fri, 3 Sep 2004 10:08:06 +0200 Subject: [ris-int] old RRC08 or new rrc14 Message-ID: <20040903080806.GN20397@ripe.net> Hi James, Bruce, Do you have any idea what might have happened rrc08? It looks it is not rebooted yesterday after Joe powered it off. Shall we ask Peter do a new installation on the box? Probably, he has to choose RRC08 config from installation menu and then change the IP address and gateway afterwards. I hope he could get root login with that installation CD. Arife From arife at ripe.net Fri Sep 3 10:22:20 2004 From: arife at ripe.net (Arife Vural) Date: Fri, 3 Sep 2004 10:22:20 +0200 Subject: [ris-int] Re: [sed] let bug in bash and data collection In-Reply-To: <41372017.8050007@ripe.net> References: <20040902091631.GG20397@ripe.net> <41372017.8050007@ripe.net> Message-ID: <20040903082220.GO20397@ripe.net> > Surely you mean if the value is "08": Yes, I noticed what I wrote after I sent the e-mail. > This isn't a bug, it's a feature! For details, use "man strtol" and see > the description for the special base value 0... I used expr, instead of let. That makes integer arithmetic automatically. Arife From arife at ripe.net Fri Sep 3 11:17:27 2004 From: arife at ripe.net (Arife Vural) Date: Fri, 03 Sep 2004 11:17:27 +0200 Subject: [ris-int] Time Out Message-ID: <200409030917.i839HRDI001012@birch.ripe.net> <<>> <<>> <<>> Dear Colleagues, Please note the following time out: Who: Arife Vural First Day: 04.10.2004 Starts at: 09:00 Last Day: 05.10.2004 Ends at: 17:00 Working days: [2.00] Type: CLV Reason: [optional for vacation] If you have any further questions, please do not hesitate to contact me. Thank you, Arife Vural From arife at ripe.net Fri Sep 3 11:19:30 2004 From: arife at ripe.net (Arife Vural) Date: Fri, 03 Sep 2004 11:19:30 +0200 Subject: [ris-int] Time Out Message-ID: <200409030919.i839JUDI001319@birch.ripe.net> <<>> <<>> <<>> Dear Colleagues, Please note the following time out: Who: Arife Vural First Day: 06.10.2004 Starts at: 09:00 Last Day: 19.10.2004 Ends at: 17:00 Working days: [10.00] Type: MED Reason: [optional for vacation] If you have any further questions, please do not hesitate to contact me. Thank you, Arife Vural From arife at ripe.net Fri Sep 3 11:20:35 2004 From: arife at ripe.net (Arife Vural) Date: Fri, 03 Sep 2004 11:20:35 +0200 Subject: [ris-int] Time Out Message-ID: <200409030920.i839KZDI001538@birch.ripe.net> <<>> <<>> <<>> Dear Colleagues, Please note the following time out: Who: Arife Vural First Day: 20.10.2004 Starts at: 09:00 Last Day: 02.11.2004 Ends at: 17:00 Working days: [10.00] Type: VAC Reason: [Turkey] If you have any further questions, please do not hesitate to contact me. Thank you, Arife Vural From Peter_Losher at isc.org Fri Sep 3 11:23:19 2004 From: Peter_Losher at isc.org (Peter Losher) Date: Fri, 3 Sep 2004 02:23:19 -0700 Subject: [ris-int] Re: RIS box @ MAE-West In-Reply-To: <200409021320.35725.Peter_Losher@isc.org> References: <20040831091651.GB29813@ripe.net> <20040902155036.GL20397@ripe.net> <200409021320.35725.Peter_Losher@isc.org> Message-ID: <200409030223.25660.Peter_Losher@isc.org> On Thursday 02 September 2004 01:20 pm, Peter Losher wrote: > On Thursday 02 September 2004 08:50 am, Arife Vural wrote: > > We are planning to unplug it tomorrow. 3rd of Sep, at 9.00 > > Pacific. If you have not move out from the rack, could you > > power on it and shutdown tomorrow? > > Can I pick up the system at around noon tomorrow (Friday)? Does this work for you Joe? (I'd like to confirm before heading down) -Peter -- Peter_Losher at isc.org | ISC | OpenPGP Key E8048D08 | "The bits must flow" -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: signature URL: From arife at ripe.net Fri Sep 3 11:29:12 2004 From: arife at ripe.net (Arife Vural) Date: Fri, 3 Sep 2004 11:29:12 +0200 Subject: [ris-int] Re: RIS box @ MAE-West In-Reply-To: <200409030223.25660.Peter_Losher@isc.org> References: <20040831091651.GB29813@ripe.net> <20040902155036.GL20397@ripe.net> <200409021320.35725.Peter_Losher@isc.org> <200409030223.25660.Peter_Losher@isc.org> Message-ID: <20040903092912.GR20397@ripe.net> Peter, > Does this work for you Joe? (I'd like to confirm before heading down) > Could you also pick up the installation CD from Joe? Thanks, Arife From arife at ripe.net Fri Sep 3 11:42:02 2004 From: arife at ripe.net (Arife Vural) Date: Fri, 3 Sep 2004 11:42:02 +0200 Subject: [ris-int] Agenda Points of RIS meeting on Mon Message-ID: <20040903094202.GS20397@ripe.net> - abcoude's decommission - RIS presentation @ R49 - status of RRC08/RRC14 and RRC13 - documentation issue, Ruud's e-mail about last bits of RIS transition. - rsync schema update - RIS CGI update If you have any additional agenda point, please let me know. Arife From Peter_Losher at isc.org Fri Sep 3 11:47:10 2004 From: Peter_Losher at isc.org (Peter Losher) Date: Fri, 3 Sep 2004 02:47:10 -0700 Subject: [ris-int] Re: RIS box @ MAE-West In-Reply-To: <20040903092912.GR20397@ripe.net> References: <20040831091651.GB29813@ripe.net> <200409030223.25660.Peter_Losher@isc.org> <20040903092912.GR20397@ripe.net> Message-ID: <200409030247.10880.Peter_Losher@isc.org> On Friday 03 September 2004 02:29 am, Arife Vural wrote: > Could you also pick up the installation CD from Joe? Sure. -- Peter_Losher at isc.org | ISC | OpenPGP Key E8048D08 | "The bits must flow" -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: signature URL: From henk at ripe.net Fri Sep 3 22:59:02 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Fri, 3 Sep 2004 22:59:02 +0200 (CEST) Subject: [ris-int] Agenda Points of RIS meeting on Mon In-Reply-To: <20040903094202.GS20397@ripe.net> References: <20040903094202.GS20397@ripe.net> Message-ID: On Fri, 3 Sep 2004, Arife Vural wrote: > > - abcoude's decommission > - RIS presentation @ R49 > - status of RRC08/RRC14 and RRC13 > - documentation issue, Ruud's e-mail about > last bits of RIS transition. > - rsync schema update > - RIS CGI update > > If you have any additional agenda point, please let me know. Beacon prefixes, hot from SIGCOMM. H. > > Arife > ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From matthew at ripe.net Sun Sep 5 22:16:02 2004 From: matthew at ripe.net (Matthew Williams) Date: Sun, 5 Sep 2004 16:16:02 -0400 Subject: [ris-int] Agenda Points of RIS meeting on Mon In-Reply-To: <20040903094202.GS20397@ripe.net> Message-ID: <002901c49385$302a2ba0$1101f242@rockstar> > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Arife Vural > Sent: 03 September 2004 05:42 > To: ris-int at ripe.net > Subject: [ris-int] Agenda Points of RIS meeting on Mon > > > > - abcoude's decommission > - RIS presentation @ R49 - Includes item: SED RIS Support reps at demo? > - status of RRC08/RRC14 and RRC13 > - documentation issue, Ruud's e-mail about > last bits of RIS transition. > - rsync schema update > - RIS CGI update > > If you have any additional agenda point, please let me know. > > Arife > From arife at ripe.net Mon Sep 6 12:26:06 2004 From: arife at ripe.net (Arife Vural) Date: Mon, 6 Sep 2004 12:26:06 +0200 Subject: [ris-int] Minutes of RIS meeting Message-ID: <20040906102606.GD11145@ripe.net> Any comment is nothing more than welcome. Arife -- Bi-weekly RIS meeting - 6 Sep, 2004 10.00am. Attendees: Arife, Shane, Henk, Bruce, James, Gerard. - abcoude decommission abcoude will continue to run until it will be replaced by new hardware. Ordering new hardware will be done around Nov. - RIS presentation @R49 Matthew will give an update @R49. Shane, Henk, Ruud and Matthew will get together to discuss details next week. Most probably Tuesday. Ziya will help Matthew during the demo at R49. - Status of RRC14 and RRC13 RRC14 is installed, but it's not network reachable. Arife is in contact with Peter Losher to put online this week. RRC13, Bruce waits IP config from Elena. When he gets those info, he will burn the CD and deliver CD to Elena during the RIPE meeting. - Documentation Kevin did some work on SED side to move RIS documents from NP pages. Arife will look at and bit tidy up the pages. James and Bruce will prepare the OPS part of doc, and both would be ready on Wed. There would be cross link from both pages to each other. - rsync schema It's finished. How to update files on RRCs will be documented by OPS. - RIS CGI Arife and Ziya built up the frame work to build up RIS CGI by using Mason and Perl. Arife started to coding from ASinuse. After ASinuse is finished, probably today. Tomorrow, Ziya and Arife will create the package and will do the server installation and WEB interface modules on halfweg. After that point, the rest of the CGI's will be built up by using the same structure. - Beacons Henk had some talk with Olaf Maneal and Zhuoqing Morley Mao during SIGCOM. They asked to continue to announce Beacon Prefixes as we do now and announce additional Anchor prefixes per RRCs. To do this, we would need more Prefix. Henk will send an e-mail around what he discussed during SIGCOM and SED will take it from there. - AOB Gerard brought up the issue which users should stay on RIS servers. NP people would keep their users on RIS servers, but they will not have root access. From matthew at ripe.net Mon Sep 6 20:20:33 2004 From: matthew at ripe.net (Matthew Williams) Date: Mon, 6 Sep 2004 14:20:33 -0400 Subject: [ris-int] Minutes of RIS meeting In-Reply-To: <20040906102606.GD11145@ripe.net> Message-ID: <000401c4943e$39ec57d0$3701f242@rockstar> > RRC13, Bruce waits IP config from Elena. When he gets those info, > he will burn the CD and deliver CD to Elena during the RIPE meeting. The last I heard from Elena was that she wouldn't be present at R49. Did someone else hear different? Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Arife Vural > Sent: 06 September 2004 06:26 > To: ris-int at ripe.net; sed at ripe.net; ops at ripe.net > Subject: [ris-int] Minutes of RIS meeting > > > > Any comment is nothing more than welcome. > > Arife > > -- > Bi-weekly RIS meeting - 6 Sep, 2004 10.00am. > > Attendees: Arife, Shane, Henk, Bruce, James, Gerard. > > - abcoude decommission > > abcoude will continue to run until it will be replaced by new > hardware. Ordering new hardware will be done around Nov. > > - RIS presentation @R49 > > Matthew will give an update @R49. Shane, Henk, Ruud and Matthew > will get together to discuss details next week. Most probably > Tuesday. > > Ziya will help Matthew during the demo at R49. > > - Status of RRC14 and RRC13 > > RRC14 is installed, but it's not network reachable. Arife is in > contact with Peter Losher to put online this week. > > RRC13, Bruce waits IP config from Elena. When he gets those info, > he will burn the CD and deliver CD to Elena during the RIPE meeting. > > - Documentation > > Kevin did some work on SED side to move RIS documents from NP pages. > Arife will look at and bit tidy up the pages. > > James and Bruce will prepare the OPS part of doc, and both would be > ready on Wed. There would be cross link from both pages to each other. > > - rsync schema > > It's finished. How to update files on RRCs will be documented by OPS. > > - RIS CGI > > Arife and Ziya built up the frame work to build up RIS CGI by > using Mason and Perl. Arife started to coding from ASinuse. After > ASinuse is finished, probably today. Tomorrow, Ziya and Arife > will create the package and will do the server installation and > WEB interface modules on halfweg. After that point, the rest of > the CGI's will be built up by using the same structure. > > - Beacons > > Henk had some talk with Olaf Maneal and Zhuoqing Morley Mao > during SIGCOM. They asked to continue to announce Beacon > Prefixes as we do now and announce additional Anchor prefixes > per RRCs. To do this, we would need more Prefix. Henk will > send an e-mail around what he discussed during SIGCOM and > SED will take it from there. > > - AOB > > Gerard brought up the issue which users should stay on RIS > servers. NP people would keep their users on RIS servers, but > they will not have root access. > From arife at ripe.net Tue Sep 7 11:01:56 2004 From: arife at ripe.net (Arife Vural) Date: Tue, 7 Sep 2004 11:01:56 +0200 Subject: [ris-int] Minutes of RIS meeting In-Reply-To: <000401c4943e$39ec57d0$3701f242@rockstar> References: <20040906102606.GD11145@ripe.net> <000401c4943e$39ec57d0$3701f242@rockstar> Message-ID: <20040907090156.GB3404@ripe.net> > > RRC13, Bruce waits IP config from Elena. When he gets those info, > > he will burn the CD and deliver CD to Elena during the RIPE meeting. > > The last I heard from Elena was that she wouldn't be present at R49. Did someone else hear different? I did not hear anything about that. Maybe a colleage of her would attend the meeting. If nobody will show up, we can send the CD by DHL. Arife > > Cheers, > Matthew > > > -----Original Message----- > > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > > On Behalf Of Arife Vural > > Sent: 06 September 2004 06:26 > > To: ris-int at ripe.net; sed at ripe.net; ops at ripe.net > > Subject: [ris-int] Minutes of RIS meeting > > > > > > > > Any comment is nothing more than welcome. > > > > Arife > > > > -- > > Bi-weekly RIS meeting - 6 Sep, 2004 10.00am. > > > > Attendees: Arife, Shane, Henk, Bruce, James, Gerard. > > > > - abcoude decommission > > > > abcoude will continue to run until it will be replaced by new > > hardware. Ordering new hardware will be done around Nov. > > > > - RIS presentation @R49 > > > > Matthew will give an update @R49. Shane, Henk, Ruud and Matthew > > will get together to discuss details next week. Most probably > > Tuesday. > > > > Ziya will help Matthew during the demo at R49. > > > > - Status of RRC14 and RRC13 > > > > RRC14 is installed, but it's not network reachable. Arife is in > > contact with Peter Losher to put online this week. > > > > RRC13, Bruce waits IP config from Elena. When he gets those info, > > he will burn the CD and deliver CD to Elena during the RIPE meeting. > > > > - Documentation > > > > Kevin did some work on SED side to move RIS documents from NP pages. > > Arife will look at and bit tidy up the pages. > > > > James and Bruce will prepare the OPS part of doc, and both would be > > ready on Wed. There would be cross link from both pages to each other. > > > > - rsync schema > > > > It's finished. How to update files on RRCs will be documented by OPS. > > > > - RIS CGI > > > > Arife and Ziya built up the frame work to build up RIS CGI by > > using Mason and Perl. Arife started to coding from ASinuse. After > > ASinuse is finished, probably today. Tomorrow, Ziya and Arife > > will create the package and will do the server installation and > > WEB interface modules on halfweg. After that point, the rest of > > the CGI's will be built up by using the same structure. > > > > - Beacons > > > > Henk had some talk with Olaf Maneal and Zhuoqing Morley Mao > > during SIGCOM. They asked to continue to announce Beacon > > Prefixes as we do now and announce additional Anchor prefixes > > per RRCs. To do this, we would need more Prefix. Henk will > > send an e-mail around what he discussed during SIGCOM and > > SED will take it from there. > > > > - AOB > > > > Gerard brought up the issue which users should stay on RIS > > servers. NP people would keep their users on RIS servers, but > > they will not have root access. > > From matthew at ripe.net Wed Sep 8 21:04:38 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 8 Sep 2004 15:04:38 -0400 Subject: [ris-int] Minutes of RIS meeting In-Reply-To: <20040907090156.GB3404@ripe.net> Message-ID: <000401c495d6$fe95b2e0$bf01f242@rockstar> > I did not hear anything about that. Maybe a colleage of her > would attend the meeting. If nobody will show up, we can send > the CD by DHL. > Did you check the attendee list for ripn or msk-ix? Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Arife Vural > Sent: 07 September 2004 05:02 > To: Matthew Williams > Cc: ris-int at ripe.net > Subject: Re: [ris-int] Minutes of RIS meeting > > > > > > RRC13, Bruce waits IP config from Elena. When he gets those info, > > > he will burn the CD and deliver CD to Elena during the > RIPE meeting. > > > > The last I heard from Elena was that she wouldn't be > present at R49. > > Did someone else hear different? > > I did not hear anything about that. Maybe a colleage of her > would attend the meeting. If nobody will show up, we can send > the CD by DHL. > > Arife > > > > > Cheers, > > Matthew > > > > > -----Original Message----- > > > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > > > On Behalf Of Arife Vural > > > Sent: 06 September 2004 06:26 > > > To: ris-int at ripe.net; sed at ripe.net; ops at ripe.net > > > Subject: [ris-int] Minutes of RIS meeting > > > > > > > > > > > > Any comment is nothing more than welcome. > > > > > > Arife > > > > > > -- > > > Bi-weekly RIS meeting - 6 Sep, 2004 10.00am. > > > > > > Attendees: Arife, Shane, Henk, Bruce, James, Gerard. > > > > > > - abcoude decommission > > > > > > abcoude will continue to run until it will be replaced by new > > > hardware. Ordering new hardware will be done around Nov. > > > > > > - RIS presentation @R49 > > > > > > Matthew will give an update @R49. Shane, Henk, Ruud and Matthew > > > will get together to discuss details next week. Most probably > > > Tuesday. > > > > > > Ziya will help Matthew during the demo at R49. > > > > > > - Status of RRC14 and RRC13 > > > > > > RRC14 is installed, but it's not network reachable. Arife is in > > > contact with Peter Losher to put online this week. > > > > > > RRC13, Bruce waits IP config from Elena. When he gets those info, > > > he will burn the CD and deliver CD to Elena during the > RIPE meeting. > > > > > > - Documentation > > > > > > Kevin did some work on SED side to move RIS documents > from NP pages. > > > Arife will look at and bit tidy up the pages. > > > > > > James and Bruce will prepare the OPS part of doc, and > both would be > > > ready on Wed. There would be cross link from both pages > to each other. > > > > > > - rsync schema > > > > > > It's finished. How to update files on RRCs will be documented by > > > OPS. > > > > > > - RIS CGI > > > > > > Arife and Ziya built up the frame work to build up RIS CGI by > > > using Mason and Perl. Arife started to coding from ASinuse. After > > > ASinuse is finished, probably today. Tomorrow, Ziya and Arife > > > will create the package and will do the server installation and > > > WEB interface modules on halfweg. After that point, the rest of > > > the CGI's will be built up by using the same structure. > > > > > > - Beacons > > > > > > Henk had some talk with Olaf Maneal and Zhuoqing Morley Mao > > > during SIGCOM. They asked to continue to announce Beacon > > > Prefixes as we do now and announce additional Anchor prefixes > > > per RRCs. To do this, we would need more Prefix. Henk will > > > send an e-mail around what he discussed during SIGCOM and > > > SED will take it from there. > > > > > > - AOB > > > > > > Gerard brought up the issue which users should stay on RIS > > > servers. NP people would keep their users on RIS servers, but > > > they will not have root access. > > > > From arife at ripe.net Thu Sep 9 12:01:17 2004 From: arife at ripe.net (Arife Vural) Date: Thu, 9 Sep 2004 12:01:17 +0200 Subject: [ris-int] Minutes of RIS meeting In-Reply-To: <000401c495d6$fe95b2e0$bf01f242@rockstar> References: <20040907090156.GB3404@ripe.net> <000401c495d6$fe95b2e0$bf01f242@rockstar> Message-ID: <20040909100116.GG19286@ripe.net> > > I did not hear anything about that. Maybe a colleage of her > > would attend the meeting. If nobody will show up, we can send > > the CD by DHL. > > > > Did you check the attendee list for ripn or msk-ix? No. Actually, CD should have been delivered yesterday to Andre's friend. James, Bruce, did we do it? Arife From arife at ripe.net Thu Sep 9 13:25:19 2004 From: arife at ripe.net (Arife Vural) Date: Thu, 09 Sep 2004 13:25:19 +0200 Subject: [ris-int] Time Out Message-ID: <200409091125.i89BPJDI013283@birch.ripe.net> <<>> <<>> <<>> Dear Colleagues, Please note the following time out: Who: Arife Vural First Day: 10.09.2004 Starts at: 09:00 Last Day: 10.09.2004 Ends at: 17:00 Working days: [1.00] Type: VAC Reason: [optional for vacation] If you have any further questions, please do not hesitate to contact me. Thank you, Arife Vural From arife at ripe.net Thu Sep 9 17:53:04 2004 From: arife at ripe.net (Arife Vural) Date: Thu, 9 Sep 2004 17:53:04 +0200 Subject: [ris-int] RIS docs - I Message-ID: <20040909155304.GH19286@ripe.net> Hi guys, I carried RIS internal pages to new space under SED structure. URL, http://iii.ripe.net/sed/twiki/bin/view/Doc/RIS With Twiki it looks quite fancy :-) I have not removed them from NP iii pages. If you think new pages looks OK, I will update NP page, clean up RIS stuff from there. If you like to update RIS iii pages, you can create an account yourself by using the following link and update them. http://iii.ripe.net/sed/twiki/bin/view/TWiki/TWikiRegistration I know, Matthew needs that to put WEB Access report online. Also from now on I will put RIS minutes in here. Arife From arife at ripe.net Thu Sep 9 17:54:58 2004 From: arife at ripe.net (Arife Vural) Date: Thu, 9 Sep 2004 17:54:58 +0200 Subject: [ris-int] RIS doc - II Message-ID: <20040909155457.GI19286@ripe.net> Hi James, Bruce, If you could send me the link for OPS documentation for RIS, I can create a link from RIS iii pages to point OPS doc. Arife From arife at ripe.net Thu Sep 9 18:05:25 2004 From: arife at ripe.net (Arife Vural) Date: Thu, 9 Sep 2004 18:05:25 +0200 Subject: [ris-int] being a member of ris-int mailling list Message-ID: <20040909160525.GJ19286@ripe.net> Hi guys, ris-int list is to discuss RIS related stuff internally and keep the coordination between groups. From OPS, James is already there. What do you think if I add you (Bruce, Gerard, Ruud) to the list as well? This way, I would know RIS related stuff will go to right persons at OPS, and not worry each time to whom I have to CC the e-mails or so. Arife From wilhelm at ripe.net Thu Sep 9 18:36:36 2004 From: wilhelm at ripe.net (Rene Wilhelm) Date: Thu, 09 Sep 2004 18:36:36 +0200 Subject: [ris-int] URGENT: need root access on halfweg Message-ID: <200409091636.i89GaaDI026112@birch.ripe.net> Hi Ops, I need root access on halfweg, as RISwhois seems to have problems and until it's been transferred to SED (meaning there's someone there who understands the code and can debug, fix things), curing problems falls upon me. wilhelm at halfweg:~$ sudo -s Password: wilhelm is not allowed to run sudo on halfweg. This incident will be reported. wilhelm at halfweg:~$ whois -h halfweg 193.0.0.0 % 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 % No entries found and yes, access statistics have shown RISwhois *is* used by the Internet community. It's not only a TTM/traceroute thingy. -- Rene From ziya at ripe.net Fri Sep 10 08:53:42 2004 From: ziya at ripe.net (Ziya Suzen) Date: Fri, 10 Sep 2004 08:53:42 +0200 Subject: [ris-int] RIS doc - II In-Reply-To: <20040909155457.GI19286@ripe.net> References: <20040909155457.GI19286@ripe.net> Message-ID: <20040910065341.GK14154@x33.ripe.net> On 2004-09-09 17:54:58 +0000, Arife Vural wrote: > > Hi James, Bruce, > > If you could send me the link for OPS documentation for RIS, > I can create a link from RIS iii pages to point OPS doc. Why not maintain it all under twiki? -- Ziya > > Arife From emil at ripe.net Fri Sep 10 09:43:19 2004 From: emil at ripe.net (Emil Gorter) Date: Fri, 10 Sep 2004 09:43:19 +0200 Subject: [ris-int] Re: [ripe.net #103695] URGENT: need root access on halfweg In-Reply-To: Message from Rene Wilhelm of "Thu, 09 Sep 2004 18:36:36 +0200." <200409091636.i89GaaDI026112@birch.ripe.net> Message-ID: <200409100743.i8A7hJDI018140@birch.ripe.net> Hi Rene, unfortunately your request arrived after normal 448-hotseat hours.. You could have called 24-7 for this. On Thu, 09 Sep 2004 18:36:36 +0200, Rene Wilhelm wrote: > > > Hi Ops, > > I need root access on halfweg, as RISwhois seems to have problems > and until it's been transferred to SED (meaning there's someone > there who understands the code and can debug, fix things), curing > problems falls upon me. > > wilhelm at halfweg:~$ sudo -s > Password: > wilhelm is not allowed to run sudo on halfweg. This incident will be reporte > d. > wilhelm at halfweg:~$ Indeed, sudo on RIS hosts was restricted to running /etc/rc.d/rc.apache by group sudo-sed. I have given people in group sudo-np full sudo on RIS Linux hosts weesp, diemen and halfweg. I think this needs to be removed after the problems are fixed, so I will keep the ticket open till then. > whois -h halfweg 193.0.0.0 > % 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 > > % No entries found > > > and yes, access statistics have shown RISwhois *is* used > by the Internet community. It's not only a TTM/traceroute > thingy. ?? E m i l . > -- Rene > From wilhelm at ripe.net Fri Sep 10 14:20:59 2004 From: wilhelm at ripe.net (Rene Wilhelm) Date: Fri, 10 Sep 2004 14:20:59 +0200 Subject: [ris-int] xrtt failing on me ... Message-ID: <200409101220.i8ACKxDI030147@birch.ripe.net> I tried to use xrtt to answer Ulrich Schmid on his question re: riswhois, but this ticketing system fails on me (it did work before). As I don't have time now to fix both riswhois and dive into the mysterious ways of xrtt, I've replied to Ulrich directly. -- Rene cow$ xrtt Ambiguous call resolved as CORE::system(), qualify as such or use & at /usr/local/ncc/bin/xrtt line 5589. /home/wilhelm/.xrttrc: No such file or directory DBI connect('mysql_read_default_group=rtt','',...) failed: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) at /usr/local/ncc/lib/perl5/5.8.0/rttCommon.pm line 314 Could not connect to mysqldb: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) Could not connect to mysqldb: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) at /usr/local/ncc/lib/perl5/5.8.0/rttCommon.pm line 908. From wilhelm at ripe.net Fri Sep 10 16:04:41 2004 From: wilhelm at ripe.net (Rene Wilhelm) Date: Fri, 10 Sep 2004 16:04:41 +0200 Subject: [ris-int] Re: [ripe.net #103695] URGENT: need root access on halfweg In-Reply-To: Message from Emil Gorter of "Fri, 10 Sep 2004 09:43:19 +0200." <200409100743.i8A7hJDI018140@birch.ripe.net> Message-ID: <200409101404.i8AE4fDI002626@birch.ripe.net> Hi Emil, Ris-int, The problem with riswhois is fixed. It turned out the advance creation of (currently empty) directories for october, november and december 2004 RIS BGP dumps triggered a bug in my code. Updated source is in (NP) CVS and halfweg:/home/risops/src/RISwhois. > I have given people in group sudo-np full sudo on RIS Linux hosts > weesp, diemen and halfweg. I think this needs to be removed after > the problems are fixed, so I will keep the ticket open till then. I would appreciate if my root privilige on halfweg could stay for somewhat longer; at least until RISwhois has been transferred and SED are comfortable with the code. (post RIPE49 - october 2004?) You can trust me to not misuse the root priviliges, I won't sudo unless there's a problem that needs my attention and will of course not touch anything I'm not responsible for. -- Rene From henk at ripe.net Mon Sep 13 09:41:55 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Mon, 13 Sep 2004 09:41:55 +0200 (CEST) Subject: [ris-int] Re: [ripe.net #103695] URGENT: need root access on halfweg In-Reply-To: <200409101404.i8AE4fDI002626@birch.ripe.net> References: <200409101404.i8AE4fDI002626@birch.ripe.net> Message-ID: On Fri, 10 Sep 2004, Rene Wilhelm wrote: > Hi Emil, Ris-int, > > The problem with riswhois is fixed. It turned out the advance creation > of (currently empty) directories for october, november and december > 2004 RIS BGP dumps triggered a bug in my code. Updated source is > in (NP) CVS and halfweg:/home/risops/src/RISwhois. > > > I have given people in group sudo-np full sudo on RIS Linux hosts > > weesp, diemen and halfweg. I think this needs to be removed after > > the problems are fixed, so I will keep the ticket open till then. > > I would appreciate if my root privilige on halfweg could stay > for somewhat longer; at least until RISwhois has been transferred > and SED are comfortable with the code. (post RIPE49 - october 2004?) I think that would be a good idea. Henk > > You can trust me to not misuse the root priviliges, I won't sudo > unless there's a problem that needs my attention and will of > course not touch anything I'm not responsible for. > > -- Rene > ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ In a room with a window in the corner, I found truth. (Ian Curtis) From arife at ripe.net Mon Sep 13 10:04:51 2004 From: arife at ripe.net (Arife Vural) Date: Mon, 13 Sep 2004 10:04:51 +0200 Subject: [ris-int] Re: [ripe.net #103695] URGENT: need root access on halfweg In-Reply-To: <200409100743.i8A7hJDI018140@birch.ripe.net> References: <200409091636.i89GaaDI026112@birch.ripe.net> <200409100743.i8A7hJDI018140@birch.ripe.net> Message-ID: <20040913080451.GA14843@ripe.net> Emil, I can not make sudo on halfweg. Could you allow me and other SED guy to do sudo on halfweg and other RIS servers (weesp, abcoude, diemen)? Thanks, Arife From emil at ripe.net Mon Sep 13 10:25:07 2004 From: emil at ripe.net (Emil Gorter) Date: Mon, 13 Sep 2004 10:25:07 +0200 Subject: [ris-int] Re: [ripe.net #103695] URGENT: need root access on halfweg In-Reply-To: Message from Arife Vural of "Mon, 13 Sep 2004 10:04:51 +0200." <20040913080451.GA14843@ripe.net> Message-ID: <200409130825.i8D8P7DI002856@birch.ripe.net> Hi Arife, On Mon, 13 Sep 2004 10:04:51 +0200, Arife Vural wrote: > > > Emil, > > I can not make sudo on halfweg. Could you allow me and other SED guy > to do sudo on halfweg and other RIS servers (weesp, abcoude, diemen)? sudo-np and sudo-sed members can do everything on RIS hosts now. This MUST get reverted asap. Good luck with fixing the bugs! E m i l . From arife at ripe.net Mon Sep 13 10:33:58 2004 From: arife at ripe.net (Arife Vural) Date: Mon, 13 Sep 2004 10:33:58 +0200 Subject: [ris-int] Re: [ripe.net #103695] URGENT: need root access on halfweg In-Reply-To: <200409130825.i8D8P7DI002856@birch.ripe.net> References: <20040913080451.GA14843@ripe.net> <200409130825.i8D8P7DI002856@birch.ripe.net> Message-ID: <20040913083357.GD14843@ripe.net> > > sudo-np and sudo-sed members can do everything on RIS hosts now. > This MUST get reverted asap. For SED, it would be permenant. For NP, I try to arrange time with Rene to take over RISwhois code. Arife > > Good luck with fixing the bugs! > > E m i l . From emil at ripe.net Mon Sep 13 10:45:27 2004 From: emil at ripe.net (Emil Gorter) Date: Mon, 13 Sep 2004 10:45:27 +0200 Subject: [ris-int] Re: [ripe.net #103695] URGENT: need root access on halfweg In-Reply-To: Message from Arife Vural of "Mon, 13 Sep 2004 10:33:58 +0200." <20040913083357.GD14843@ripe.net> Message-ID: <200409130845.i8D8jRDI011071@birch.ripe.net> Hi, > > sudo-np and sudo-sed members can do everything on RIS hosts now. > > This MUST get reverted asap. > > For SED, it would be permenant. that's not up to me or you alone to decide, I'm afraid. So for now I assume things will have to be reverted to the way they were. If you / SED or NP need sudo permanently I need to discuss it at OPS. But that's a discussion we can have after the RIS troubles are gone. Cheers, E m i l . From arife at ripe.net Mon Sep 13 10:51:15 2004 From: arife at ripe.net (Arife Vural) Date: Mon, 13 Sep 2004 10:51:15 +0200 Subject: [ris-int] Re: [ripe.net #103695] URGENT: need root access on halfweg In-Reply-To: <200409130845.i8D8jRDI011071@birch.ripe.net> References: <20040913083357.GD14843@ripe.net> <200409130845.i8D8jRDI011071@birch.ripe.net> Message-ID: <20040913085114.GF14843@ripe.net> > > For SED, it would be permenant. > > that's not up to me or you alone to decide, I'm afraid. > So for now I assume things will have to be reverted to the way they > were. If you / SED or NP need sudo permanently I need to discuss it > at OPS. We discussed this issue at the last RIS meeting with Gerard and we agreed to keep sudo for SED, not NP. Could you please check it out with Gerard? Arife From matthew at ripe.net Mon Sep 13 11:32:31 2004 From: matthew at ripe.net (Matthew Williams) Date: Mon, 13 Sep 2004 11:32:31 +0200 Subject: [ris-int] IPv6 queries Message-ID: <000401c49974$97d018b0$300200c1@rockstar> Hi James, What more IPv6 stuff is is there besides http://www.ris.ripe.net/ipv6-updates/ and http://www.ris.ripe.net/cgi-bin/ipv6/prefixquery.cgi? Please send me the URLs for the RIS update talk. Many thanks :) Cheers, Matthew From arife at ripe.net Mon Sep 13 16:05:05 2004 From: arife at ripe.net (Arife Vural) Date: Mon, 13 Sep 2004 16:05:05 +0200 Subject: [ris-int] Time Out Message-ID: <200409131405.i8DE55DI005850@birch.ripe.net> <<>> <<>> <<>> Dear Colleagues, Please note the following time out: Who: Arife Vural First Day: 29.09.2004 Starts at: 09:00 Last Day: 01.10.2004 Ends at: 17:00 Working days: [3.00] Type: VAC Reason: [Turkey] If you have any further questions, please do not hesitate to contact me. Thank you, Arife Vural From matthew at ripe.net Mon Sep 13 19:06:42 2004 From: matthew at ripe.net (Matthew Williams) Date: Mon, 13 Sep 2004 19:06:42 +0200 Subject: [ris-int] RIS update slides v 0.3 Message-ID: <002501c499b4$0aec2e30$300200c1@rockstar> Cheers, Matthew -------------- next part -------------- A non-text attachment was scrubbed... Name: RIS_RIPE49_03.pdf Type: application/pdf Size: 357315 bytes Desc: not available URL: From support at ca-assist.net Tue Sep 14 17:11:04 2004 From: support at ca-assist.net (support at ca-assist.net) Date: Wed, 15 Sep 2004 0:11:4 +0900 Subject: [ris-int] =?ISO-2022-JP?B?GyRCTCQ+NUJ6OS05cCIoGyhC?= =?ISO-2022-JP?B?GyRCIXklRyE8JT8hPEZ+Tk8jMSMwIzAjMBsoQg==?= =?ISO-2022-JP?B?GyRCS3w3b08iQjNGfjJZGyhC?= ( =?ISO-2022-JP?B?GyRCIzIjMCMwTD5CZ0pnPTghKhsoQg==?=) =?ISO-2022-JP?B?GyRCIXkbKEI=?= Message-ID: <20040914152548.2A95251C23@postman.ripe.net> ????????????????????????? ------------------------------------------------------------ ? ????????? ????????????1-18-13-2F ------------------------------------------------------------ ???????????????????????????? ???????????????????????????????? ????????????????URL???????????? http://www.qmsys.net/r.php?id=1&sid=e0713439040eb96c9302271782e0d580 ??URL??????????????????????????? ??????????????????????????? teishi at qmsys.net ------------------------------------------------------------ ?????????????????(????????)? ???????????????????????????? ????????????????????? ?2004.09??? ???????????????????????????? ????????/????????????????1,921,762????? ?????????????????????????? ?????????????????????????? ? ? ???????????????? ? ????????????? ? ??????????????? ? ????????????????? ??????????????????http://www.ca-assist.net? ?????????????????? ????????????? ?????????????????? ??????????? ????????????????? ????????????????????????? ??????????????? ??????????????? ???????????????????? ??????????????????????????????????? ??????????????????????????????????? ??????????????????????????????????? ??????????????????????????????????? ??????????????????????????????????? ????? ???????????????????????????? ??????????????????????????????????? ??????????????????????????????????? ??????????????????????????????????? ??????????????????????????????????? ??????????????????????????????????? ??????????????????????????????????? ??????????????????????????????????? ??????????????????????????????????? ??????????????????????????????????? ??????????????????????????????????? ??????????????????????????????????? ??????????????????????????????????? ?????????????????????????????????? ????????????http://www.ca-assist.net?? ---------------------------------------------------------------------- ???????? ---------------------------------------------------------------------- ???????? ?? ?http://www.ca-assist.net????????? ?? ?????????????? ?? ???????????????????? ?? ??????????????????????????? ????????????????????????? ? - ???????????????? ----------------------------------- ?????????????????????????(?)??????? ??????????????????????????????????? ????????????? ???HTML?????????????????????????????? ??????????????????????????????????? ??????????????????????????????????? From matthew at ripe.net Tue Sep 14 19:51:50 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 14 Sep 2004 19:51:50 +0200 Subject: [ris-int] RE: IPv6 queries Message-ID: <000401c49a83$82f7aec0$1f0200c1@rockstar> Hi James, I know you're busy because of R49 preps, but I really do need an answer to below even though it's just "That's all!" ;) Cheers, Matthew > -----Original Message----- > From: Matthew Williams [mailto:matthew at ripe.net] > Sent: 13 September 2004 11:33 > To: 'James Aldridge' > Cc: 'ris-int at ripe.net' > Subject: IPv6 queries > > > Hi James, > > What more IPv6 stuff is is there besides > http://www.ris.ripe.net/ipv6-updates/ and http://www.ris.ripe.net/cgi-bin/ipv6/prefixquery.cgi? Please send me the URLs for the RIS update talk. Many thanks :) Cheers, Matthew From matthew at ripe.net Tue Sep 14 23:37:21 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 14 Sep 2004 23:37:21 +0200 Subject: [ris-int] RIS Update v. 0.4 Message-ID: <000501c49aa3$0a8a9ea0$aaa8a8c0@rockstar> With comments from meeting taken into consideration. Cheers, Matthew -------------- next part -------------- A non-text attachment was scrubbed... Name: RIS_RIPE49_04.pdf Type: application/pdf Size: 361953 bytes Desc: not available URL: From james at ripe.net Wed Sep 15 10:57:40 2004 From: james at ripe.net (James Aldridge) Date: Wed, 15 Sep 2004 10:57:40 +0200 Subject: [ris-int] Re: IPv6 queries In-Reply-To: Message from "Matthew Williams" of "Tue, 14 Sep 2004 19:51:50 +0200." <000401c49a83$82f7aec0$1f0200c1@rockstar> Message-ID: <200409150857.i8F8veDI029779@birch.ripe.net> "Matthew Williams" wrote: > Hi James, > > I know you're busy because of R49 preps, but I really do need an answer to below even though it's just "That's all!" ;) Sorry. "That's all!" ;-) James > > Cheers, > Matthew > > > -----Original Message----- > > From: Matthew Williams [mailto:matthew at ripe.net] > > Sent: 13 September 2004 11:33 > > To: 'James Aldridge' > > Cc: 'ris-int at ripe.net' > > Subject: IPv6 queries > > > > > > Hi James, > > > > What more IPv6 stuff is is there besides > > http://www.ris.ripe.net/ipv6-updates/ and > http://www.ris.ripe.net/cgi-bin/ipv6/prefixquery.cgi? > > Please send me the URLs for the RIS update talk. > > Many thanks :) > > Cheers, > Matthew > From matthew at ripe.net Wed Sep 15 12:03:38 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 15 Sep 2004 12:03:38 +0200 Subject: [ris-int] Re: IPv6 queries In-Reply-To: <200409150857.i8F8veDI029779@birch.ripe.net> Message-ID: <000901c49b0b$45a715a0$aaa8a8c0@rockstar> :) I thought so, just needed confirmation. Thanks for these contributions. Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of James Aldridge > Sent: 15 September 2004 10:58 > To: Matthew Williams > Cc: 'James Aldridge'; ris-int at ripe.net > Subject: [ris-int] Re: IPv6 queries > > > "Matthew Williams" wrote: > > Hi James, > > > > I know you're busy because of R49 preps, but I really do need an > > answer to below even though it's just "That's all!" ;) > > Sorry. > > "That's all!" ;-) > > James > > > > > > Cheers, > > Matthew > > > > > -----Original Message----- > > > From: Matthew Williams [mailto:matthew at ripe.net] > > > Sent: 13 September 2004 11:33 > > > To: 'James Aldridge' > > > Cc: 'ris-int at ripe.net' > > > Subject: IPv6 queries > > > > > > > > > Hi James, > > > > > > What more IPv6 stuff is is there besides > > > http://www.ris.ripe.net/ipv6-updates/ and > > http://www.ris.ripe.net/cgi-bin/ipv6/prefixquery.cgi? > > > > Please send me the URLs for the RIS update talk. > > > > Many thanks :) > > > > Cheers, > > Matthew > > > From arife at ripe.net Wed Sep 15 17:42:42 2004 From: arife at ripe.net (Arife Vural) Date: Wed, 15 Sep 2004 17:42:42 +0200 Subject: [ris-int] Re: RIS docs - I In-Reply-To: <20040909155304.GH19286@ripe.net> References: <20040909155304.GH19286@ripe.net> Message-ID: <20040915154242.GN16992@ripe.net> FYI: I updated NP iii pages. There is only one link left about RIS and that point new RIS pages @ SED. Arife On Thu, Sep 09, 2004 at 05:53:04PM +0200, Arife Vural wrote: > > Hi guys, > > I carried RIS internal pages to new space under SED structure. > > URL, http://iii.ripe.net/sed/twiki/bin/view/Doc/RIS > > With Twiki it looks quite fancy :-) > > I have not removed them from NP iii pages. If you think new pages > looks OK, I will update NP page, clean up RIS stuff from there. > > If you like to update RIS iii pages, you can create an account > yourself by using the following link and update them. > > http://iii.ripe.net/sed/twiki/bin/view/TWiki/TWikiRegistration > > I know, Matthew needs that to put WEB Access report online. Also > from now on I will put RIS minutes in here. > > Arife From matthew at ripe.net Thu Sep 16 14:25:12 2004 From: matthew at ripe.net (Matthew Williams) Date: Thu, 16 Sep 2004 14:25:12 +0200 Subject: [ris-int] Final version of RIS Update Message-ID: <001a01c49be8$36c16b20$1f0200c1@rockstar> /spool/matthew/ripe49/RIS_RIPE49_FINAL.[pdf|ppt] Cheers, Matthew Ps. More or less the same as v 0.4 From arife at ripe.net Mon Sep 20 14:29:49 2004 From: arife at ripe.net (Arife Vural) Date: Mon, 20 Sep 2004 14:29:49 +0200 Subject: [ris-int] RIS announces new Beacon Prefix 195.80.238.0/24. Message-ID: <20040920122949.GB9606@ripe.net> Dear All, We started to announce new Beacon Prefix 195.83.238.0/24 at LINX, SFINX, VIX, NSPIXP2, NYIIX behind AS12654. This Beacon prefix is requested from Hitesh Ballani to do research about Anycast servers behavior. Please adjust your filters to receive this additional prefix from RIS (AS12654) and pass it to your upstream provider. There is no real traffic towards this prefix. However, we configured a dummy interface on RRCs from this address range to allow Hitesh Ballani do also some measurement in addition to the reachability of Anycast servers. If you would have any questions, please do not hesitate to contact with us. Kind regards. Arife From arife at ripe.net Mon Sep 20 15:26:11 2004 From: arife at ripe.net (Arife Vural) Date: Mon, 20 Sep 2004 15:26:11 +0200 Subject: [ris-int] test Message-ID: <20040920132611.GF9606@ripe.net> From wilhelm at ripe.net Mon Sep 20 23:41:49 2004 From: wilhelm at ripe.net (Rene Wilhelm) Date: Mon, 20 Sep 2004 23:41:49 +0200 Subject: [ris-int] hitesh@ripe.net ? [was Re: RIS announces new Beacon Prefix 195.80.238.0/24.] In-Reply-To: Message from Arife Vural of "Mon, 20 Sep 2004 14:32:07 +0200." <20040920123207.GD9606@ripe.net> Message-ID: <200409202141.i8KLfnrL026139@birch.ripe.net> Hi Arife, > We started to announce new Beacon Prefix 195.83.238.0/24 at LINX, > SFINX, VIX, NSPIXP2, NYIIX behind AS12654. This Beacon prefix is > requested from Hitesh Ballani to do research about > Anycast servers behavior. vrfy -e hitesh at birch.ripe.net 5.1.1 hitesh at birch.ripe.net... User unknown hitesh at birch.ripe.net ... User unknown ????? -- Rene From arife at ripe.net Tue Sep 21 12:03:32 2004 From: arife at ripe.net (Arife Vural) Date: Tue, 21 Sep 2004 12:03:32 +0200 Subject: [ris-int] Re: RIS announces new Beacon Prefix 195.80.238.0/24. In-Reply-To: <20040920122949.GB9606@ripe.net> References: <20040920122949.GB9606@ripe.net> Message-ID: <20040921100332.GA28050@ripe.net> On Mon, Sep 20, 2004 at 02:29:49PM +0200, Arife Vural wrote: > > Dear All, > > We started to announce new Beacon Prefix 195.83.238.0/24 at LINX, > SFINX, VIX, NSPIXP2, NYIIX behind AS12654. This Beacon prefix is > requested from Hitesh Ballani to do research about > Anycast servers behavior. I typed Hitesh's e-mail address wrong in previous e-mail, sorry for that. His e-mail address is in case you like to contact with him. Arife > > Please adjust your filters to receive this additional prefix from > RIS (AS12654) and pass it to your upstream provider. There is no real > traffic towards this prefix. However, we configured a dummy interface > on RRCs from this address range to allow Hitesh Ballani do also some > measurement in addition to the reachability of Anycast servers. > > If you would have any questions, please do not hesitate to contact > with us. > > Kind regards. > > Arife From leave-info-letter at geldgeschenk24.de Tue Sep 21 12:06:21 2004 From: leave-info-letter at geldgeschenk24.de (Geldgeschenk24) Date: Tuesday, 21 Sep 2004 12:06:21 Subject: [ris-int] +++ Monatlich 50 EURO geschenkt +++ Message-ID: Sie erhalten diese E-Mail, weil Ihre Adresse eingegeben wurde. Wenn Sie Missbrauch vermuten, senden Sie bitte sofort eine Mail an mailto:leave-Info-letter at Geldgeschenk24.de. Sie wollen jeden Monat zus?tzlich 50 EURO? Informieren Sie sich noch heute: http://www.GeldGeschenk24.de From wilhelm at ripe.net Tue Sep 21 18:40:50 2004 From: wilhelm at ripe.net (Rene Wilhelm) Date: Tue, 21 Sep 2004 18:40:50 +0200 Subject: [ris-int] riswhois: did nagios report outdated info? Message-ID: <200409211640.i8LGeorL014857@birch.ripe.net> Hi Ops, This one might be for Gerard (as he did the nagios config for this): I noticed that riswhoisd (on halfweg) is no longer refreshing it's data: whois -h riswhois sources % 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 rrc00 20040915 1600Z rrc01 20040915 1600Z rrc03 20040915 1600Z rrc04 20040915 1600Z rrc05 20040915 1600Z rrc06 20040915 1600Z rrc07 20040915 1600Z rrc10 20040915 1600Z rrc11 20040915 1600Z rrc12 20040915 1600Z It's 6 days ago since riswhoisd last parsed the BGP dump data files. When this happened a few months ago, Gerard implemented rules in nagios that should check for outdated timestamps. Question: did nagios give you such a report in the last days ???? If not, please consider this a request to fix it. I will not restart riswhoisd until tomorrow this time, to give you a chance to test the nagios setup for the up-to-date check. ris-int: it's not clear why riswhoisd can't refresh; it used to work fine; probably it somehow cannot fork a new process that refreshes data while the main daemon continues listening. more debug code will have to be added to riswhois to be able to track this in future. For now the only remedy is a cold restart of the daemon. -- Rene From arife at ripe.net Wed Sep 22 12:12:12 2004 From: arife at ripe.net (Arife Vural) Date: Wed, 22 Sep 2004 12:12:12 +0200 Subject: [ris-int] riswhois: did nagios report outdated info? In-Reply-To: <200409211640.i8LGeorL014857@birch.ripe.net> References: <200409211640.i8LGeorL014857@birch.ripe.net> Message-ID: <20040922101212.GC15275@ripe.net> Hi Rene, > ris-int: it's not clear why riswhoisd can't refresh; it used to > work fine; probably it somehow cannot fork a new process that > refreshes data while the main daemon continues listening. > more debug code will have to be added to riswhois to be able > to track this in future. For now the only remedy is a cold > restart of the daemon. I did that, it looks it catched up the latest files. Arife From matthew at ripe.net Sun Sep 26 03:40:31 2004 From: matthew at ripe.net (Matthew Williams) Date: Sun, 26 Sep 2004 02:40:31 +0100 Subject: [ris-int] FW: myASN bug not resolved Message-ID: <00ac01c4a369$d13c73b0$07c989d4@rockstar> Hmm, I have adjusted the flag to N. Cheers, Matthew > -----Original Message----- > From: Marco d'Itri [mailto:md at Linux.IT] > Sent: 25 September 2004 13:37 > To: ris at ripe.net > Subject: myASN bug not resolved > > > Earlier this year I reported this bug, which is now flagged > as fixed: "Transit alarm wrongly flagging paths with only the > Origin AS as leaks". > > I can verify that the problem is still present, see the log > of my alarm 545: > http://www.ris.ripe.net/myasn/show_alarmevents.html?source=alarmlog;alarm_id=545;order=utc_last -- ciao, | Marco | [8188 apSa/cadRSna2] From arife at ripe.net Mon Sep 27 13:21:20 2004 From: arife at ripe.net (Arife Vural) Date: Mon, 27 Sep 2004 13:21:20 +0200 Subject: [ris-int] risops crontab e-mail on ris-request Message-ID: <20040927112119.GM28275@ripe.net> Hi Vasco, I'm sending one copy of risops e-mails to ris-request. There is not many. Those e-mails are important when something is broken. I did not have time to implement SED procedure to send crontab messages to different places. Arife From arife at ripe.net Mon Sep 27 14:34:20 2004 From: arife at ripe.net (Arife Vural) Date: Mon, 27 Sep 2004 14:34:20 +0200 Subject: [ris-int] Re: RIS box @ MAE-West In-Reply-To: <200408241719.52649.Peter_Losher@isc.org> References: <20040820130524.GA21467@ripe.net> <200408241719.52649.Peter_Losher@isc.org> Message-ID: <20040927123420.GO28275@ripe.net> Hi Paul, Peter, Everything is ready on RIS box, except the peering IP address. I'm just wondering whether any progress about getting peering IP address for RIS box. BTW, I will be away for vacation from this Wed. Vasco, a colleague of mine, will work on relocating RIS box at PAIX. Please, do not forget to CC him and ris-request at ripe.net when you reply this e-mail. Regards. Arife From arife at ripe.net Mon Sep 27 14:48:20 2004 From: arife at ripe.net (Arife Vural) Date: Mon, 27 Sep 2004 14:48:20 +0200 Subject: [ris-int] [ugin@ripn.net: Re: RIS & MCK-IX] Message-ID: <20040927124820.GP28275@ripe.net> Hi Bruce, James, I do not know where we are at RRC13. Installation CD or image should send to people in Moscow. Could you keep in touch with MCK-IX people about installation of RRC13? Arife ----- Forwarded message from Evgueni Kouskevitch ----- From: Evgueni Kouskevitch To: Bruce Campbell Subject: Re: RIS & MCK-IX Date: Tue, 7 Sep 2004 17:40:28 +0400 Cc: arife at ripe.net, NOC RELARN Hello! Now you can hand your installation CD to Andrei Robatchevski for Alexey Platonov who will be present at Amsterdam until Thursday, September 9. -- Evgueni G. Kouskevitch Russian Institute for RIPN NOC:+7(095)192-9179 Public Networks ----- End forwarded message ----- From ris-request at ripe.net Mon Sep 27 14:53:23 2004 From: ris-request at ripe.net (RIPE NCC RIS) Date: Mon, 27 Sep 2004 14:53:23 +0200 Subject: [ris-int] Fw: NCC#2004081420 [RE: RIPE beacon request!] Message-ID: <200409271253.i8RCrNih006991@x12.ripe.net> Hi James, Hitesh could ask some changes about announcing Beacon Prefix. Vasco might need help to do those changes. Could you please give him a hand to do those changes? BTW, I updated the following page. http://www.ripe.net/ripencc/pub-services/np/ris/beaconlist.html You can find the latest changes there. Thanks. Arife ----- Begin forwarded message ----- Date: Fri, 17 Sep 2004 02:11:17 -0400 From: "Hitesh Ballani" To: "RIPE NCC RIS" Subject: RE: NCC#2004081420 RIPE beacon request! Message-Id: <81224EA6DDA07C43BC7555E32401029E054260 at EXCHVS2.cs.cornell.edu> Hi Arife, > Sorry getting back to you late. That is all-right ... I can imagine you being very busy! > Please let me know which RRCs you > like to announce Beacon prefix and which pattern we will start-up. Lets start off with a prefix (I presume 195.80.238.0/24) being advertised as normal (i.e. no periodic withdrawals) from 6 locations : RRC01 (Lon,UK), RRC02 (Paris,UK), RRC05 (Vienna,AT), RRC06 (Otemcahi, JP), RRC08 (San Jose,US), RRC11(NY,USA). As I mentioned earlier, the purpose is to get baseline measurements for an anycasted prefix when there are no flaps (at least, no intentional flaps). Then, later we can introduce flaps for other experiments. Actually, what I would like to do is to have the prefix advertised in a stable fashion (i.e. no intentional withdrawals) from 7 RRC locations with the locations changing every couple of days .... i.e. of the 13 RRCs, 7 are always advertising the prefix but the set of seven changes every couple of days ...since, I would like the non-european sites (3 of them) to always be part of the advertising set, so we are left with choose(13 - 3, 7 -3) = choose(10,4) = 1260 combinations ... while this is not certainly not possible, I was wondering if we could try out 5-7 odd combinations so that the entire experiment finishes in a couple of weeks and then, we can move onto the experiments with periodic withdrawals ... however, I am not sure if this can be automated (I would be happy to write any scripts needed for this) because it would be a pain for you to do this manually .. if this is possible, then I would be more than happy to send you a chart of the 5-7 sets of 7 RRCs, each set advertising the prefix for 2 (or whatever u are comfortable with) days .. However, if this is not feasible, then we could start with the pattern mentioned in the previous paragraph and make 1 or 2 changes (2 weeks, one change a week gives us 2 combinations to try out). Comments?? By the way, are you going to set up interfaces on these machines so that I can also do end-to-end experiments? Thanks, Hitesh ------ End forwarded message ------ From henk at ripe.net Mon Sep 27 16:27:19 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Mon, 27 Sep 2004 16:27:19 +0200 (CEST) Subject: [ris-int] RIS Beacons In-Reply-To: <200409241353.i8ODriWn030333@x21.ripe.net> References: <200308181136.h7IBau3j005724@birch.ripe.net> <200409241353.i8ODriWn030333@x21.ripe.net> Message-ID: All, At SIGCOMM 2004, it became clear that the current beacon prefixes suffer from 2 problems: a) They have more peers giving transit than any other AS on the Internet. b) When a prefix is invisible, it is not clear if this is caused by an experimental problem or by the prefix being filtered. The anchor prefix does not solve this problem, there should be one anchor per beacon. So, people suggested that for the next period (1/10/2004-30/9/2005), we make the following changes: 1. A new /19 is requested from the RIPE NCC. This /19 is split into /24's. 2. Each RRC annouces 2 /24's. Assuming A.B.Z is the base address A.B.(Z+2*Y).0/24 A.B.(Z+2*Y+1).0/24 For Y=0 to 13 for the (up to 16) RRC's. The first prefix is announced permanently. The second one is a flapping prefix: up at 0 GMT, down at 2 GMT, up at 4 GMT etc. The pattern may be changed at a later stage. 3. Inside each /24, a pingable address will be established. 4. We ask only 2 or 3 peers at each IX to provide transit for these prefixes. (In other words, we do not ask everybody). 5. Other experiments that we do are: - An overflow prefix (prefix announced at 1 RRC, flapping at the next). - Hitesh's experiment. 6. The current 195.80.224.0/20 is returned to the RIPE NCC Comments? 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 ------------------------------------------------------------------------------ In a room with a window in the corner, I found truth. (Ian Curtis) From arife at ripe.net Mon Sep 27 17:21:46 2004 From: arife at ripe.net (Arife Vural) Date: Mon, 27 Sep 2004 17:21:46 +0200 Subject: [ris-int] Switching to new layout and RIS WEB pages Message-ID: <20040927152146.GR28275@ripe.net> Hi all, I'll be off for vacation from this Wed. Please, coordinate RIS part of switching to new layout with Ziya. Documentation how to do the switch on RIS site is available at http://iii/sed/twiki/bin/view/SED/MigrateRISWEBPagesToNewRIPENCCLayout Good luck. Arife From Peter_Losher at isc.org Mon Sep 27 18:23:21 2004 From: Peter_Losher at isc.org (Peter Losher) Date: Mon, 27 Sep 2004 09:23:21 -0700 Subject: [ris-int] Re: RIS box @ MAE-West In-Reply-To: <20040927123420.GO28275@ripe.net> References: <20040820130524.GA21467@ripe.net> <200408241719.52649.Peter_Losher@isc.org> <20040927123420.GO28275@ripe.net> Message-ID: <200409270923.36592.Peter_Losher@isc.org> On Monday 27 September 2004 05:34 am, Arife Vural wrote: > Everything is ready on RIS box, except the peering IP address. Cool. > I'm just wondering whether any progress about getting peering IP > address for RIS box. Paul has been working with Switch and Data on getting you access to the PAIX peering switch, so I'll let him give a status report on this. > BTW, I will be away for vacation from this Wed. Vasco, a colleague > of mine, will work on relocating RIS box at PAIX. Please, do not > forget to CC him and ris-request at ripe.net when you reply this e-mail. Will do. Have a nice holiday. :) Best Wishes - Peter -- Peter_Losher at isc.org | ISC | OpenPGP 0xE8048D08 | "The bits must flow" -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available URL: From paul at vix.com Tue Sep 28 01:01:13 2004 From: paul at vix.com (Paul Vixie) Date: Mon, 27 Sep 2004 23:01:13 +0000 Subject: [ris-int] Re: RIS box @ MAE-West In-Reply-To: Message from Arife Vural of "Mon, 27 Sep 2004 14:34:20 +0200." <20040927123420.GO28275@ripe.net> Message-ID: <20040927230113.619B813951@sa.vix.com> i'm making good progress with paix-s&d on getting you your own peering port. From arife at ripe.net Tue Sep 28 11:01:26 2004 From: arife at ripe.net (Arife Vural) Date: Tue, 28 Sep 2004 11:01:26 +0200 Subject: [ris-int] Re: RIS box @ MAE-West In-Reply-To: <200409270923.36592.Peter_Losher@isc.org> References: <20040820130524.GA21467@ripe.net> <200408241719.52649.Peter_Losher@isc.org> <20040927123420.GO28275@ripe.net> <200409270923.36592.Peter_Losher@isc.org> Message-ID: <20040928090126.GG16324@ripe.net> > > I'm just wondering whether any progress about getting peering IP > > address for RIS box. > > Paul has been working with Switch and Data on getting you access to the PAIX > peering switch, so I'll let him give a status report on this. OK. > > > BTW, I will be away for vacation from this Wed. Vasco, a colleague > > of mine, will work on relocating RIS box at PAIX. Please, do not > > forget to CC him and ris-request at ripe.net when you reply this e-mail. > > Will do. Have a nice holiday. :) Thanks. Arife From arife at ripe.net Tue Sep 28 11:06:09 2004 From: arife at ripe.net (Arife Vural) Date: Tue, 28 Sep 2004 11:06:09 +0200 Subject: [ris-int] NCC#2004092945 RIS box @ MAE-West In-Reply-To: <20040927230113.619B813951@sa.vix.com> References: <20040927123420.GO28275@ripe.net> <20040927230113.619B813951@sa.vix.com> Message-ID: <20040928090609.GH16324@ripe.net> > i'm making good progress with paix-s&d on getting you your own peering port. Good! Then, we will hear from you soon about peering details. Arife From shane at ripe.net Tue Sep 28 12:25:13 2004 From: shane at ripe.net (Shane Kerr) Date: Tue, 28 Sep 2004 12:25:13 +0200 Subject: [ris-int] RIS Beacons In-Reply-To: References: <200308181136.h7IBau3j005724@birch.ripe.net> <200409241353.i8ODriWn030333@x21.ripe.net> Message-ID: <41593C09.5010703@ripe.net> Henk Uijterwaal (RIPE NCC) wrote: > All, > > At SIGCOMM 2004, it became clear that the current beacon prefixes suffer > from 2 problems: > > a) They have more peers giving transit than any other AS on the Internet. > > b) When a prefix is invisible, it is not clear if this is caused by > an experimental problem or by the prefix being filtered. The > anchor prefix does not solve this problem, there should be one anchor > per beacon. > > So, people suggested that for the next period (1/10/2004-30/9/2005), we > make the following changes: > > 1. A new /19 is requested from the RIPE NCC. This /19 is split into > /24's. > > 2. Each RRC annouces 2 /24's. Assuming A.B.Z is the base address > > A.B.(Z+2*Y).0/24 > A.B.(Z+2*Y+1).0/24 > > For Y=0 to 13 for the (up to 16) RRC's. > > The first prefix is announced permanently. The second one is a flapping > prefix: up at 0 GMT, down at 2 GMT, up at 4 GMT etc. The pattern may > be changed at a later stage. > > 3. Inside each /24, a pingable address will be established. > > 4. We ask only 2 or 3 peers at each IX to provide transit for these > prefixes. (In other words, we do not ask everybody). > > 5. Other experiments that we do are: > > - An overflow prefix (prefix announced at 1 RRC, flapping at the next). > - Hitesh's experiment. > > 6. The current 195.80.224.0/20 is returned to the RIPE NCC > > > > Comments? This looks good to me. -- Shane Kerr RIPE NCC From arife at ripe.net Tue Sep 28 13:33:10 2004 From: arife at ripe.net (Arife Vural) Date: Tue, 28 Sep 2004 13:33:10 +0200 Subject: [ris-int] RRC13 (Moscow) & RRC14 (PAIX) Message-ID: <20040928113310.GO16324@ripe.net> Hi guys, If any of those RRCs would be online when I'm away, you can find the details of how to configure mySQL server and update CGIs in the following doc, http://iii/sed/twiki/bin/view/SED/HowToAddNewRRC I have already done mySQL config for RRC14. RRC13 needs to be done. Arife From arife at ripe.net Tue Sep 28 17:04:07 2004 From: arife at ripe.net (Arife Vural) Date: Tue, 28 Sep 2004 17:04:07 +0200 Subject: [ris-int] Arife is offline from now on. Message-ID: <20040928150407.GD32624@ripe.net> Hi all, I'll be away for a month. During that time if you need anything from me, you can reach by phone. My mobile number is, Mobile: +31 61 471 8561 I do not know yet, I might check my e-mails occasionally. But do not expect me to get back to you until I come back. Arife From matthew at ripe.net Tue Sep 28 21:12:04 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 28 Sep 2004 21:12:04 +0200 Subject: [ris-int] RIS Beacons In-Reply-To: <41593C09.5010703@ripe.net> Message-ID: <00f401c4a58f$0b275550$aba8a8c0@rockstar> Hi Henk, > > a) They have more peers giving transit than any other AS on the > > Internet. This was discussed internally right from day one of RIS beacon project. Good that the research community have confirmed concerns raised back then. > > > > b) When a prefix is invisible, it is not clear if this is caused by > > an experimental problem or by the prefix being filtered. The > > anchor prefix does not solve this problem, there should > be one anchor > > per beacon. Yup, our beacons were deemed practically useless in the paper by Mao, Bush et al, so it's good that we're finally fixing above. What about timestamping and sequence numbers in the BGP messages? Was this also something that needed to be addressed? Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Shane Kerr > Sent: 28 September 2004 12:25 > To: Henk Uijterwaal (RIPE NCC) > Cc: zmao at eecs.umich.edu; ris-int at ripe.net > Subject: Re: [ris-int] RIS Beacons > > > Henk Uijterwaal (RIPE NCC) wrote: > > All, > > > > At SIGCOMM 2004, it became clear that the current beacon prefixes > > suffer from 2 problems: > > > > a) They have more peers giving transit than any other AS on the > > Internet. > > > > b) When a prefix is invisible, it is not clear if this is caused by > > an experimental problem or by the prefix being filtered. The > > anchor prefix does not solve this problem, there should > be one anchor > > per beacon. > > > > So, people suggested that for the next period > (1/10/2004-30/9/2005), > > we make the following changes: > > > > 1. A new /19 is requested from the RIPE NCC. This /19 is split into > > /24's. > > > > 2. Each RRC annouces 2 /24's. Assuming A.B.Z is the base address > > > > A.B.(Z+2*Y).0/24 > > A.B.(Z+2*Y+1).0/24 > > > > For Y=0 to 13 for the (up to 16) RRC's. > > > > The first prefix is announced permanently. The second > one is a flapping > > prefix: up at 0 GMT, down at 2 GMT, up at 4 GMT etc. > The pattern may > > be changed at a later stage. > > > > 3. Inside each /24, a pingable address will be established. > > > > 4. We ask only 2 or 3 peers at each IX to provide transit for these > > prefixes. (In other words, we do not ask everybody). > > > > 5. Other experiments that we do are: > > > > - An overflow prefix (prefix announced at 1 RRC, > flapping at the next). > > - Hitesh's experiment. > > > > 6. The current 195.80.224.0/20 is returned to the RIPE NCC > > > > > > > > Comments? > > This looks good to me. > > -- > Shane Kerr > RIPE NCC > From zmao at eecs.umich.edu Wed Sep 29 06:57:05 2004 From: zmao at eecs.umich.edu (Z. Morley Mao) Date: Wed, 29 Sep 2004 00:57:05 -0400 (EDT) Subject: [ris-int] RIS Beacons In-Reply-To: <00f401c4a58f$0b275550$aba8a8c0@rockstar> References: <00f401c4a58f$0b275550$aba8a8c0@rockstar> Message-ID: Hi Henk and Matthew, Thanks very much for including me on these emails. I have also CC'd Ramesh Govindan and Paul Francis who are also interested in using the Beacons. > > > a) They have more peers giving transit than any other AS on the > > > Internet. > > This was discussed internally right from day one of RIS beacon project. > Good that the research community have confirmed concerns raised back > then. Would it be possible to set up the experiment such that the beacon alternates across the different upstream providers, i.e., at one point announced by two providers, then withdraw from one, re-announce to another one, etc? And iterate using another two different providers. For one of the multi-homed PSG beacons (hosted by Randy Bush), we are performing this experiment (shown http://www.psg.com/~zmao/beacon5.jpg) to understand the effect of fail over behavior. Perhaps something similar to this can be set up in the RIS beacon project. This would be very interesting to study. > > > > > > b) When a prefix is invisible, it is not clear if this is caused by > > > an experimental problem or by the prefix being filtered. The > > > anchor prefix does not solve this problem, there should > > be one anchor > > > per beacon. > > Yup, our beacons were deemed practically useless in the paper by Mao, > Bush et al, so it's good that we're finally fixing above. > > What about timestamping and sequence numbers in the BGP messages? Was > this also something that needed to be addressed? Perhaps a similar scheme to the PSG beacons can be adopted. Right now, for PSG beacons we are overloading the Aggregator AS field to denote the sequence number (each new announcement has a seq number incremented from the old one), and aggregator IP field to denote the time at which the message is sent out. To prevent people from misinterpreting these two fields, we make sure that the Aggregator AS is in the private AS range (64512-65535), and the Aggregator IP is also in the private address range (e.g., 10/8). Thanks! --Morley > Cheers, > Matthew > > > -----Original Message----- > > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > > On Behalf Of Shane Kerr > > Sent: 28 September 2004 12:25 > > To: Henk Uijterwaal (RIPE NCC) > > Cc: zmao at eecs.umich.edu; ris-int at ripe.net > > Subject: Re: [ris-int] RIS Beacons > > > > > > Henk Uijterwaal (RIPE NCC) wrote: > > > All, > > > > > > At SIGCOMM 2004, it became clear that the current beacon prefixes > > > suffer from 2 problems: > > > > > > a) They have more peers giving transit than any other AS on the > > > Internet. > > > > > > b) When a prefix is invisible, it is not clear if this is caused by > > > an experimental problem or by the prefix being filtered. The > > > anchor prefix does not solve this problem, there should > > be one anchor > > > per beacon. > > > > > > So, people suggested that for the next period > > (1/10/2004-30/9/2005), > > > we make the following changes: > > > > > > 1. A new /19 is requested from the RIPE NCC. This /19 is split into > > > /24's. > > > > > > 2. Each RRC annouces 2 /24's. Assuming A.B.Z is the base address > > > > > > A.B.(Z+2*Y).0/24 > > > A.B.(Z+2*Y+1).0/24 > > > > > > For Y=0 to 13 for the (up to 16) RRC's. > > > > > > The first prefix is announced permanently. The second > > one is a flapping > > > prefix: up at 0 GMT, down at 2 GMT, up at 4 GMT etc. > > The pattern may > > > be changed at a later stage. > > > > > > 3. Inside each /24, a pingable address will be established. > > > > > > 4. We ask only 2 or 3 peers at each IX to provide transit for these > > > prefixes. (In other words, we do not ask everybody). > > > > > > 5. Other experiments that we do are: > > > > > > - An overflow prefix (prefix announced at 1 RRC, > > flapping at the next). > > > - Hitesh's experiment. > > > > > > 6. The current 195.80.224.0/20 is returned to the RIPE NCC > > > > > > > > > > > > Comments? > > > > This looks good to me. > > > > -- > > Shane Kerr > > RIPE NCC > > > From matthew at ripe.net Thu Sep 30 13:04:20 2004 From: matthew at ripe.net (Matthew Williams) Date: Thu, 30 Sep 2004 13:04:20 +0200 Subject: FW: [ris-int] RIS Beacons Message-ID: <00db01c4a6dd$3c7f85b0$1f0200c1@rockstar> Sorry, forgot to include ris-int. /Matthew > -----Original Message----- > From: Matthew Williams [mailto:matthew at ripe.net] > Sent: 29 September 2004 16:05 > To: zmao at eecs.umich.edu > Cc: beacons at ripe.net > Subject: RE: [ris-int] RIS Beacons > > > Hi again, > > The old beacons list has been revitalised with the additions > of Shane, Paul and Ramesh. The more, the merrier ;) > > > Bush), we are performing this experiment (shown > > http://www.psg.com/~zmao/beacon5.jpg) to understand the > > effect of fail over behavior. Perhaps something similar to > > this can be set up in the RIS beacon project. This would be > > very interesting to study. > > Wow, quite an intricate little beacon. In principle, once we > have the appropriate set up with transit providers (and they > understand what we're doing), then we should be able to > oblige. The question, however, is how to prioritise among > many experiments and find the RIPE NCC resources to support > them. The RIS team will probably have to discuss this > internally before providing answers. > > > Perhaps a similar scheme to the PSG beacons can be adopted. > > Right now, for PSG beacons we are overloading the Aggregator > > Sorry, I forgot that James had actually implemented above. > > +++ > > Since 12th September 2003 > > All beacon prefixes are now announced with additional > attributes. We now overload the BGP AGGREGATOR attribute to > tag each announcement with a timestamp, a sequence number and > the identifier of the RRC making the announcement. These are > encoded as follows.... > > http://www.ripe.net/ris/beaconlist.html > > +++ > > This seems similar to PSG's schema, no? > > I believe that you use your own beacon code, while we still > use Quagga. Where there any special reasons for this or was > Quagga just to heavy-weight for beacon purposes? Moreover, > some concerns were raised about 'lag' between execution of > the cron job that modifies the [no] network statement and > when the a's or w's actually hit the wire. Is this still an > issue or will timestamping be sufficient to deal with it? > > Cheers, > Matthew > > > -----Original Message----- > > From: Z. Morley Mao [mailto:zmao at eecs.umich.edu] > > Sent: 29 September 2004 06:57 > > To: Matthew Williams > > Cc: 'Henk Uijterwaal (RIPE NCC)'; ris-int at ripe.net; 'Shane > > Kerr'; Ramesh Govindan; Paul Francis > > Subject: RE: [ris-int] RIS Beacons > > > > > > Hi Henk and Matthew, > > > > Thanks very much for including me on these emails. I have > > also CC'd Ramesh Govindan and Paul Francis who are also > > interested in using the Beacons. > > > > > > > a) They have more peers giving transit than any other > AS on the > > > > > Internet. > > > > > > This was discussed internally right from day one of RIS beacon > > > project. Good that the research community have confirmed concerns > > > raised back then. > > > > Would it be possible to set up the experiment such that the > > beacon alternates across the different upstream providers, > > i.e., at one point announced by two providers, then withdraw > > from one, re-announce to another one, etc? And iterate using > > another two different providers. > > > > For one of the multi-homed PSG beacons (hosted by Randy > > Bush), we are performing this experiment (shown > > http://www.psg.com/~zmao/beacon5.jpg) to understand the > > effect of fail over behavior. Perhaps something similar to > > this can be set up in the RIS beacon project. This would be > > very interesting to study. > > > > > > > > > > > > b) When a prefix is invisible, it is not clear if this > > is caused by > > > > > an experimental problem or by the prefix being > > filtered. The > > > > > anchor prefix does not solve this problem, there should > > > > be one anchor > > > > > per beacon. > > > > > > Yup, our beacons were deemed practically useless in the > > paper by Mao, > > > Bush et al, so it's good that we're finally fixing above. > > > > > > What about timestamping and sequence numbers in the BGP > > messages? Was > > > this also something that needed to be addressed? > > > > Perhaps a similar scheme to the PSG beacons can be adopted. > > Right now, for PSG beacons we are overloading the Aggregator > > AS field to denote the sequence number (each new announcement > > has a seq number incremented from the old one), and > > aggregator IP field to denote the time at which the message > > is sent out. To prevent people from misinterpreting these > > two fields, we make sure that the Aggregator AS is in the > > private AS range (64512-65535), and the Aggregator IP is also > > in the private address range (e.g., 10/8). > > > > Thanks! > > > > --Morley > > > > > Cheers, > > > Matthew > > > > > > > -----Original Message----- > > > > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] On > > > > Behalf Of Shane Kerr > > > > Sent: 28 September 2004 12:25 > > > > To: Henk Uijterwaal (RIPE NCC) > > > > Cc: zmao at eecs.umich.edu; ris-int at ripe.net > > > > Subject: Re: [ris-int] RIS Beacons > > > > > > > > > > > > Henk Uijterwaal (RIPE NCC) wrote: > > > > > All, > > > > > > > > > > At SIGCOMM 2004, it became clear that the current > > beacon prefixes > > > > > suffer from 2 problems: > > > > > > > > > > a) They have more peers giving transit than any other > > AS on the > > > > > Internet. > > > > > > > > > > b) When a prefix is invisible, it is not clear if this > > is caused by > > > > > an experimental problem or by the prefix being > > filtered. The > > > > > anchor prefix does not solve this problem, there should > > > > be one anchor > > > > > per beacon. > > > > > > > > > > So, people suggested that for the next period > > > > (1/10/2004-30/9/2005), > > > > > we make the following changes: > > > > > > > > > > 1. A new /19 is requested from the RIPE NCC. This /19 > > is split into > > > > > /24's. > > > > > > > > > > 2. Each RRC annouces 2 /24's. Assuming A.B.Z is the > > base address > > > > > > > > > > A.B.(Z+2*Y).0/24 > > > > > A.B.(Z+2*Y+1).0/24 > > > > > > > > > > For Y=0 to 13 for the (up to 16) RRC's. > > > > > > > > > > The first prefix is announced permanently. The second > > > > one is a flapping > > > > > prefix: up at 0 GMT, down at 2 GMT, up at 4 GMT etc. > > > > The pattern may > > > > > be changed at a later stage. > > > > > > > > > > 3. Inside each /24, a pingable address will be established. > > > > > > > > > > 4. We ask only 2 or 3 peers at each IX to provide > > transit for these > > > > > prefixes. (In other words, we do not ask everybody). > > > > > > > > > > 5. Other experiments that we do are: > > > > > > > > > > - An overflow prefix (prefix announced at 1 RRC, > > > > flapping at the next). > > > > > - Hitesh's experiment. > > > > > > > > > > 6. The current 195.80.224.0/20 is returned to the RIPE NCC > > > > > > > > > > > > > > > > > > > > Comments? > > > > > > > > This looks good to me. > > > > > > > > -- > > > > Shane Kerr > > > > RIPE NCC > > > > > > > > > > > From alexis at ww.net Thu Sep 30 15:30:16 2004 From: alexis at ww.net (Alexis Yushin) Date: Thu, 30 Sep 2004 15:30:16 +0200 Subject: [ris-int] some notes regarding myasn... Message-ID: <20040930133016.GA32375@virgin.ww.net> Hi, Yesterday, in the brewery, I understood from Henk that you guys are going to have a myasn meeting somewhere in the near future. I thought it might be usefull if I send in some ideas of what needs to be done/implemented. I'm also looking for a new contract right now and I would be quite willing to work on myasn again :) Either way I hope that my input helps. Cheers, Alexis Prio 1. - bugfixes/feature implementation (obvious) - proper authentication module (with logout option) - optimization/clean-up myasn-scan/myasn-send/myasn-admin move the functionality of these programs into respective RIPE::NCC::myASn::Scan RIPE::NCC::myASn::Send (this will untie lots of knots and make myasn much more extendable) - reimplement XML import with XML::DOM and use as DTD - enable retromatch (will be trivial after myasn-scan reimplemented as perl interface; retromatch is already in there but requires a rather resource inefficient invokation of myasn-scan) - handle notification mail bounces/errors with some inteligence - graphical (.png) summary on the start page Prio 2. - prefix independent alarms with complex (multi-part) regular expressions (this is one most important and powerfull feature that will make myasn usefull for much larger range of applications) - site global alarm groups with possibility to subscribe to them (martians system/default route) - visibility alarms - churn based alarms - snmp alarm notifications - pgp signing of notification messages (usefull?) Prio 3. - auto sync with IRR and LIR portal (for prefixes and as numbers) - self tuning alarms From matthew at ripe.net Thu Sep 30 18:28:55 2004 From: matthew at ripe.net (Matthew Williams) Date: Thu, 30 Sep 2004 18:28:55 +0200 Subject: [ris-int] FW: myASN code walk-through Message-ID: <00ff01c4a70a$946bc9a0$1f0200c1@rockstar> Hi Ziya, Olaf Maennel at the Technical University of Munich is helping us out with ideas for future myASn alarms. I know this is short notice, but when would you have time for a conf call with Olaf and a student of his? Olaf Maennel wrote: > do you have some time for a conf call on Tuesday, Oct 05 at 3pm or > 3:30pm? > I'm meeting Florian Hauer, the student working on myASN. If > time permits > on your side for a quick(*) walk through the latest version of the > myASN code that would be very helpful, because Florian could > participate. What do you think? Cheers, Matthew