See how to create custom endpoint policies in Cisco Identity Services Engine.
One of my readers sent me this question:
Other than using Excel (and of course an automation tool) any suggestions for a tool to create device config for some 200 customer VRFs from a standard template?
You need three things to get the job done:
Read more ...Five fun facts:
Back in December 2014, Cloudflare opened our first data center in Africa and our 30th datacenter globally. That was in Johannesburg, which has since seen over 10x growth in traffic delivered to South Africa and surrounding countries.
Now, we are expanding into our second city in South Africa — Cape Town, bringing us 870 miles (1,400km) closer to millions of Internet users. Only 15% smaller than Johannesburg by population, Cape Town commands a majority of the tourism business for the country.
For Cloudflare, our newest Continue reading
Is the Internet bringing us together? Or is it further dividing us? Will the Internet of the future be a force for social cohesion? Or will it lead to greater fragmentation?
Please join us on Thursday, May 11, from 12:30 - 14:00 BST (UTC+1) for a live video stream out of the Royal Institute of International Affairs at Chatham House in London, UK. In the session a panel of experts will address these and many related questions (view the longer description):
Full Stack Journey episode 8 features Ivan Pepelnjak, well-known author, blogger, podcaster, and speaker. Ivan produces a phenomenal amount of content around networking and adjacent technologies.
The post Full Stack Journey 008: Ivan Pepelnjak appeared first on Packet Pushers.
On Friday, we announced DNS analytics for all Cloudflare customers. Because of our scale –– by the time you’ve finished reading this, Cloudflare DNS will have handled millions of DNS queries –– we had to be creative in our implementation. In this post, we’ll describe the systems that make up DNS Analytics which help us comb through trillions of these logs each month.
Cloudflare already has a data pipeline for HTTP logs. We wanted to utilize what we could of that system for the new DNS analytics. Every time one of our edge services gets an HTTP request, it generates a structured log message in the Cap’n Proto format and sends it to a local multiplexer service. Given the volume of the data, we chose not to record the full DNS message payload, only telemetry data we are interested in such as response code, size, or query name, which has allowed us to keep only ~150 bytes on average per message. It is then fused with processing metadata such as timing information and exceptions triggered during query processing. The benefit of fusing data and metadata at the edge is that we can spread Continue reading