May 2006 - Ris-int - mailman.ripe.net

succeed ruby
by Lazarus Strong 24 May '06

24 May '06

1 0

Re: test VALLtUvM
by Othello Nyland 22 May '06

22 May '06

Hi, M E R / D / A S O M ^ V / A G R A X ^ N A X L E V / T R A P R O Z ^ C C / A L / S V A L / U M A M B / E N http://www.mitakasiwobeans.com before they went on, stole in and kindheartedly put the keys back on his belt. That will save him some of the trouble he is in for, said Mr. Baggins to himself. He wasnt a bad fellow, and quite decent to the prisoners. It will puzzle them all too. They will think we had a very strong magic to pass through all those locked doors and disappear.

1 0

BancorpSouth's Online Access website has been upgraded
by BancorpSouth 17 May '06

17 May '06

1 0

[arife@ripe.net: [ris-int] RIS meeting minutes]
by arife＠ripe.net 16 May '06

16 May '06

Hi all, After having meeting with Andrei, I updated RIS ToDo list. http://iii/twiki/bin/view/SED/RIS#Todo Feel free to update it if there is anything missing. Arife ----- Forwarded message from Arife Vural <arife(a)ripe.net> ----- From: Arife Vural <arife(a)ripe.net> To: ris-int(a)ripe.net, Francesco Vivoli <fvivoli(a)ripe.net>, Andrei Robachevsky <andrei(a)ripe.net> Subject: [ris-int] RIS meeting minutes Date: Thu, 13 Apr 2006 11:52:41 +0200 Cc: Vasco Asturiano <vasco(a)ripe.net>, Trudy Prins <trudy(a)ripe.net> Attendees: James, Arife, Henk, Lorenzo, Francesco 1. Everyone agrees it's a good idea to have RIS data distributed over the Internet. This needs to be discuss with Andrei and get back to Simon Leinen. (AV) 2. Runing some scripts/tools Geoff has that uses RIS data. Arife will contact with Geoff to run them here. 3. RRC boxes in LACNIC region, we are happy to offer LACNIC people help how do it. There is not much point for RIS to have 7 RRCs in LACNIC area. Henk will contact with Milton. 4. RIS statistics, SED and Comms should look at how much of the statistics we produce are used. If there is no interest, we should stop spending CPU cycles. 5. Beacon request from The Hong Kong Polytechnic University, Lorenzo is in touch with them. He will let us know when do the configuration changes. 6. Having new RRC in NAP of Amreica is a good idea, as long as we get interested parities to peer with us. Josh Snowhorn, Terramark seems to be voluntered to do this. 7. Henk is voluntered to do RIS/TTM presentation in DE-CIX technical meeting. 8. Load on AMS-IX RRC is getting quite high with the number of peers. We should check our budget and get a new box, and share the load between two boxes. Any comments are welcome. -- Arife Vural SED, RIPE NCC

2 1

