July 2004 - Ris-int - mailman.ripe.net

ris@ripe.net e-mail are ticketized from now on.
by Arife Vural 23 Jul '04

23 Jul '04

Hi guys, ris e-mails are ticketized from now on. ris is staying as mailinglist, and one copy of the e-mail is going to RIS ticketing que. People who are in the ris list will continue get the all ris e-mails. If you do not want, ask OPS to remove your e-mail address. But, please if you like to reply any of those e-mails, use XRTT. Otherwise, we loose control who replied which e-mail and so. Arife

1 0

MSK-IX RRC
by Matthew Williams 23 Jul '04

23 Jul '04

Just thinking out loud: In order to circumvent excessive $$$ at Russian customs, wouldn't it be smarter to have the IXP order a Dell PowerEdge to OPS requirements and ship your nifty little CD instead? Would that work or should we just go down the normal route. I will naturally have to ask the IXP as well. Cheers, Matthew

3 5

Other RIS things ...
by Matthew Williams 23 Jul '04

23 Jul '04

Hi Arife, Mae-West doesn't seem to be picking up in peers (4 - and according to Hong-Wei, no full feeds). It was some time ago since you tried to get their attention (nanog in miami?). After the good experiences at the NYIIX, shall we try LAIX? What do you think? BC thought that we should wait until the end of the year, but that requires giving gebert, bechly and pucik a little push (again). BTW, have you thought about cleaning up active bgp session or it that ops work? If they already have tools to monitor anycast and 3333 sessions then maybe the RIS could just plug into that. Cheers, Matthew +++ RRC00 ----- 195.66.224.112 4 3549 0 0 0 0 0 never Active | 195.69.144.85 4 3257 0 0 0 0 0 never Connect | RRC01 ----- 195.66.224.40 4 15861 0 0 0 0 0 never Active | 195.66.224.41 4 5604 0 0 0 0 0 never Active | 195.66.224.48 4 1299 0 0 0 0 0 never Active | 195.66.224.117 4 12513 0 0 0 0 0 never Active | 195.66.224.168 4 20940 0 10123 0 0 0 never Active | 195.66.226.10 4 2856 86 9 0 0 0 03w5d22h Connect | 195.66.226.11 4 2856 85 9 0 0 0 03w5d22h Connect | 195.66.226.40 4 15861 0 0 0 0 0 never Active | 195.66.226.47 4 8272 0 0 0 0 0 never Active | 195.66.226.103 4 2818 442 299 0 0 0 2d15h56m Active | 195.66.226.119 4 12390 0 0 0 0 0 never Connect | RRC02 ----- 194.68.129.164 4 13237 0 0 0 0 0 never Active | 194.68.129.173 4 6774 0 0 0 0 0 never Connect | 194.68.129.186 4 20766 356 355376 0 0 0 4d15h53m Idle | 194.68.129.225 4 5462 0 0 0 0 0 never Active | 194.68.129.252 4 2686 0 0 0 0 0 never Active | Etc....

4 4

myASN SQL queries
by Arife Vural 22 Jul '04

22 Jul '04

Hi Alexis, Today, when I looked at mySQL logs, I saw the one of myASN query and it returns almost all the entries in table. I do not know that was the intention or not. But, when we meet up for handover, I would like to go over those SQLs with you whether we can do any optimization or not. BTW, I hope tomorrow morning is OK for you. I have not got a reply from you yet. Arife

1 0

myASN transition on Wed, 14.00
by Arife Vural 21 Jul '04

21 Jul '04

Hi guys, What about working myASN transition on Wed, 14.00? Arife

4 6

We need your fb again ;)
by Matthew Williams 21 Jul '04

21 Jul '04

Hi Comms, Please see explanations here: http://www.ripe.net/ris/myasngls.html#50 And then think about alternative terms for below: *Hold Down Time *Hold Down Event: 'Min-Event-Duration' and 'Min-Event-Count' are our current candidates. *Time To Live: We have two lines of thought here. One relates to 'detection' of events building up to an alarm entry in the email sent to the user, while the other follows the line of 'suppression' of further entries once the first entry has been triggered (based on exactly the same events). If we go along with the second concept, then this is a maximum time interval. In the first case, we're talking about a fixed 'window' (time interval). I hope all that made sense ;) Here come some suggestions: "Event-count Window", "Alarm-Suppress-Time", "Max-suppress-time", "Event-Suppress-Time', "max-detect-window", "alarm-detect-window"... Etc etc... We could go on forever and ever. The question is: What works for you? The beta is more or less ready so we need to get this one out of the way once and for all... ;) Cheers, Matthew --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/

