June 2005 - Ris-int - mailman.ripe.net

alarm create error
by Andrew Partan 20 Jun '05

20 Jun '05

I was creating alarms for AS 3944 and got this: System error error: DBI connect('myasn;host=193.0.0.210;port=3306','myasn',...) failed: Can't connect to MySQL server on '193.0.0.210' (111) at /usr/local/lib/perl5/site_perl/5.8.0/Alzabo/Driver/MySQL.pm line 188 Stack: [/usr/local/perl5.8.0/lib/perl5/5.8.0/Carp.pm:191] [/usr/local/lib/perl5/site_perl/5.8.0/mach/DBI.pm:596] [/usr/local/lib/perl5/site_perl/5.8.0/mach/DBI.pm:646] [/usr/local/lib/perl5/site_perl/5.8.0/Alzabo/Driver/MySQL.pm:188] [/usr/local/lib/perl5/site_perl/5.8.0/Alzabo/Driver/MySQL.pm:35] [/usr/local/lib/perl5/site_perl/5.8.0/Alzabo/Runtime/Schema.pm:122] [/home/risops/myasn/lib/RIPE/NCC/myASn/Data.pm:134] [/export/risfsa13/www/ris/myasn/newalarm.html:146] [/export/risfsa13/www/ris/myasn/autohandler.html:69] [/export/risfsa13/www/ris/myasn/syshandler:29] code stack: I hit the back button & redid the create & it worked just fine the 2nd time. --asp

1 0

Re: R: RIPE-NCC Testbox Order
by Henk Uijterwaal 20 Jun '05

20 Jun '05

Hi, In a related discussion At 16:29 06/06/2005, Stefano Pasquini wrote: [...] >Also the RIS project for us is a lot interesting and would want to >participate, do you have some suggestions for this service? >Many thanks for your support. This is the Vatican city Internet office, obviously located in Rome. Perhaps we can set up peering with them in Milano. Can you contact him to sort this out? Henk ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ Look here junior, don't you be so happy. And for Heaven's sake, don't you be so sad. (Tom Verlaine)

2 2

Time Out 07.07.2005:09:00 - 14.07.2005:18:00
by Arife Vural 17 Jun '05

17 Jun '05

<<<DO NOT CHANGE THE TIME/DATE/TYPE OF TIMEOUT HERE>>> <<<THAT WON'T BE REFLECTED IN CTIME. IF YOU WANT TO>>> <<<MAKE SUCH CHANGES, CANCEL THE STT AND START OVER>>> Dear Colleagues, Please note the following time out: Who: Arife Vural First Day: 07.07.2005 Starts at: 09:00 Last Day: 14.07.2005 Ends at: 18:00 Working days: [6.00] Type: VAC Reason: [Turkey] If you have any further questions, please do not hesitate to contact me. Thank you, Arife Vural

1 0

Re: RRC13 & RRC14 announcements
by Rene Wilhelm 15 Jun '05

15 Jun '05

Hi Arife, Announcing to IX lists is one thing, but we also *used* to announce to the public at large! A news flash on RIPE NCC homepage, an item in the RIS news page, a mail to ris-users list etc. That hasn't happened since RRC12 last year. The RIS news at http://www.ripe.net/projects/ris/news.html mentions RRC08 leaving MAE WEST in september last year, but no word on it returning as RRC14 at PAIX. -- Rene > We announced RRC14, we sent the e-mail indiviually all the peers. > Since PAIX does not have IX maillinglist. At that time, when we discussed > to send it to NANOG mailling list but ISC guys somehow did not like > the idea I do not know remember the reason now. > > We did not announce RRC13 yet. I sent the announcement to Russian > guy, he would translate and forward to IX maillinglist, but I have not > heard from him. I will ping him. > > Arife

4 4

Draft announcement to nanog
by Lorenzo Colitti 15 Jun '05

15 Jun '05

