CloudFlare turns 5 years old this September. It's been an amazing ride since our launch. Before we launched at TechCrunch Disrupt on September 27, 2010, we'd signed up about 1,000 beta customers. It took us nine months to get those first customers. (By comparison, today we typically sign up 1,000 customers every 3 hours.)
Those first beta customers were instrumental. They put up with us when we were had only one data center (in Chicago). They put up with us as we brought traffic online in our next facilities in Ashburn, Virginia and San Jose, California — and had the routing challenges that came along with running a distributed network for the first time. They sent us bug reports, provided us feature requests, and were instrumental to building the foundation that grew into what is CloudFlare today.
Archival Footage
When we launched, we wanted to feature their stories and experience about CloudFlare so we had them submit their stories by video. Here's the video we included as part of our launch presentation.
I'm proud of the fact that more than 80% of those original 1,000 customers are still using CloudFlare five years later.
Send Us Your Stories
As we Continue reading
In recent months the news of Chris Roberts alleged hacking of an inflight entertainment system and possibly other parts of the Boeing 737 have sparked a wave of controversy. Public opinion was originally on Roberts' side, but the recent publication of the FBI affidavit changed that drastically. According to the affidavit, Roberts admitted to doing a live "pen-test" of a plane network in mid-air.
Whether this is true or not, it raises some valid concerns over the ethical implications of white hat hacking. In the case of Roberts, who, according to the affidavit, was able to steer the airplane off the intended course, the consequences could have been dire. It is not believed that Roberts had any intention of hurting either himself or any of the passengers, but if the affidavit is in fact true, the possibility was real.
To read this article in full or to leave a comment, please click here
Who owns ONIE security?
A favorite topic among network engineers, documentation is a source of both wonder and horror. Network documentation is difficult to get right. How much detail is enough? How old is that diagram, really? Can't this be automated? Wait, the automated generator spit out *that*? In this show, the Packet Pushers along with former guest Dominik discuss their documentation experiences, good and bad. What have we gotten right? What have we gotten wrong? What's been worth the trouble? What was a waste of time? What did we wish we'd documented before we really needed it?
The post Show 250 – How To Document A Network appeared first on Packet Pushers.
This vendor-written tech primer has been edited by Network World to eliminate product promotion, but readers should note it will likely favor the submitter’s approach.
Advancements in attack evasion techniques are making new threats extremely difficult to detect. The recent Duqu 2.0 malware, which was used to hack the Iranian nuclear pact discussions, Kaspersky Lab, and an ICS/SCADA hardware vendor, is a prime example. To keep up, a new security model that uses a different approach to the traditional “evidence of compromise” process is needed.
To read this article in full or to leave a comment, please click here
What's on your network monitoring agenda?
This episode of Network Break looks at ONIE security risks, a sensible car hack lawsuit, missing millions at Ubiquiti, EMC and VMware going all the way, a potential Apple win at IBM, and other tech news.
The post Network Break 48: Apple Smugness, ONIE Pwned appeared first on Packet Pushers.
Enter the advanced security arena with the A10 DemoFriday on September 11, 2015.

The post Worth Reading: Another Salvo in the Crypto War appeared first on 'net work.

The post Worth Reading: Knowledge and Power appeared first on 'net work.
Yes, we really are going to reach a point where the RIRs will run out of IPv4 addresses. As this chart from Geoff’s blog shows —
Why am I thinking about this? Because I ran across a really good article by Geoff Huston over at potaroo about the state of the IPv4 address pool at APNIC. The article is a must read, so stop right here, right click on this link, open it in a new tab, read it, and then come back. I promise this blog isn’t going anyplace while you’re over on Geoff’s site. But my point isn’t to ring the alarm bells on the IPv4 situation. Rather, I’m more interested in how we got here in the first place. Specifically, why has it taken so long for the networking industry to adopt IPv6?
Inertia is a tempting answer, but I’m not certain I buy this as the sole reason for lack of deployment. IPv6 was developed some fifteen years ago; since then we’ve deployed tons of new protocols, tons of new networking gear, and lots of other things. Remember what a cell phone looked like fifteen years ago? In fact, if we’d have started fifteen years ago Continue reading

Matt has a greater starter up on running Cumulus IX on a Vagrant installation — since Vagrant is available on a few widely deployed machines, this is a great tool for learning the environment. As soon as I can get one of my Ubuntu machines local, or figure out how to get enough drive space on one of my laptops to install this, I’ll be getting Vagrant set up to use on a few different things.
The post Worth Reading: Vagrant and Cumulus appeared first on 'net work.