4 4

Today's RIS meeting minutes
by Arife Vural 21 Jul '04

21 Jul '04

Main points: - RIS budget issue is discussed. New RRC hardware and replacement would be in OPS budget. Arife compiled the needs for RIS server and sent it to Shane. Shane will discuss this with Henk/Andrei. Shane suggest to make an analysis how many RIS servers we like to install and then do the installation at one go, rather than each year putting 2 new RRCs in budget. Matthew mentioned installation of 2 new RRCs (Dubai, Moscow) are in discussion. - This week Arife and Alessandro from SED will sit down with Alexis to talk about myASN transition. - After RIS transition it seems a lot of thing is settle down, because of that there is not much need to do RIS meeting every week. From now on, there will be RIS meeting once in two week. Arife will update the Ctime accordingly. Any correction/addition/comments are welcome. Arife

2 2

myasn xml
by Alexis Yushin 15 Jul '04

15 Jul '04

Hi, I've just added http://www.ris.ripe.net/myasn/xml.html, a page to import myASn configuration as XML... Its not linked into index yet, since it has not been properly tested. Syntax is something like: <alarmgroup name="XML-Import"> <alarm type="origin" mec="1" med="1m" ast="1h"> <prefix>193.0.0.0/16</prefix> <exception>193.0.1.0/24</exception> <exception>193.0.2.0/24</exception> <myasn>12324 2344</myasn> </alarm> <alarm type="customer"> <prefix>193.0.0.0/16</prefix> <exception>193.0.1.0/24</exception> <exception>193.0.2.0/24</exception> <myasn>12324 2344</myasn> <theirasn>12324 2344</theirasn> </alarm> </alarmgroup> You get the idea... Alexis

1 0

Re: [staff] DHL: received goods
by James Aldridge 15 Jul '04

15 Jul '04

Saskia van Gorp wrote: > Hi all, > > Did anybody around end of June - beginning of July receive a package from > Vienna (Austria) > Airway bill: 582 5977511 > Ref: inivie/vix > Sent out from Vienna on June 26. I guess that this was the old RIS Route Collector (rrc05) being returned. James

1 0

FW: ANNOUNCEMENT: New RIS Remote Route Collector at DE-CIX (RRC12)
by Matthew Williams 14 Jul '04

14 Jul '04

Hi Webbies, Would it be possible to link http://www.ripe.net/ris/rrc12.html from http://www.ripe.net/ ? Text something like: "RIPE NCC Remote Route Collector deployed at the German Internet Exchange (DE-CIX)" Many thanks! Cheers, Matthew > -----Original Message----- > From: Matthew Williams [mailto:matthew@ripe.net] > Sent: 07 July 2004 19:11 > To: 'ris-users(a)ripe.net' > Subject: ANNOUNCEMENT: New RIS Remote Route Collector at > DE-CIX (RRC12) > > > > > *** PGP Signature Status: good > *** Signer: Matthew Williams-Bywater <matthew(a)ripe.net> > *** Signed: 07/07/2004 19:11:05 > *** Verified: 14/07/2004 18:50:15 > *** BEGIN PGP VERIFIED MESSAGE *** > > [Apologies for duplicate mails] > > Dear All, > > The RIPE NCC is pleased to announce that the RIS Project's > twelth* Remote Route Collector, RRC12, is now ready to peer > with members at the German Internet Exchange (DE-CIX). > > RRC12 is located at the German Internet Exchange (DE-CIX), > and has been operational since July 2004. The RRC has an > interface on the shared DE-CIX fabric, running both IPv4 and > IPv6, and collects routing information from all exchange > members, who are willing to peer with us. > > The use of TCP MD5 Signatures on IPv4 BGP sessions is > supported on all RIS Route Collectors. MD5, however, is not > supported on IPv6 sessions. > > Details: > -------- > - Peering address: 80.81.192.152 (IPv4); 2001:7f8::316e:0:1 (IPv6) > - Autonomous system: 12654 > - Policy: http://www.ripe.net/ris/rrc12.html > - Peering requests: > * Email: rispeering(a)ripe.net > * Web form at URL: http://www.ris.ripe.net/cgi-bin/peerreg.cgi > > The Routing Information Service (RIS), which started as a > modest RIPE NCC project in 1999, has gradually grown to over > 300 IPv4 and IPv6 peers at now twelve* data collection points > in Europe, Japan and North America. Our mission is to collect > BGP routing information over a function of time, and make it > available to the Internet community. In essence, this means > devising tools that can help ISPs debug problems over time > without being limited to one BGP view and providing RIS raw > data regarding the Internet's historical development. > > Useful Links: > ------------- > RIS Info: http://www.ripe.net/ris/ > RIS Tools: http://www.ripe.net/ris/query.html > List of RRC Locations: http://www.ris.ripe.net/cgi-bin/rrcstatus.cgi > > Please send your comments to ris-int(a)ripe.net. > > Best regards, > The RIS Team > > *) RRC09 has been decommissioned > > --- > > Matthew Williams (MW243-RIPE) > > Customer Liaison Engineer > > RIPE NCC - http://www.ripe.net/np/ > > > *** END PGP VERIFIED MESSAGE *** >