Hi Henk, here's the announcement I was thinking of sending to nanog. What do you think? Cheers, Lorenzo ==========================8<-------------------------- From: lorenzo(a)ripe.net To: routing-wg(a)ripe.net, nanog(a)merit.edu Cc: henk(a)ripe.net, compunet(a)dia.uniroma3.it Hi, as part of our AS-set stuffing experiments (described, including links to in-depth information, in [1]), we will be announcing unusually large AS-sets on Thursday 16 June. The prefixes involved will be 84.205.73.0/24 and 84.205.89.0/24, both originating in AS12654. The AS-sets will consist of AS12654 repeated n times, thus, the paths will look like 12654 {12654, 12654, ..., 12654}. No other AS numbers will be used. The values of n we will use are 25, 50, 75 and 100. The announcements are designed to measure the effectiveness of our techniques in today's Internet with today's IPv4 operational practices. This is *not* a test to see if routers will fall over: we have successfully tested longer AS-sets in the lab on both Cisco and Juniper, and longer AS-paths and AS-sets have been observed in the wild [2,3]. See [1] for more information on the safety of these announcements. The proposed schedule is as follows: 84.205.73.0/24 84.205.89.0/24 14:00 UTC: 25-element AS-set 50-element AS-set 14:30 UTC: withdrawal withdrawal 16:00 UTC: 75-element AS-set 100-element AS-set 16:30 UTC: withdrawal withdrawal If anyone should see a problem during the announcements, please contact me and I will take immediate action. Regards, Lorenzo [1] http://www.merit.edu/mail.archives/nanog/2005-06/msg00210.html [2] http://www.ripe.net/projects/ris/Talks/0101_RIPE38_AA/sld003.html [3] http://www.ripe.net/maillists/ncc-archives/ris-users/2002/msg00044.html -- lorenzo(a)ripe.net colitti(a)dia.uniroma3.it www.ripe.net www.dia.uniroma3.it/~compunet RIPE NCC Roma Tre Computer Networks research group

2 1

Announcing new AS-set stuffing experiments?
by Lorenzo Colitti 13 Jun '05

13 Jun '05

Hi ris-int, since nanog's reaction to my post explaining our AS-set stuffing techniques generated fewer flames than expected, I was thinking of announcing AS-set stuffing experiments over IPv4 today or tomorrow. I would start with an experiment to determine how far large AS-sets penetrate into the Internet. Idea: announce progressively longer AS-sets containing only AS 12654 (so AS-paths like 12654 {n * 12654}) and see if the large AS-sets survive all the way to the RRCs or not. This would: a) provide results we need b) eliminate some opposition by showing that large AS-sets are safe c) not irritate people because we're only using our own ASn The values of n would be 5, 10, 20, 50, 75, 100. This is well below the safety limit we have seen with Ciscos (254). Once that is done, I would announce other experiments using other people's ASes, saying that people can opt-out if they don't want their AS to appear. Thoughts? Cheers, Lorenzo -- --------------------------------------------------------- Lorenzo Colitti Ph.D student Computer Networks research group Roma Tre University colitti(a)dia.uniroma3.it +39-0655173215 ---------------------------------------------------------

1 0

Re: [ris-int] Re: RRC13 & RRC14 announcements
by James Aldridge 10 Jun '05

10 Jun '05

Arife Vural wrote: > We did not announce RRC13 yet. I sent the announcement to Russian > guy, he would translate and forward to IX maillinglist, but I have not > heard from him. I will ping him. Email list for the MCK-IX is <msk-ix(a)ripn.net>. They also have a route server there which Evgueni Kouskevitch offered a peering with (this was all happenning just before RIPE50 so things were somewhat busy on the OPS side). James

1 0

Re: RRC13 & RRC14 announcements
by Henk Uijterwaal 10 Jun '05

10 Jun '05

