April 2007 - Ris-int - mailman.ripe.net

perfect notice
by TINA TAHIR 24 Apr '07

24 Apr '07

The world has gone wireless and Mobile Airwaves (mbwc) is in the right place in the right time with a Red Hot Product! We are waiting for Financial Results to be announced by the Mobile Airwaves any day. With all the New Contracts they have acquired we are awaiting Record Earnings! mbwc is currently under priced at around 3 cents. With the Mobile Airwaves being so Tightly held we expecting the inlux of buying to Push the price off the charts! Get in on this Breakout Winner Early!

1 0

AS3.5 received as AS_TRANS from 1 RIS peer
by Rene Wilhelm 11 Apr '07

11 Apr '07

Following Surfnet's announcement of their as3.5 beacon to the nanog list, I had a quick look at RIS. (see below) For 93 peers the transition mechanism succeeds, the route collectors succesfully recreate a 4-byte AS path with 4-byte origin ASN. However, for 1 peer the RRC01 collector reports AS_TRANS as origin. This suggests the supposed transitive NEW_AS_PATH attribute was lost either in the peer or in one of its upstreams. BTW, has the APNIC 4-byte asn beacon been switched off? RISwhois only 'sees' two IPv4 prefixes with 4-byte origin ASNs: dog [~]; whois -h riswhois dump |grep '^[0-9]*\.[0-9]' 3.7 84.205.88.0/24 74 3.5 145.125.0.0/20 93 The RIS beacon, AS3.7, has somewhat less visibility than the route inserted by Surfnet (seen by 74 instead of 93 peers). -- Rene $ whois -h riswhois 145.125/20 % For more information visit http://www.ripe.net/ris/riswhois.html route: 145.125.0.0/20 origin: AS3.5 descr: SURFNET-NL SURFnet, The Netherlands lastupd-frst: 2007-03-29 11:54Z 80.81.192.8@rrc12 lastupd-last: 2007-04-10 15:27Z 198.32.160.179@rrc11 seen-at: rrc00,rrc01,rrc03,rrc04,rrc05,rrc06,rrc07,rrc10,rrc11,rrc12,rrc13,rrc14,rrc15 num-rispeers: 93 source: RISWHOIS route: 145.125.0.0/20 origin: AS23456 descr: AS_TRANS lastupd-frst: 2007-04-10 03:14Z 195.66.224.68@rrc01 lastupd-last: 2007-04-10 03:14Z 195.66.224.68@rrc01 seen-at: rrc01 num-rispeers: 1 source: RISWHOIS

3 5

Yahoo! Groups: You're invited! Join What_Buddha_Said today.
by What_Buddha_Said moderator 04 Apr '07

04 Apr '07

early_dhamma has invited you to join What_Buddha_Said [http://groups.yahoo.com/group/What_Buddha_Said/] on Yahoo! Groups, the best way to discover and share information and advice with others. All for free. A personal invitation from early_dhamma: Calm & Insight leads to Freedom & Bliss! This Noble 8-Fold Way makes Deathless... This Ease is Peace... Friendship is Greatest & You are Welcome! Bhikkhu Samahita, Ceylon ;-) See for yourself why millions of people are members of Yahoo! Groups. But hurry. This invitation expires in 30 days. Join this group: http://groups.yahoo.com/i?i=YNCJnoZRkGYw82NKkBQO0IkhIkY&e=ris-int%40ripe%2E… ------------------------------------------------------------------------ Yahoo! Groups is a free service that allows you to stay in touch with friends and family or meet new people who share your interests. Yahoo! Groups values your privacy. It is a violation of our service rules for Groups members to abuse this invitation feature. If you feel this has happened, please notify us: http://help.yahoo.com/help/us/groups/abuse/index.html You may also change your email preferences to stop receiving group invitations in the future. To do so, please go here: http://groups.yahoo.com/s?tag=qeGz9ML5h62ujOKmADgIjVbQHUPetywamZcK04bWn9-Qa… Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/

1 0

Re: [ris-int] how to get the next hop from ris raw data
by Rene Wilhelm 04 Apr '07

04 Apr '07

> Yes. The two next-hops are the BGP next-hop and the link-local next-hop, > as specified by RFC 2545 section 3: > > The value of the Length of Next Hop Network Address field on a > MP_REACH_NLRI attribute shall be set to 16, when only a global > address is present, or 32 if a link-local address is also included in > the Next Hop field. > The link-local address shall be included in the Next Hop field if and > only if the BGP speaker shares a common subnet with the entity > identified by the global IPv6 address carried in the Network Address > of Next Hop field and the peer the route is being advertised to. ok, got that, thanks! But next question is how this applies to IPv4. The bgpdump.c code features same constructs for AFI_IP and AFI_IP6. e.g. printf("(IPv4 Unicast)\n"); printf("NEXT_HOP: %s\n",inet_ntoa(attr->mp_info->announce[AFI_IP][SAFI_UNICAST]->nexthop.v4_addr)); if (attr->mp_info->announce[AFI_IP][SAFI_UNICAST]->nexthop_len==32) printf("NEXT_HOP: %s\n",inet_ntoa(attr->mp_info->announce[AFI_IP][SAFI_UNICAST]->nexthop_local.v4_addr)); is it ever possible to get nexthop_len==32 in this case ??? or did the authors of bgpdump.c just liked typing? :) Cheers, -- Rene