1 0

Re: [ris-int] Reply-To forwarded to /dev/null in myASn messages
by Rene Wilhelm 14 Jul '04

14 Jul '04

Hi, > ... myASn can use reply-to address forwarded to /dev/null Are we sure we want that? How often does it happen? Shouldn't there be follow by a risopsy when a notification fails to be delivered? (for permanent failures, either try to get in touch with representatives of the AS to correct the address, or deconfigure the alarm???) -- Rene > Hi guys, > > Can we do this? > > Arife > > ----- Forwarded message from Alexis Yushin <alexis(a)ripe.net> ----- > > From: Alexis Yushin <alexis(a)ripe.net> > To: matthew(a)ripe.net (Matthew Williams) > Subject: Re: [MAILER-DAEMON(a)ripe.net: Undelivered Mail Returned to Sender] > Date: Wed, 14 Jul 2004 13:17:01 +0200 (CEST) > Cc: alexis(a)ripe.net (Alexis Yushin), arife(a)ripe.net (Arife Vural), > ris-int(a)ripe.net > > Arife, > > We need to add risops to the trusted users class in sendmail.cf on weesp. > Something like > > FEATURE(`use_ct_file') dnl > > and > > /etc/mail/trusted-users > uucp > root > daemon > risops > > So myASn can use reply-to address forwarded to /dev/null > > Alexis > > > Once Matthew Williams wrote: > >Hi Alexis, > > > >Working on this? > > > >Cheers, > >Matthew > > > >----- Forwarded message from Mail Delivery System <MAILER-DAEMON(a)ripe.net> ----- > > > >X-Recipient: <risops(a)ripe.net> > >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > >From: MAILER-DAEMON(a)ripe.net (Mail Delivery System) > >Subject: Undelivered Mail Returned to Sender > >To: risops(a)ripe.net > > > >Content-Description: Notification > >This is the Postfix program at host postman.ripe.net. > > > >I'm sorry to have to inform you that the message returned > >below could not be delivered to one or more destinations. > > > >For further assistance, please send mail to <postmaster> > > > >If you do so, please include this problem report. You can > >delete your own text from the message returned below. > > > > The Postfix program > > > ><asnalarm(a)linkey.ru>: host mail.linkey.ru[213.159.99.4] said: 550 sorry, no > > mailbox here by that name (#5.1.1 - chkusr) > > > >Content-Description: Delivery error report > >Reporting-MTA: dns; postman.ripe.net > >Arrival-Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > > > >Final-Recipient: rfc822; asnalarm(a)linkey.ru > >Action: failed > >Status: 5.0.0 > >Diagnostic-Code: X-Postfix; host mail.linkey.ru[213.159.99.4] said: 550 sorry, > > no mailbox here by that name (#5.1.1 - chkusr) > > > >Content-Description: Undelivered Message > >Date: Tue, 13 Jul 2004 21:43:49 GMT > >From: myASn Notifications <myasn(a)ripe.net> > >To: asnalarm(a)linkey.ru > >Subject: New alarms for 13302 > >X-RIPE-Spam-Level: > >X-RIPE-Spam-Status: N 0.111983 / 0.0 / 0.0 / disabled > >X-RIPE-Signature: b5599a70a52cbd8205f40bab1f24afd6 > > > > > >Dear myASn contact, > > > >New alarms were detected for 13302. Please find the details below. Depending on your detail > >level settings you might not see all the events. Please use the web interface for further details. > > > >-- myASn System > > > > > >Transit alarm 713 (Transit), 213.159.96.0/19 (exceptions not shown), myASn: , Their ASn: , HDT: 60, HDE: 1, TTL: 3600 > >.=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=. > >| RRC | Prefix | AS Path | Conflict | Peer | UTC First | UTC Last | Count | > >|=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=| > >| rrc00 | 213.159.96.0/19 | | | 129.250.0.232 | Tue Jul 13 21:16:35 2004 | Tue Jul 13 21:16:35 2004 | 1 | > >'=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=' > > > > > >----- End forwarded message ----- > > > >-- > >>Matthew Williams > >>Customer Liaison Engineer > >>RIPE - Network Coordination Centre (www.ripe.net) > > > > ----- End forwarded message ----- >