Shane, Arife, See below, sorry for the Dutch. Bottom line: Rene noticed that we never announced the existence of RRC13 and 14, and thus do not have any peering sessions there yet. In particular after all the trouble to get the Moscow RRC running, that seems like a waste of time. Matthew used to do these announcements in the past, but he left. I guess I assumed that you'd do this, but then again I don't know if we ever agreed this. I'm happy to do this though. So, do you want to send an announcement or should we do this? Henk At 14:18 09/06/2005, Rene Wilhelm wrote: >Henk, > >Tijdens het werken aan ripe50 routing minutes vroeg ik me af of >RRC13 (moskou) en RRC14 (palo alto, former rrc08) ooit aangekondigd waren >aan de community. Matthew deed dat in het verleden. > >Zojuist heb ik even zitten rond kijken op www.ripe.net en voorzover ik kan >zien is er nooit iets gemeld over deze 2 route collectors. :( > >Het laatste news item over RIS in http://www.ripe.net/news/ >dateert van 20 july 2004, "announcing RRC12 / DE-CIX" > >http://www.ripe.net/projects/ris/news.html gaat ietsje verder maar heeft >ook niets over de RRC13/14, de laatste melding daar is van 30 sept 2004, >"BGPlay upgraded". > >In de ris-users lijst is de laatste RRC gerelateerde mail de aankondiging >van 1 september 2004, over de verhuizing van de RRC08/MAE-WEST. Hoewel >beloofd, is er nooit een follow up geweest waarin de activering van (nu) >RRC14 in PAIX werd aangekondigd. > >Tenslotte viel me op dat RRC13/Moskou tot nu toe geen enkele peering sessie >lijkt te hebben, alle ruwe data files op halfweg zijn (uncompressed) 0 bytes >lang. Toch wel zonde van alle inspanningen om die box aan de praat te >krijgen. > > >-- 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 ------------------------------------------------------------------------------ Look here junior, don't you be so happy. And for Heaven's sake, don't you be so sad. (Tom Verlaine)

2 1

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

09 Jun '05