[arife@ripe.net: [Membros] ANNOUNCEMENT: The RIS Project's Remote Route Collector is online at Sao Paulo Internet Exchange.]
by arife＠ripe.net 15 May '06

15 May '06

Hi Milton, It has been a long time, I hope you're doing OK. After we sent the announcement, we did not get so many peering request with RIS. Do you think you could help us to get more peers at Sao Paulo. What about forwarding this e-mail to members mailling list with few lines of Portugees or Spanish explanation? Do you think it will help? BTW, I think Henk got back to you about the installation of RRC in your region. If you need any help from us, please do not hesitate to contact with us. Regards. Arife ----- Forwarded message from Arife Vural <arife(a)ripe.net> ----- From: Arife Vural <arife(a)ripe.net> To: membros(a)sp.ptt.br, ris-users(a)ripe.net Subject: [Membros] ANNOUNCEMENT: The RIS Project's Remote Route Collector is online at Sao Paulo Internet Exchange. Date: Wed, 4 Jan 2006 13:20:39 +0100 [Apologies for duplicate e-mails] Dear All, The RIPE NCC is pleased to announce that the Routing Information Service (RIS) Project's first Remote Route Collector (RRC) in South America, RRC15, is online at Sao Paulo Internet Exchange Point and is now ready to peer with PTTMetro-SP members. RRC15 has been operational since Dec 2005 and is located at PTTMetro-SP, Sao Paulo. The RRC has an interface on the shared PTTMetro-SP network, running IPv4, and collects routing information from all exchange members willing to peer with us. Many thanks to Milton Kaoru Kashiwakura, Luciano Gomes and LACNIC for helping us with locating the RIS Remote Route Collector at PTTMetro-SP. Our details: ------------ Peering addresses: 200.219.130.23 Autonomous system: 12654 Our policy: http://www.ripe.net/projects/ris/docs/peering.html Peering requests: E-mail: rispeering(a)ripe.net Web form at URL: http://www.ris.ripe.net/cgi-bin/peerreg.cgi The RIS project, which started as a modest RIPE NCC project in 1999, has gradually grown to include over 400 IPv4 and IPv6 peers at 14 data collection points in Europe, Japan and North America. Our mission is to collect Border Gateway Protocol (BGP) routing information and make it available to the Internet community. This involves devising tools that can help ISPs debug problems over time without them being limited to using BGP, and providing RIS with raw data regarding the Internet's historical development. For more information about RIS, please see: http://www.ripe.net/ris/ For more information about RIS Tools, please see: http://www.ripe.net/projects/ris/tools/index.html Please send any comments to: ris(a)ripe.net. Best regards, Arife Vural RIPE NCC, Software Engineering Department _______________________________________________ Membros mailing list Membros(a)sp.ptt.br http://sp.ptt.br/mailman/listinfo/membros ----- End forwarded message ----- -- Arife Vural SED, RIPE NCC

1 0

- PayPal - Funds Frozen
by Paypal Inc. 13 May '06

13 May '06

1 0

ID: 92171 - PayPal funds were frozen
by Paypal Inc. 13 May '06

13 May '06

1 0

Implementation of HK university prepending work
by Lorenzo Colitti 04 May '06

04 May '06

Hi all, this morning I had a chat with James on our prepending setup and he seemed to think it was mostly sane. Unfortunately, there seems to be no way to implement what we need to do without causing session resets towards the affected peers (9 in all) when we reconfigure the RRCs. Since Arife is away for a few weeks and there doesn't seem to be someone to talk to in SED about this, I will be implementing the prepending setup myself. This is a bit tricky, so I wrote a script to do it. (I'm just debugging the script now.) What I plan to do is: Today: - Finish debugging script and test on an inactive peer - Find our peers' email addresses (not as easy as it seems) - Tell our peers that we will be performing the experiments - Tell ris-users that those 9 BGP sessions will be reset tomorrow Tomorrow: - Configure RRCs (this resets the 9 sessions) Saturday and afterwards: - Perform experiments Comments? Cheers, Lorenzo -- Lorenzo Colitti lorenzo(a)ripe.net Network Engineer +31-20-5354471 RIPE NCC www.ripe.net

2 1

Re: AMBtcEN news
by Ondrej Hamel 02 May '06

02 May '06

Hi, C V P X A L V I I r a m e A A A o n b v L L G z a i i I I R a x e t U S A c n ra M http://www.kvoratizalopan.com mutton again tomorrow, said one of the trolls. Never a blinking bit of manflesh have we had for long enough, said a second. What the ell William was a-thinkin of to bring us into these parts at all, beats me and the drink runnin short, whats more, he said jogging the elbow of William, who was taking a pull at his jug. William choked. Shut yer mouth! he said as soon as he could.

1 0

Fixed config file
by Lorenzo Colitti 02 May '06

02 May '06