4 4

Re: [ris-int] Reply-To forwarded to /dev/null in myASn messages
by Rene Wilhelm 14 Jul '04

14 Jul '04

>> Shouldn't there be follow up by a risopsy when a notification >> fails to be delivered? (for permanent failures, either try > Quite unlikely, if I know that alarm notifications were successfully > sent to my inbox. Sorry, I don't understand your reply. If a mail from the myASn system bounces, someone should in my opinion take action. Either the user made a mistake, typo, entering the e-mail address in the myASn system, or he has left the ISP owning the ASn. risops could try to get in touch with the ASn owner, to get the email address corrrected (remember, we are running a _service_ ) or when that fails remove the address from the alarm system (no point polluting internal an external systems with e-mails you know will bounce back) Also, when the human recipients behind a remote e-mail change, they might reply, querying what the message was about; it's not polite to silently ignore such one-off replies. -- Rene > > We need to add risops to the trusted users class in sendmail.cf on > > weesp. Something like > > So myASn can use reply-to address forwarded to /dev/null > > > > Once Matthew Williams wrote: > > >Hi Alexis, > > > > > >Working on this? > > > > > >Cheers, > > >Matthew > > > > > >----- Forwarded message from Mail Delivery System > > ><MAILER-DAEMON(a)ripe.net> ----- > > > > > >X-Recipient: <risops(a)ripe.net> > > >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > > >From: MAILER-DAEMON(a)ripe.net (Mail Delivery System) > > >Subject: Undelivered Mail Returned to Sender > > >To: risops(a)ripe.net

2 2

Re: [MAILER-DAEMON@ripe.net: Undelivered Mail Returned to Sender]
by Alexis Yushin 14 Jul '04

14 Jul '04