Hi Arife, I understand it's a difficult issue; fortunately we're left with only 1 debogon prefix: whois -h riswhois -F -M 87/8 |grep 12654 12654 87.255.248.0/21 1 The other one, 87.192.0.0/16, is now announced by AS25441 and seen by 64 RIS peers. Perhaps all it takes to clear the bogus debogon is for a new owner to insert a fresh announcement? If you want to continue contacting every AS which according to the routing tables sees the debogon route, you could also check route-views' routers for info. For example, @oregon-ix: x27$ telnet route-views.oregon-ix.net [...] route-views.oregon-ix.net>sh ip bgp 87.255.248.0/21 BGP routing table entry for 87.255.248.0/21, version 60855137 Paths: (1 available, best #1, table Default-IP-Routing-Table) Not advertised to any peer 3277 6820 3246 5400 5400 3257 28747 12654 194.85.4.55 from 194.85.4.55 (194.85.4.55) Origin IGP, localpref 100, valid, external, best Community: 3277:6820 3277:65361 Only the "5400 3257 28747 12654" part is in common with RIS, the other ASNs are different. Cheers, -- Rene > Hi Mike, > > I'm chasing those guys who still think we announce that prefix. But I have > not got any useful info from them. Last, I contacted with AS9177, but I > have not got any reply back. > > I attached the e-mail that I got from Tiscali, it looks this route still > is hanging there because of a Cisco bug or maybe other vendor OS bugs. > I do not know what else I could do be honest ... > > Arife > > -- > > From: Alexander Koch <koch(a)tiscali.net> > To: Arife Vural <arife(a)ripe.net> > Subject: Re: Need a favor > Message-ID: <20050608120049.GA21021(a)shekinah.ip.tiscali.net> > References: <20050608120017.GC22290(a)ripe.net> > Mime-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > In-Reply-To: <20050608120017.GC22290(a)ripe.net> > Organization: Tiscali International Network B.V. > X-NCC-RegID: eu.nacnet > User-Agent: Mutt/1.5.9i > X-RIPE-Spam-Level: > X-RIPE-Spam-Tests: BAYES_00 > X-RIPE-Spam-Status: U 0.298951 / -2.6 > X-RIPE-Signature: f24e950eeaafece3eb369dee26ae860b > Status: RO > Content-Length: 1707 > Lines: 50 > > Hello Arife, > > what you see is probably comparable to IPv6 ghosts routes > where a /35 more specific route sticked in the routing table > long after it was theoretically withdrawn. > > We currently do not see the route from RealROOT, but then, > AS28747 was changed to AS 9009 two weeks ago or so. Also > seeing the AS path I believe you can safely assume AS5400 > (BT's backbone) is not seeing it either... your best bet > might be to contact bgp(a)sunrise.net and/or AS9177 directly. > > Does that help? > > Best regards, > Alexander > > On Wed, 8 June 2005 14:00:17 +0200, Arife Vural wrote: > > Hi Alexander, > > > > Part of De-bogonising project we were announcing 87/8. We stopped it > > for a while, but it's seen in routing tables. Be honest, I could not > > explain why this route was still in the routing tables even if we do > > not have any entries in our config file for that prefix. > > > > On rrc00, it's seen like that, > > > > rrc00> sh ip bgp 87.255.248.0/21 > > BGP routing table entry for 87.255.248.0/21 > > Paths: (1 available, best #1, table Default-IP-Routing-Table) > > Not advertised to any peer > > 9177 6730 5400 3257 28747 12654 > > 212.47.190.1 from 212.47.190.1 (213.193.66.42) > > Origin IGP, localpref 100, valid, external, best > > Last update: Wed Jun 8 10:20:46 2005 > > > > I contacted with AS28747, but could not get any reply back to check > > whether they get this prefix from us or not. > > > > I would like to ask you to check whether you get this prefix from AS28747. > > If so, not sure but resetting the session with AS28747 would make any help? > > > > Kind regards. > > > > Arife > > -- > Alexander Koch <koch(a)tiscali.net> / ako4-ripe > Tiscali Int., Peering Coordination > Phone +49 6103 916 480, Fax +49 6103 916 464 > > On Tue, Jun 07, 2005 at 10:13:17AM +0200, RIPE NCC Hostmaster wrote: > > Dear Colleagues, > > > > It's quiet in this ticket for quite a while, while on the Net it's not > > so quiet: the ranges are still (again?) announced and visible > > (in case you don't know): > > > > route: 87.255.248.0/21 > > origin: AS12654 > > descr: RIPE-NCC-RIS-AS RIPE NCC RIS Project. > > lastupd-frst: 2005-06-05 14:10Z 212.47.190.1@rrc00 > > lastupd-last: 2005-06-05 14:10Z 212.47.190.1@rrc00 > > seen-at: rrc00 > > num-rispeers: 1 > > source: RISWHOIS > > > > We are still curious when is it going to stop. > > > > > > -- > > Sincerely, > > > > Mike Petuschak > > RIPE NCC > > > > > > > > > Hi Arife, > > > > > > Thanks for the update. > > > > > > Today RISwhois only sees 1 (one) peer at rrc00 forwarding the > > > old debogon announcments from 87/8: > > > > > > route: 87.192.0.0/16 > > > origin: AS12654 > > > descr: RIPE-NCC-RIS-AS RIPE NCC RIS Project. > > > lastupd-frst: 2005-06-01 10:11Z 212.47.190.1@rrc00 > > > lastupd-last: 2005-06-01 10:11Z 212.47.190.1@rrc00 > > > seen-at: rrc00 > > > num-rispeers: 1 > > > source: RISWHOIS > > > > > > route: 87.255.248.0/21 > > > origin: AS12654 > > > descr: RIPE-NCC-RIS-AS RIPE NCC RIS Project. > > > lastupd-frst: 2005-06-01 10:11Z 212.47.190.1@rrc00 > > > lastupd-last: 2005-06-01 10:11Z 212.47.190.1@rrc00 > > > seen-at: rrc00 > > > num-rispeers: 1 > > > source: RISWHOIS > > > > > > > > > The last update is yesterday, 10:11 UTC (14:11 local time) > > > is that when you reset the session with AS28747? > > > > > > -- Rene

2 1

Re: updated libbgpdump
by Arife Vural 09 Jun '05

09 Jun '05

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

2 2