From eromijn at ripe.net Mon Apr 2 10:12:01 2007 From: eromijn at ripe.net (Erik Romijn) Date: Mon, 2 Apr 2007 10:12:01 +0200 Subject: [ris-int] Re: Update to RIS raw data format for 4-byte ASNs In-Reply-To: <460D7CC0.6030606@dia.uniroma3.it> References: <20070315163736.GN5323@ripe.net> <20070328211043.997452F583@herring.ripe.net> <20070329083757.GU22296@ripe.net> <460D7CC0.6030606@dia.uniroma3.it> Message-ID: <20070402081200.GH16168@ripe.net> [ I can't cc to sg at ripe.net, unless someone approves it in mailman ] On Fri, Mar 30, 2007 at 02:10:24PM -0700, Lorenzo Colitti wrote: > as a user of libbgpdump, I'm curious: does this change break existing > users of the MRT format, even if they don't care about 32-bit ASNs? Yes for RIB dumps. For update dumps, you just won't see any updates from a 4-byte AS peer. For RIB dumps, the entire format changed, so you won't see anything with older versions. > sure you don't want people who download the RIS raw data and try to > parse it with route_btoa or old versions of libbgpdump to stop being > able to use the raw data files, right? I prefer not to, but IMHO, it was the best option here. The other option could be to dump only route entries with a 4-byte AS in the new format. But that would lead to a very very nasty quagga patch and people might be missing routes without knowing. > If this stuff did break, were the users warned with an appropriate email > to the ris-users mailing list? I didn't see one, but admittedly I only > briefly scanned the archives... Yes. One on Jan 11, one on Mar 15 with details of the new format, one on Mar 22 (also sent to routing-wg) to say that changes will be applied on Mar 27. cheers, -- Erik Romijn RIPE NCC jr. software engineer http://www.ripe.net/ Information Services dept. From wilhelm at ripe.net Tue Apr 3 18:33:36 2007 From: wilhelm at ripe.net (Rene Wilhelm) Date: Tue, 03 Apr 2007 18:33:36 +0200 Subject: [ris-int] how to get the next hop from ris raw data In-Reply-To: Message from Lorenzo Colitti of "Fri, 30 Mar 2007 14:10:24 PDT." <460D7CC0.6030606@dia.uniroma3.it> Message-ID: <20070403163336.90F6B2F583@herring.ripe.net> 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 From colitti at dia.uniroma3.it Wed Apr 4 03:15:37 2007 From: colitti at dia.uniroma3.it (Lorenzo Colitti) Date: Tue, 03 Apr 2007 18:15:37 -0700 Subject: [ris-int] how to get the next hop from ris raw data In-Reply-To: <20070403163336.90F6B2F583@herring.ripe.net> References: <20070403163336.90F6B2F583@herring.ripe.net> Message-ID: <4612FC39.80606@dia.uniroma3.it> Rene Wilhelm wrote: > 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 ????? 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. Cheers, Lorenzo -- Lorenzo Colitti http://www.colitti.com/lorenzo/ From wilhelm at ripe.net Wed Apr 4 04:42:56 2007 From: wilhelm at ripe.net (Rene Wilhelm) Date: Wed, 04 Apr 2007 04:42:56 +0200 Subject: [ris-int] how to get the next hop from ris raw data In-Reply-To: Message from Lorenzo Colitti of "Tue, 03 Apr 2007 18:15:37 PDT." <4612FC39.80606@dia.uniroma3.it> Message-ID: <20070404024256.2271F2F583@herring.ripe.net> > 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 From colitti at dia.uniroma3.it Wed Apr 4 06:20:47 2007 From: colitti at dia.uniroma3.it (Lorenzo Colitti) Date: Tue, 03 Apr 2007 21:20:47 -0700 Subject: [ris-int] how to get the next hop from ris raw data In-Reply-To: <20070404024256.2271F2F583@herring.ripe.net> References: <20070404024256.2271F2F583@herring.ripe.net> Message-ID: <4613279F.1010208@dia.uniroma3.it> Rene Wilhelm wrote: > 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? :) I think the authors of bgpdump.c just liked cut and paste :-) Hello from sunny California! Cheers, Lorenzo -- Lorenzo Colitti http://www.colitti.com/lorenzo/ From What_Buddha_Said-owner at yahoogroups.com Wed Apr 4 08:27:46 2007 From: What_Buddha_Said-owner at yahoogroups.com (What_Buddha_Said moderator) Date: 4 Apr 2007 06:27:46 -0000 Subject: [ris-int] Yahoo! Groups: You're invited! Join What_Buddha_Said today. Message-ID: <1175668066.1105.17726.w109@yahoogroups.com> 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%2Enet ------------------------------------------------------------------------ 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-Qay1X_C7p1L8G-Oha9wjUevpVDPjU Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bg_lblue_top.gif Type: image/gif Size: 50 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bg_lblue_bottom.gif Type: image/gif Size: 50 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bg_lblue_left.gif Type: image/gif Size: 54 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bg_lblue_right.gif Type: image/gif Size: 54 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cr_m_lblue_nw.gif Type: image/gif Size: 52 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cr_m_lblue_ne.gif Type: image/gif Size: 52 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cr_m_lblue_sw.gif Type: image/gif Size: 52 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cr_m_lblue_se.gif Type: image/gif Size: 52 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bg_blue_left.gif Type: image/gif Size: 51 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bg_blue_right.gif Type: image/gif Size: 51 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bg_blue_bottom.gif Type: image/gif Size: 50 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cr_blue_sw.gif Type: image/gif Size: 90 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cr_blue_se.gif Type: image/gif Size: 90 bytes Desc: not available URL: From wilhelm at ripe.net Tue Apr 10 22:20:23 2007 From: wilhelm at ripe.net (Rene Wilhelm) Date: Tue, 10 Apr 2007 22:20:23 +0200 Subject: [ris-int] AS3.5 received as AS_TRANS from 1 RIS peer Message-ID: <20070410202024.2C0F72F59E@herring.ripe.net> 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 at rrc12 lastupd-last: 2007-04-10 15:27Z 198.32.160.179 at 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 at rrc01 lastupd-last: 2007-04-10 03:14Z 195.66.224.68 at rrc01 seen-at: rrc01 num-rispeers: 1 source: RISWHOIS From daniel.karrenberg at ripe.net Wed Apr 11 07:53:38 2007 From: daniel.karrenberg at ripe.net (Daniel Karrenberg) Date: Wed, 11 Apr 2007 07:53:38 +0200 Subject: [ris-int] AS3.5 received as AS_TRANS from 1 RIS peer In-Reply-To: <20070410202024.2C0F72F59E@herring.ripe.net> References: <20070410202024.2C0F72F59E@herring.ripe.net> Message-ID: <20070411055337.GD1868@reiftel.ripe.net> Suggestion: contact the peer where AS_TRANS appears and try to trace this problem back. Write this up a little more formally and send it tot the routing-wg and nanog. Present at routing-wg @ talinn? Daniel From eromijn at ripe.net Wed Apr 11 08:57:58 2007 From: eromijn at ripe.net (Erik Romijn) Date: Wed, 11 Apr 2007 08:57:58 +0200 Subject: [ris-int] AS3.5 received as AS_TRANS from 1 RIS peer In-Reply-To: <20070411055337.GD1868@reiftel.ripe.net> References: <20070410202024.2C0F72F59E@herring.ripe.net> <20070411055337.GD1868@reiftel.ripe.net> Message-ID: On Apr 11, 2007, at 7:53 AM, Daniel Karrenberg wrote: > Suggestion: contact the peer where AS_TRANS appears and try to trace > this problem back. Done already last week. They forwarded it to one of their upstreams that do some strange AS path mangling that may be related. Didn't get more from them yet, will poke them. cheers, -- Erik Romijn RIPE NCC jr. software engineer http://www.ripe.net/ Information Services dept. From eromijn at ripe.net Wed Apr 11 09:02:09 2007 From: eromijn at ripe.net (Erik Romijn) Date: Wed, 11 Apr 2007 09:02:09 +0200 Subject: [ris-int] AS3.5 received as AS_TRANS from 1 RIS peer In-Reply-To: <20070410202024.2C0F72F59E@herring.ripe.net> References: <20070410202024.2C0F72F59E@herring.ripe.net> Message-ID: <01561B74-C103-48A0-BB8E-C9B4403925D8@ripe.net> On Apr 10, 2007, at 10:20 PM, Rene Wilhelm wrote: > > BTW, has the APNIC 4-byte asn beacon been switched off? > RISwhois only 'sees' two IPv4 prefixes with 4-byte origin ASNs: So do the looking glasses. This did work before, so I assume they switched it off. cheers, -- Erik Romijn RIPE NCC jr. software engineer http://www.ripe.net/ Information Services dept. From eromijn at ripe.net Wed Apr 11 13:38:18 2007 From: eromijn at ripe.net (Erik Romijn) Date: Wed, 11 Apr 2007 13:38:18 +0200 Subject: [ris-int] Re: AS3.5 received as AS_TRANS from 1 RIS peer In-Reply-To: <20070410202024.2C0F72F59E@herring.ripe.net> References: <20070410202024.2C0F72F59E@herring.ripe.net> Message-ID: <20070411113817.GG16168@ripe.net> On Tue, Apr 10, 2007 at 10:20:23PM +0200, Rene Wilhelm wrote: > The RIS beacon, AS3.7, has somewhat less visibility than the > route inserted by Surfnet (seen by 74 instead of 93 peers). This -might- be because peers filter on 12654$ for routes from rrc03. And therefore don't accept "12654 23456". We didn't send an announcement about this to the AMS-IX filter-updates list. RR data is up-to-date ofcourse. cheers, -- Erik Romijn RIPE NCC jr. software engineer http://www.ripe.net/ Information Services dept. From wilhelm at ripe.net Wed Apr 11 14:51:00 2007 From: wilhelm at ripe.net (Rene Wilhelm) Date: Wed, 11 Apr 2007 14:51:00 +0200 (CEST) Subject: [ris-int] Re: AS3.5 received as AS_TRANS from 1 RIS peer In-Reply-To: <20070411113817.GG16168@ripe.net> References: <20070410202024.2C0F72F59E@herring.ripe.net> <20070411113817.GG16168@ripe.net> Message-ID: On Wed, 11 Apr 2007, Erik Romijn wrote: > On Tue, Apr 10, 2007 at 10:20:23PM +0200, Rene Wilhelm wrote: > > The RIS beacon, AS3.7, has somewhat less visibility than the > > route inserted by Surfnet (seen by 74 instead of 93 peers). > > This -might- be because peers filter on 12654$ for routes from rrc03. > And therefore don't accept "12654 23456". Understood. It was just an observation, not a complaint. RIS started with 'collecting only' and peers are under no obligation to forward announcements received from the route collectors. Still, 74 peers isn't bad at all. > We didn't send an announcement > about this to the AMS-IX filter-updates list. RR data is up-to-date > ofcourse. -- Rene From dullespunished at strabag.ru Tue Apr 24 13:50:53 2007 From: dullespunished at strabag.ru (TINA TAHIR) Date: Tue, 24 Apr 2007 14:10:53 +0180 Subject: [ris-int] perfect notice Message-ID: <01c7867a$5edafb10$6c822ecf@dullespunished> 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!