2 1

how to get the next hop from ris raw data
by Rene Wilhelm 04 Apr '07

04 Apr '07

Hi Lorenzo, Erik, I have to parse RIS raw data (in C) for a SG project. Bgpdump.c sort of shows how to do this, but I don't quite understand what's happening with next hop in the show_attr function: if (attr->mp_info->announce[AFI_IP6][SAFI_UNICAST]) { printf("(IPv6 Unicast)\n"); printf("NEXT_HOP: %s\n",inet_ntop(AF_INET6,&attr->mp_info->announce[AFI_IP6][SAFI_UNICAST]->nexthop.v6_addr,buf,128)); if (attr->mp_info->announce[AFI_IP6][SAFI_UNICAST]->nexthop_len==32) printf("NEXT_HOP: %s\n",inet_ntop(AF_INET6,&attr->mp_info->announce[AFI_IP6][SAFI_UNICAST]->nexthop_local.v6_addr,buf,128)); } (and the same for IPv4 unicast) What is this special case where ... nexthop_len==32 ? If I read this piece of C correctly, it would result in two next hop addresses being printed ????? Can one of you explain? Thanks, -- Rene

2 1

Re: Update to RIS raw data format for 4-byte ASNs
by Rene Wilhelm 02 Apr '07

02 Apr '07

Hi Erik, I didn't follow any of the discussions on the new MRT format, as I (naively) thought it would just be minor update for the longer AS numbers. But after reading your recent mails and having started work on importing RIS raw in a SG project, I see there's a fundamental change (at least for RIB dumps): in the old format, a call to bgpdump_read_next would return information on one and only one entry of the routing table. In the new format, a call to bgpdump_read_next returns a whole block of entries; for the latest rrc03 bview, anything between 1 and 35 at a time. To me it looks strange, seems to make programmer's life needlessly more complicated. Now one not only has to loop over all bgpdump_read_next records, but also loop over all entries in each "record". Programs which worked with old raw data will need major revision; and those which need to work with both old and new format will look ugly, a different paradigm for processing old and new data. Do you have any idea of the reasons behind this big change? Cheers, -- Rene > Dear Colleagues, > > This is an update concerning 4-byte Autonomous System Numbers (ASNs). > > An IETF draft has been released describing a new version of the MRT > format, used for RIS raw data. We have published a new version of > libbgpdump to support this, which can be downloaded from: > http://www.ris.ripe.net/source/ > > There is at this stage no set date on which 4-byte ASNs will appear in > the RIS. The current raw data does not use the new format. > > Details of the changes to RIS for 4-byte ASNs, including more information > on the new raw data format, can be found at: > http://www.ripe.net/projects/ris/docs/asn.html > > If you have any questions, please send an e-mail to <ris(a)ripe.net>. > > Regards, > > Erik Romijn > Information Services Department > RIPE NCC

3 4