Arife, We need to add risops to the trusted users class in sendmail.cf on weesp. Something like FEATURE(`use_ct_file') dnl and /etc/mail/trusted-users uucp root daemon risops So myASn can use reply-to address forwarded to /dev/null Alexis Once Matthew Williams wrote: >Hi Alexis, > >Working on this? > >Cheers, >Matthew > >----- Forwarded message from Mail Delivery System <MAILER-DAEMON(a)ripe.net> ----- > >X-Recipient: <risops(a)ripe.net> >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) >From: MAILER-DAEMON(a)ripe.net (Mail Delivery System) >Subject: Undelivered Mail Returned to Sender >To: risops(a)ripe.net > >Content-Description: Notification >This is the Postfix program at host postman.ripe.net. > >I'm sorry to have to inform you that the message returned >below could not be delivered to one or more destinations. > >For further assistance, please send mail to <postmaster> > >If you do so, please include this problem report. You can >delete your own text from the message returned below. > > The Postfix program > ><asnalarm(a)linkey.ru>: host mail.linkey.ru[213.159.99.4] said: 550 sorry, no > mailbox here by that name (#5.1.1 - chkusr) > >Content-Description: Delivery error report >Reporting-MTA: dns; postman.ripe.net >Arrival-Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > >Final-Recipient: rfc822; asnalarm(a)linkey.ru >Action: failed >Status: 5.0.0 >Diagnostic-Code: X-Postfix; host mail.linkey.ru[213.159.99.4] said: 550 sorry, > no mailbox here by that name (#5.1.1 - chkusr) > >Content-Description: Undelivered Message >Date: Tue, 13 Jul 2004 21:43:49 GMT >From: myASn Notifications <myasn(a)ripe.net> >To: asnalarm(a)linkey.ru >Subject: New alarms for 13302 >X-RIPE-Spam-Level: >X-RIPE-Spam-Status: N 0.111983 / 0.0 / 0.0 / disabled >X-RIPE-Signature: b5599a70a52cbd8205f40bab1f24afd6 > > >Dear myASn contact, > >New alarms were detected for 13302. Please find the details below. Depending on your detail >level settings you might not see all the events. Please use the web interface for further details. > >-- myASn System > > >Transit alarm 713 (Transit), 213.159.96.0/19 (exceptions not shown), myASn: , Their ASn: , HDT: 60, HDE: 1, TTL: 3600 >.=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=. >| RRC | Prefix | AS Path | Conflict | Peer | UTC First | UTC Last | Count | >|=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=| >| rrc00 | 213.159.96.0/19 | | | 129.250.0.232 | Tue Jul 13 21:16:35 2004 | Tue Jul 13 21:16:35 2004 | 1 | >'=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=' > > >----- End forwarded message ----- > >-- >>Matthew Williams >>Customer Liaison Engineer >>RIPE - Network Coordination Centre (www.ripe.net) >

3 4

[alexis@ripe.net: Re: [MAILER-DAEMON@ripe.net: Undelivered Mail Returned to Sender]]
by Arife Vural 14 Jul '04

14 Jul '04

Hi guys, Can we do this? Arife ----- Forwarded message from Alexis Yushin <alexis(a)ripe.net> ----- From: Alexis Yushin <alexis(a)ripe.net> To: matthew(a)ripe.net (Matthew Williams) Subject: Re: [MAILER-DAEMON(a)ripe.net: Undelivered Mail Returned to Sender] Date: Wed, 14 Jul 2004 13:17:01 +0200 (CEST) Cc: alexis(a)ripe.net (Alexis Yushin), arife(a)ripe.net (Arife Vural), ris-int(a)ripe.net Arife, We need to add risops to the trusted users class in sendmail.cf on weesp. Something like FEATURE(`use_ct_file') dnl and /etc/mail/trusted-users uucp root daemon risops So myASn can use reply-to address forwarded to /dev/null Alexis Once Matthew Williams wrote: >Hi Alexis, > >Working on this? > >Cheers, >Matthew > >----- Forwarded message from Mail Delivery System <MAILER-DAEMON(a)ripe.net> ----- > >X-Recipient: <risops(a)ripe.net> >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) >From: MAILER-DAEMON(a)ripe.net (Mail Delivery System) >Subject: Undelivered Mail Returned to Sender >To: risops(a)ripe.net > >Content-Description: Notification >This is the Postfix program at host postman.ripe.net. > >I'm sorry to have to inform you that the message returned >below could not be delivered to one or more destinations. > >For further assistance, please send mail to <postmaster> > >If you do so, please include this problem report. You can >delete your own text from the message returned below. > > The Postfix program > ><asnalarm(a)linkey.ru>: host mail.linkey.ru[213.159.99.4] said: 550 sorry, no > mailbox here by that name (#5.1.1 - chkusr) > >Content-Description: Delivery error report >Reporting-MTA: dns; postman.ripe.net >Arrival-Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > >Final-Recipient: rfc822; asnalarm(a)linkey.ru >Action: failed >Status: 5.0.0 >Diagnostic-Code: X-Postfix; host mail.linkey.ru[213.159.99.4] said: 550 sorry, > no mailbox here by that name (#5.1.1 - chkusr) > >Content-Description: Undelivered Message >Date: Tue, 13 Jul 2004 21:43:49 GMT >From: myASn Notifications <myasn(a)ripe.net> >To: asnalarm(a)linkey.ru >Subject: New alarms for 13302 >X-RIPE-Spam-Level: >X-RIPE-Spam-Status: N 0.111983 / 0.0 / 0.0 / disabled >X-RIPE-Signature: b5599a70a52cbd8205f40bab1f24afd6 > > >Dear myASn contact, > >New alarms were detected for 13302. Please find the details below. Depending on your detail >level settings you might not see all the events. Please use the web interface for further details. > >-- myASn System > > >Transit alarm 713 (Transit), 213.159.96.0/19 (exceptions not shown), myASn: , Their ASn: , HDT: 60, HDE: 1, TTL: 3600 >.=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=. >| RRC | Prefix | AS Path | Conflict | Peer | UTC First | UTC Last | Count | >|=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=| >| rrc00 | 213.159.96.0/19 | | | 129.250.0.232 | Tue Jul 13 21:16:35 2004 | Tue Jul 13 21:16:35 2004 | 1 | >'=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=' > > >----- End forwarded message ----- > >-- >>Matthew Williams >>Customer Liaison Engineer >>RIPE - Network Coordination Centre (www.ripe.net) > ----- End forwarded message -----

1 0

rrc12
by Matthew Williams 13 Jul '04

13 Jul '04

Hi Arife, Are we ready to announce RRC12? Cheers, Matthew

3 12

Re: FW: [ris-int] Logging on to rrcs
by Rene Wilhelm 13 Jul '04

13 Jul '04

Hi James, > Matthew wrote: > > > > > Please add me to users who can logon to rrcs :) > > > > Please open a ticket using "stt ops" or via the form on iii > > James while I can understand mailto:ops, I still have difficulty seeing any benefit in "stt" or webform. What difference does it make to ops? Do you (yes you're one of "them" now:-) have seperate queues for each (sub)category? Or are these purely administrative, to see how many tickets in which category were handled by which person? Why does the user have to classify his ticket? isn't that better done by ops? -- Rene

1 0

FW: [ris-int] Logging on to rrcs
by Matthew Williams 13 Jul '04

13 Jul '04

Hi there, Please add me to users who can logon to rrcs :) Cheers, Matthew > -----Original Message----- > From: ris-int-admin(a)ripe.net [mailto:ris-int-admin@ripe.net] > On Behalf Of Arife Vural > Sent: 13 July 2004 15:43 > To: Matthew Williams > Cc: ris-int(a)ripe.net > Subject: Re: [ris-int] Logging on to rrcs > > > > Hi Matthew, > > It looks your username is not in /etc/passwd file on RRCs. > Can you send an e-mail to OPS to add? > > Arife > > On Tue, Jul 13, 2004 at 03:37:02PM +0200, Arife Vural wrote: > > > > Hi Matthew, > > > > > I seem to have some probs logging on.... (all rrcs?) > > > > > > > You have to login by your username, and then if you need you > > can run sudo command switch to risops or root user. After > > Linux migration, OPS changed login to RRC boxes from risops > > to individual users. This way it would more easy for OPS to > > keep track who runs which command and so. > > > > BTW, if you need to connect BGPD on RRCs you do not need > > to loging box, you can run, > > > > telnet rrc031 2605 > > > > That connection is open only RIPE NCC prefix. > > > > Arife > > > > > matthew@cow at 15:22:15:~$ ssh rrc031 -l risops > > > Warning: Permanently added 'rrc031,193.0.0.232' (RSA) to > the list of > > > known hosts. Permission denied (publickey,keyboard-interactive). > > > > > > matthew@cow at 15:22:20:~$ ssh rrc021 -l risops > > > Permission denied (publickey,keyboard-interactive). > > > > > > Cheers, > > > Matthew >

2 2

FW: [ris-int] Logging on to rrcs
by Matthew Williams 13 Jul '04

13 Jul '04

Don't bother as I'll probably only need bgpd access anyway ;) , but please update docs with procedure. Cheers, matthew > -----Original Message----- > From: ris-int-admin(a)ripe.net [mailto:ris-int-admin@ripe.net] > On Behalf Of Matthew Williams > Sent: 13 July 2004 15:44 > To: 'James Aldridge' > Cc: ris-int(a)ripe.net > Subject: FW: [ris-int] Logging on to rrcs > > > Hi there, > > Please add me to users who can logon to rrcs :) > > Cheers, > Matthew > > > -----Original Message----- > > From: ris-int-admin(a)ripe.net [mailto:ris-int-admin@ripe.net] > > On Behalf Of Arife Vural > > Sent: 13 July 2004 15:43 > > To: Matthew Williams > > Cc: ris-int(a)ripe.net > > Subject: Re: [ris-int] Logging on to rrcs > > > > > > > > Hi Matthew, > > > > It looks your username is not in /etc/passwd file on RRCs. Can you > > send an e-mail to OPS to add? > > > > Arife > > > > On Tue, Jul 13, 2004 at 03:37:02PM +0200, Arife Vural wrote: > > > > > > Hi Matthew, > > > > > > > I seem to have some probs logging on.... (all rrcs?) > > > > > > > > > > You have to login by your username, and then if you need > you can run > > > sudo command switch to risops or root user. After Linux > migration, > > > OPS changed login to RRC boxes from risops to individual > users. This > > > way it would more easy for OPS to keep track who runs > which command > > > and so. > > > > > > BTW, if you need to connect BGPD on RRCs you do not need > > > to loging box, you can run, > > > > > > telnet rrc031 2605 > > > > > > That connection is open only RIPE NCC prefix. > > > > > > Arife > > > > > > > matthew@cow at 15:22:15:~$ ssh rrc031 -l risops > > > > Warning: Permanently added 'rrc031,193.0.0.232' (RSA) to > > the list of > > > > known hosts. Permission denied (publickey,keyboard-interactive). > > > > > > > > matthew@cow at 15:22:20:~$ ssh rrc021 -l risops > Permission denied > > > > (publickey,keyboard-interactive). > > > > > > > > Cheers, > > > > Matthew > > >