Hi James, here is the fixed bgpd config with the route-map. This one should have the proper community values... Cheers, Lorenzo -- Lorenzo Colitti lorenzo(a)ripe.net Network Engineer +31-20-5354471 RIPE NCC www.ripe.net ! hostname bgpd password zebra enable password zebra ! router bgp 12654 neighbor 194.146.105.1 remote-as 12654 neighbor 194.146.105.1 next-hop-self neighbor 194.146.105.1 allowas-in ! neighbor 194.68.123.143 remote-as 16150 neighbor 194.68.123.143 description Router as16150 neighbor 194.68.123.143 send-community neighbor 194.68.123.143 route-map as11-out out ! neighbor 194.68.123.109 remote-as 5400 neighbor 194.68.123.109 description Router as5400 neighbor 194.68.123.109 send-community neighbor 194.68.123.109 route-map as21-out out ! neighbor 194.68.123.141 remote-as 13237 neighbor 194.68.123.141 description Router as13237 neighbor 194.68.123.141 send-community neighbor 194.68.123.141 route-map as31-out out ! ip community-list 10 permit 12654:100 ip community-list 11 permit 12654:101 ip community-list 12 permit 12654:102 ip community-list 13 permit 12654:103 ip community-list 14 permit 12654:104 ip community-list 15 permit 12654:105 ip community-list 16 permit 12654:106 ip community-list 17 permit 12654:107 ip community-list 18 permit 12654:108 ip community-list 19 permit 12654:109 ip community-list 41 deny 12654:199 ip community-list 41 permit ! route-map as11-out permit 10 match community 11 set as-path prepend 12654 ! route-map as11-out permit 15 match community 12 set as-path prepend 12654 12654 ! route-map as11-out permit 20 match community 13 set as-path prepend 12654 12654 12654 ! route-map as11-out permit 25 match community 14 set as-path prepend 12654 12654 12654 12654 ! route-map as11-out permit 30 match community 15 set as-path prepend 12654 12654 12654 12654 12654 ! route-map as11-out permit 35 match community 16 set as-path prepend 12654 12654 12654 12654 12654 12654 ! route-map as11-out permit 40 match community 17 set as-path prepend 12654 12654 12654 12654 12654 12654 12654 ! route-map as11-out permit 45 match community 18 set as-path prepend 12654 12654 12654 12654 12654 12654 12654 12654 ! route-map as11-out permit 50 match community 19 set as-path prepend 12654 12654 12654 12654 12654 12654 12654 12654 12654 ! route-map as11-out permit 55 match community 10 set as-path prepend 12654 12654 12654 12654 12654 12654 12654 12654 12654 12654 ! route-map as11-out permit 90 match community 41 ! ip community-list 20 permit 12654:200 ip community-list 21 permit 12654:201 ip community-list 22 permit 12654:202 ip community-list 23 permit 12654:203 ip community-list 24 permit 12654:204 ip community-list 25 permit 12654:205 ip community-list 26 permit 12654:206 ip community-list 27 permit 12654:207 ip community-list 28 permit 12654:208 ip community-list 29 permit 12654:209 ip community-list 42 deny 12654:299 ip community-list 42 permit ! route-map as21-out permit 10 match community 21 set as-path prepend 12654 ! route-map as21-out permit 15 match community 22 set as-path prepend 12654 12654 ! route-map as21-out permit 20 match community 23 set as-path prepend 12654 12654 12654 ! route-map as21-out permit 25 match community 24 set as-path prepend 12654 12654 12654 12654 ! route-map as21-out permit 30 match community 25 set as-path prepend 12654 12654 12654 12654 12654 ! route-map as21-out permit 35 match community 26 set as-path prepend 12654 12654 12654 12654 12654 12654 ! route-map as21-out permit 40 match community 27 set as-path prepend 12654 12654 12654 12654 12654 12654 12654 ! route-map as21-out permit 45 match community 28 set as-path prepend 12654 12654 12654 12654 12654 12654 12654 12654 ! route-map as21-out permit 50 match community 29 set as-path prepend 12654 12654 12654 12654 12654 12654 12654 12654 12654 ! route-map as21-out permit 55 match community 20 set as-path prepend 12654 12654 12654 12654 12654 12654 12654 12654 12654 12654 ! route-map as21-out permit 90 match community 42 ! ! ip community-list 30 permit 12654:300 ip community-list 31 permit 12654:301 ip community-list 32 permit 12654:302 ip community-list 33 permit 12654:303 ip community-list 34 permit 12654:304 ip community-list 35 permit 12654:305 ip community-list 36 permit 12654:306 ip community-list 37 permit 12654:307 ip community-list 38 permit 12654:308 ip community-list 39 permit 12654:309 ip community-list 43 deny 12654:399 ip community-list 43 permit ! route-map as31-out permit 10 match community 31 set as-path prepend 12654 ! route-map as31-out permit 15 match community 32 set as-path prepend 12654 12654 ! route-map as31-out permit 20 match community 33 set as-path prepend 12654 12654 12654 ! route-map as31-out permit 25 match community 34 set as-path prepend 12654 12654 12654 12654 ! route-map as31-out permit 30 match community 35 set as-path prepend 12654 12654 12654 12654 12654 ! route-map as31-out permit 35 match community 36 set as-path prepend 12654 12654 12654 12654 12654 12654 ! route-map as31-out permit 40 match community 37 set as-path prepend 12654 12654 12654 12654 12654 12654 12654 ! route-map as31-out permit 45 match community 38 set as-path prepend 12654 12654 12654 12654 12654 12654 12654 12654 ! route-map as31-out permit 50 match community 39 set as-path prepend 12654 12654 12654 12654 12654 12654 12654 12654 12654 ! route-map as31-out permit 55 match community 30 set as-path prepend 12654 12654 12654 12654 12654 12654 12654 12654 12654 12654 ! route-map as31-out permit 90 match community 43 ! ! log file /var/log/zebra/bgpd.log ! debug bgp debug bgp events debug bgp filters debug bgp fsm debug bgp keepalives debug bgp updates !

1 0