From ocl at gih.com Mon Feb 1 10:47:43 2010 From: ocl at gih.com (Olivier MJ Crepin-Leblond) Date: Mon, 01 Feb 2010 11:47:43 +0100 Subject: [IPv6crawler-wg] Fwd: Update - Week 26th Jan - 31st Jan 2010 Message-ID: <4B66B14F.9080501@gih.com> The send date was wrong, and I realise that this was probably caught in your respective/collective anti-spam traps. I hope this one reaches you. Kind regards, Olivier -------- Message original -------- Sujet: Update - Week 26th Jan - 31st Jan 2010 Date : Sun, 01 Feb 2009 16:27:39 +0100 De : Olivier MJ Crepin-Leblond Pour : IPv6crawler-wg at gih.com Hello everyone, just a quick update on last week's activities. The HP Proliant DL140 and DL360 server have both been sourced, built and supplied by Omer. * Dell DL 140 - Web Server - Dual Xeon Processors running at 3.4 GHz 2MB Level 2 Cache 800MHz front-side bus supporting Hyper-Threading Technology - 4Gb RAM - 2 x 1Tb SATA disks, running as a software RAID - 500W power supply * Dell DL360 - Crawler - Dual Intel Xeon 3.8 GHz/800MHz - 2MB L2 - 4Gb RAM - 2 x 340Gb hot-swappable SCSI disks running as a hardware RAID - Dual 500W power supply, hot swappable Thanks Omer! Both are now running Centos v 5.4 Pictures of the servers with Rex and Omer in the GIH office, are attached to this message, along with the CISCO 2811. The CISCO 2811 has now been installed by Rex and Alan in the Data Centre, and the servers will be installed in the forthcoming week. Our schedule has slipped slightly, since Rex and Alan from 2020media have gone on an IPv6 course a RIPE headquarters in Amsterdam on thursday and friday last week. However, this is fine because it will enable Rex and Alan to know the subtleties of IPv6. Also, we now already have an IPv6 prefix which will be our base for IPv6 addresses, and it is implemented in the router at: 2a00:19e8::1 - thanks Rex and Alan! [root at waikiki ocl]# traceroute 2a00:19e8::1 traceroute to 2a00:19e8::1 (2a00:19e8::1), 30 hops max, 40 byte packets 1 adsl-gw6.gih.co.uk (2001:470:1f09:92d::1) 3.970 ms 5.282 ms 5.263 ms 2 ocl999-1.tunnel.tserv5.lon1.ipv6.he.net (2001:470:1f08:92d::1) 49.776 ms 72.009 ms 71.994 ms 3 1g-4-6.core1.lon5.ipv6.he.net (2001:470:0:67::1) 72.791 ms 72.742 ms 73.999 ms 4 g1-1-1-t40-br3.ipv6.router.uk.clara.net (2001:7f8:4::20ea:1) 72.619 ms * * 5 ten1-0-0.t40-cr1.ipv6.router.uk.clara.net (2001:a88:0:1::119) 73.747 ms * * 6 g4-1-t40-br2.ipv6.router.uk.clara.net (2001:a88:0:1::d9) 79.980 ms 76.350 ms 75.836 ms 7 2a00:19e8::1 (2a00:19e8::1) 79.473 ms 35.184 ms 86.377 ms [root at waikiki ocl]# I have a conference call with Sameh and Moustafa on monday to update on progress. I've created accounts for everyone on the computers. I'll email you separately with your account details. Warm regards, -- Olivier MJ Cr?pin-Leblond, PhD http://www.gih.com/ocl.html -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 250120102476.jpg Type: image/jpeg Size: 998009 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 250120102477.jpg Type: image/jpeg Size: 975022 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 250120102475.jpg Type: image/jpeg Size: 767868 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 250120102465.jpg Type: image/jpeg Size: 939654 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 250120102466.jpg Type: image/jpeg Size: 863068 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 250120102463.jpg Type: image/jpeg Size: 874974 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 250120102458.jpg Type: image/jpeg Size: 650321 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 210120102442.jpg Type: image/jpeg Size: 913810 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 250120102459.jpg Type: image/jpeg Size: 911365 bytes Desc: not available URL: From ocl at gih.com Mon Feb 1 18:19:39 2010 From: ocl at gih.com (Olivier MJ Crepin-Leblond) Date: Mon, 01 Feb 2010 19:19:39 +0100 Subject: [IPv6crawler-wg] =?utf-8?q?Fwd=3A_ICANN_News_Alert_--_To_4=2C294?= =?utf-8?q?=2C967=2C296_and_Beyond_=E2=80=93_Under_10=25_of_IPv4_Space_Rem?= =?utf-8?q?ains=3A_Adoption_of_IPv6_Is_Essential?= Message-ID: <4B671B3B.1030806@gih.com> Hey everyone, I've made a lot of noise at ICANN around 6 months ago. It's not paying off. Warm regards, Olivier -------- Message original -------- Sujet: ICANN News Alert -- To 4,294,967,296 and Beyond ? Under 10% of IPv4 Space Remains: Adoption of IPv6 Is Essential Date : Mon, 1 Feb 2010 12:58:29 -0500 De : ICANN News Alert Pour : ocl at gih.com ICANN News Alert http://www.icann.org/en/announcements/announcement-29jan10-en.htm ------------------------------------------------------------------------ To 4,294,967,296 and Beyond ? Under 10% of IPv4 Space Remains: Adoption of IPv6 Is Essential 29 January 2010 * * *History of IPv4* It has long been anticipated, but the available pool of unallocated Internet addresses using the older IPv4 protocol ? which holds a total of slightly more than four billion IP addresses - has now dipped to below the 10 percent mark, meaning that there are only a bit over 400 million IP addresses left in the global pool of unallocated addresses. The IPv4 protocol defines the unique numeric address number assigned to each computer that is connected to the Internet. The Internet was developed in the early 1980s and has served us well for about three decades. With a bit over 400 million addresses remaining, the IPv4 address space is expected to be fully allocated in about two years? time, although predicting an exact date is not practical as this will depend upon human behaviour. ?It is important that the public understand that many of the IPv4 addresses that have been allocated have not yet been distributed to the public, so there will be no immediate global shortage of IPv4 addresses at the consumer level,? said Rod Beckstrom, ICANN?s CEO and President. *IPv4 Distribution System* IPv4 addresses are distributed in a hierarchical system. As the IANA functions operator, ICANN allocates IPv4 blocks to the five Regional Internet Registries (RIRs) around the world, and the RIRs then allocate smaller blocks to ISPs and other network operators. It is the ISPs and other Internet operators who assign the addresses to the individual Internet connections used by most computer users. Recent growth in Internet deployment in the Asia Pacific region, particularly in China, has resulted in strong growth in allocations by that region?s RIR, APNIC (Asia Pacific Network Information Centre). *Consensus Policies Developed in Regional Forums* ICANN?s process for allocating IPv4 blocks to RIRs is in accordance with the global policy that was developed through the RIRs? regional public policy forums. This process is very similar to those used for developing other ICANN policies, like the GNSO and ccNSO. The RIRs allocate addresses to ISPs and other network operators according to the policies that have been developed in these forums and which include participants from industry, governments and civil society. These forums are open to participation by anyone with access to e-mail. Bottom-up Policy Making Process ? Policy Developed by Users in a Multi-stakeholder Environment *Deploy IPv6 Now* ?This is the time for the Internet community to act,? said Rod Beckstrom, ICANN?s President and Chief Executive Officer. ?For the global Internet to grow and prosper without limitation, we need to encourage the rapid and widespread adoption of the IPv6 protocol.? IPv6 is the new system the Internet engineering community has developed to cope with the increased demand for IP addresses. Technical experts agree that the single biggest advantage of IPv6 is its capacity to accommodate Internet growth. For example, if all IPv4 address could fit within a BlackBerry, it would take a storage device the physical size of the Earth to contain all available IPv6 addresses. *Why IPv6 Is Essential for Internet Growth?* Developed in the 1990s , IPv6 has been available for allocation to ISPs since 1999. An increasing number of ISPs have been deploying IPv6 over the past decade, as have governments and businesses. The biggest attraction of IPv6 is the enormous address space it provides. Instead of just 4 billion IPv4 addresses ? fewer than the number of people on the planet ? there are 340,282,366,920,938,463,463,374,607,431,768,211,456 IPv6 addresses. An easier way to think of this number is 340 trillion trillion trillion addresses. This vastness was purposely designed so that all of the conceivable networks now and in the future would have enough addresses for the multitude of devices that can now be connected to them, such as mobile phones, general-purpose computers, cameras and e-book readers. But all sorts of devices that aren?t intended to be used by people will also soon have IP addresses. Examples include utility meters and h ousehold appliances that communicate with providers to find out the cheapest time to buy power. Similarly, IPv6 can allow people to use off-the-shelf equipment to securely connect to a myriad of home automation technologies and other systems remotely. There is no need for special gateways and proxies when every system can be securely accessed over IPSEC and operated directly. As such, adopting IPv6 addresses clearly offers a number of advantages: * There will be plenty of IP addresses for everyone. * Anything connected to a network will be able to have a unique address. * The new larger address space can open the door to a whole new generation of online devices and services. ?Quite simply, it comes down to the simple fact that IPv6 is the future of the Internet,? said Beckstrom. ?The Internet now defines communication and commerce and to accommodate its explosive worldwide growth we need to act now to guarantee an online future that accommodates growth with few limitations.? To learn more about IPv6, go to: http://www.icann.org/en/announcements/factsheet-ipv6-26oct07.pdf [PDF, 402K] ------------------------------------------------------------------------ *Sign up for ICANN's Monthly Magazine * This message was sent from ICANN News Alert to ocl at gih.com. It was sent from: ICANN, 4676 Admiralty Way, Suite 330 , Marina del Rey, CA 90292-6601. You can modify/update your subscription via the link below. Email Marketing by iContact - Try It Free! Manage your subscription -------------- next part -------------- An HTML attachment was scrubbed... URL: From ocl at gih.com Mon Feb 1 23:07:21 2010 From: ocl at gih.com (Olivier MJ Crepin-Leblond) Date: Tue, 02 Feb 2010 00:07:21 +0100 Subject: [IPv6crawler-wg] =?utf-8?q?Fwd=3A_ICANN_News_Alert_--_To_4=2C294?= =?utf-8?q?=2C967=2C296_and_Beyond_=E2=80=93_Under_10=25_of_IPv4_Space_Rem?= =?utf-8?q?ains=3A_Adoption_of_IPv6_Is_Essential?= In-Reply-To: <4B671B3B.1030806@gih.com> References: <4B671B3B.1030806@gih.com> Message-ID: <4B675EA9.3080005@gih.com> Le 01/02/2010 19:19, Olivier MJ Crepin-Leblond a ?crit : > Hey everyone, > > I've made a lot of noise at ICANN around 6 months ago. It's not paying > off. > Warm regards, I meant - it's NOW paying off. O. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ocl at gih.com Fri Feb 5 01:04:53 2010 From: ocl at gih.com (Olivier MJ Crepin-Leblond) Date: Fri, 05 Feb 2010 02:04:53 +0100 Subject: [IPv6crawler-wg] Address details for Crawler & Web servers Message-ID: <4B6B6EB5.2080903@gih.com> Hey everyone, I am happy to say that the servers are up and running. Thanks to Rex, Alan and Omer for getting them, and the network running! Great job, gentlemen! turtle.ipv6matrix.org (crawler) - 212.124.204.162 turtle.ipv6matrix.org (crawler) - 2a00:19e8:20:1::a2 elephant.ipv6matrix.org (www) - 212.124.204.170 elephant.ipv6matrix.org (www) - 2a00:19e8:20:1::aa The direct SSH into root is closed, so if you need root privilege you have to login as our own logins, and then su to super-user. The crawler (turtle.ipv6matrix.org / crawler.ipv6matrix.org) is the primary nameserver for zone ipv6matrix.org. DNS will progagate soon, so in the meantime, please use the IP addresses. The FTP server is working on each machine, so you can start transferring software across. HTTPd is running on the Web server. Bind 9 (named) is running on the crawler which is the primary NS for zones: - ipv6matrix.org - ipv6matrix.com - ipv6matrix.net The machines are also connected to each other directly at 1Gb/s through a cross-over cable. This path can be used to transfer files really quickly between the machines (the data transfers from the crawler to the www server) The ends of that cross-over cable are: shell.ipv6matrix.org (crawler) - 194.33.63.250 tusk.ipv6matrix.org (www) - 194.33.63.251 Please let me know how you get on. Cheers, -- Olivier MJ Cr?pin-Leblond, PhD http://www.gih.com/ocl.html From mmg at doc.ic.ac.uk Mon Feb 8 17:55:30 2010 From: mmg at doc.ic.ac.uk (Moustafa Ghanem) Date: Mon, 08 Feb 2010 17:55:30 +0000 Subject: [IPv6crawler-wg] Address details for Crawler & Web servers In-Reply-To: <4B6B6EB5.2080903@gih.com> References: <4B6B6EB5.2080903@gih.com> Message-ID: <4B705012.8020906@doc.ic.ac.uk> Sameh and Mohamed, I have managed to log in to the machines myself. Would you please let us know if you are having any problems accessing them. M Olivier MJ Crepin-Leblond wrote: > Hey everyone, > > I am happy to say that the servers are up and running. > Thanks to Rex, Alan and Omer for getting them, and the network running! > Great job, gentlemen! > > turtle.ipv6matrix.org (crawler) - 212.124.204.162 > turtle.ipv6matrix.org (crawler) - 2a00:19e8:20:1::a2 > > elephant.ipv6matrix.org (www) - 212.124.204.170 > elephant.ipv6matrix.org (www) - 2a00:19e8:20:1::aa > > The direct SSH into root is closed, so if you need root privilege you > have to login as our own logins, and then su to super-user. > The crawler (turtle.ipv6matrix.org / crawler.ipv6matrix.org) is the > primary nameserver for zone ipv6matrix.org. > DNS will progagate soon, so in the meantime, please use the IP addresses. > The FTP server is working on each machine, so you can start > transferring software across. > HTTPd is running on the Web server. > Bind 9 (named) is running on the crawler which is the primary NS for > zones: > - ipv6matrix.org > - ipv6matrix.com > - ipv6matrix.net > > The machines are also connected to each other directly at 1Gb/s > through a cross-over cable. > This path can be used to transfer files really quickly between the > machines (the data transfers from the crawler to the www server) > > The ends of that cross-over cable are: > > shell.ipv6matrix.org (crawler) - 194.33.63.250 > tusk.ipv6matrix.org (www) - 194.33.63.251 > > Please let me know how you get on. > > Cheers, > From ocl at gih.com Mon Feb 15 22:47:50 2010 From: ocl at gih.com (Olivier MJ Crepin-Leblond) Date: Mon, 15 Feb 2010 23:47:50 +0100 Subject: [IPv6crawler-wg] Note to Clients and Colleagues / GIH email disruption Message-ID: <4B79CF16.1050003@gih.com> 15 February 2010 Dear Clients and Colleagues, I wanted to write a quick note to explain the recent serious disruption we have had with our telecom systems and how it has hindered our business. On Thursday 11 February 2010 at around 10:55am, the GIH office lost connectivity with the outside world, and that affected all of our servers on-site which were, effectively cut-out from the rest of the world. Upon testing the line remotely, British Telecom (BT) engineers found that there was a problem at the BT exchange, and as we pay a premium to be one of their priority customers, they would have this link again within 24h. Due to "an extremely busy day", BT was unable to dispatch an engineer on-site on Friday, but promised to fix the problem by the next day. On Saturday afternoon, a BT engineer came to the GIH office and tested the line from our side, only to say "there is something seriously wrong - it makes a sound like a fire engine" and proceeded to the South Kensington Exchange to fix the fault. He called us from there to tell us that the exchange was completely deserted and that he could not fix this by himself so the work was moved to Monday - this morning. On Monday morning, after spending 45 minutes with the operator, I was told that an engineer was in the South Kensington Exchange, and an engineer onsite and they were carrying out tests on the line. I was also told that our second telephone line into the office is also facing a fault, although it appears that it is a different fault than the first one - much like the fault in the office next to ours. So no back-up link possible. Two hours later, I spent another 20 minutes with BT faults, and they announced to me that this is a major fault, with their cable being damaged and no spare capacity at all in the area, which requires closing the road, installing alternative traffic lights, digging the road up and working on the cables directly. Work would start on Wednesday 17th February due to the potential for big disruption of London traffic. I therefore arranged for our servers and router to be physically moved from the GIH office to our providers, the Twenty Twenty Media offices in South London. They are now in place in on a temporary basis, and are running smoothly again. Customers and colleagues routing their email through salsa.gih.co.uk can use the service again since it is stable. A backlog of 59 000 emails currently being stored at our back-up MX, psg.com, is being processed but will take a while to clear, so if you have not received a reply from us, please accept my most sincere apologies. These exceptional circumstances were completely outside our control. Special thanks go to Zsena Ka for coming in the office on Saturday and Rex Wickham (2020Media) for doing an exceptional job on Monday to move the servers single-handedly, in spite of traffic problems and the inability to park in the middle of the day in the busy High Street Kensington Area. Your sincerely, -- Olivier MJ Cr?pin-Leblond, PhD http://www.gih.com/ocl.html