1 0

Logging on to rrcs
by Matthew Williams 13 Jul '04

13 Jul '04

Hi Arife, I seem to have some probs logging on.... (all rrcs?) matthew@cow at 15:22:15:~$ ssh rrc031 -l risops Warning: Permanently added 'rrc031,193.0.0.232' (RSA) to the list of known hosts. Permission denied (publickey,keyboard-interactive). matthew@cow at 15:22:20:~$ ssh rrc021 -l risops Permission denied (publickey,keyboard-interactive). Cheers, Matthew

2 3

FW: myasn handover
by Matthew Williams 12 Jul '04

12 Jul '04

Hi Shane, How do you want to schedule below? Cheers, Matthew > -----Original Message----- > From: Alexis Yushin [mailto:alexis@ripe.net] > Sent: 12 July 2004 14:13 > To: Matthew Williams > Subject: myasn handover > > I'm pratically finished with all the stuff (unless I forgot > something), how do we go about the handover? Is there a > meeting scheduled with Shane or whoever? In my contract we > have three days at the office planned for handover, do you > know which days these will be?

1 0

Shut down of myASn prototype
by Matthew Williams 12 Jul '04

12 Jul '04

Hi Arife, It might be a good idea to send out a brief notification shortly before you shut it down ;) Cheers, Matthew

1 0

RE: Bug in bgpdump
by hong-wei_kong＠agilent.com 10 Jul '04

10 Jul '04

Hi Lorenzo, I noticed that the patch will cause problem to IPv4 prefixes and next hop. There is some minor bug in the patch. I have fixed it and checked the result. please check this one in. regards, hongwei -----Original Message----- From: Lorenzo Colitti [mailto:colitti@dia.uniroma3.it] Sent: Monday, July 05, 2004 7:56 PM To: hong-wei_kong(a)agilent.com Cc: ris-int(a)ripe.net; pizzonia(a)dia.uniroma3.it Subject: Re: Bug in bgpdump hong-wei_kong(a)agilent.com wrote: > Hi Lorenzo, > > Thank you for fixing this bug. However, I don't find the attached > patch with your email. Have you forgot to attach the file? Yes, I forgot. ;-) Here it is. Can someone check it in? Cheers, Lorenzo -- --------------------------------------------------------- Lorenzo Colitti Ph.D student Computer Networks research group Roma Tre University colitti(a)dia.uniroma3.it +39-0655173215 ---------------------------------------------------------

1 0

Bread crumbs
by Matthew Williams 09 Jul '04

09 Jul '04

Hi Alexis, Can you add bread crumbs (top-left corner: myASn>xxx) for 'Getting Started Guide', 'FAQ', 'Reported Bugs', 'Requested Features' and 'Acknowledgments'? Cheers, Matthew

2 6

Web Access Report for the Routing Information Service - June, 2004
by Matthew Williams 09 Jul '04

09 Jul '04

Hi All, The monthly RIS Web Access Report is available at the following URL: http://iii.ripe.net/np/ris/WWW062004_RIS.pdf Please comment on oddities (there is a 'p' missing somewhere ;) Cheers, Matthew

1 0

code update
by Alexis Yushin 09 Jul '04

09 Jul '04

Matthew, I think the best option since we have limited time if you send a notification to users that due to code update or maintenance of myASn users might be not able to access the myasn system, not receive or receive bogus alarms etc beginning from 4pm today until Monday 10am Amsterdam time? That should be enough for me to make the updates and test stuff. Otherwise it will take really extra long amount of time to get a whole second copy of myasn on diemen test it and then update...... Alexis

2 1