Should service providers offer managed SD-WAN services? According to Betteridge’s law of headlines, the answer is NO, and that’s exactly what I explained in a short video with the same name.
Turns out there’s not much to explain; even with my usual verbosity I was done in five minutes, so you might want to watch SD-WAN Technical Challenges as well.
Should service providers offer managed SD-WAN services? According to Betteridge’s law of headlines, the answer is NO, and that’s exactly what I explained in a short video with the same name.
Turns out there’s not much to explain; even with my usual verbosity I was done in five minutes, so you might want to watch SD-WAN Technical Challenges as well.
Infrastructure security is something that is important to get right so that attacks can be prevented—or, in the case of a successful attack—damage can be minimized. It is especially important in a Kubernetes environment because, by default, a large number of Kubernetes configurations are not secure.
Securing Kubernetes at the infrastructure level requires a combination of host hardening, cluster hardening, and network security.
Let’s dive into each of these and look at best practices for securing both self-hosted and managed Kubernetes clusters.
There are many techniques that can be used to ensure a secure host. Here are three best practices for host hardening.
If you have the flexibility to choose an operating system (i.e. your organization doesn’t standardize on one operating system across all infrastructure), use a modern immutable Linux distribution, such as Flatcar Container Linux or Bottlerocket. This type of operating system is specifically designed for containers and offers several benefits, including:
Another year of massive growth in the number and speed of connections to the global Internet—what is the impact on the global routing table? Goeff Huston joins Tom Ammon and Russ White to discuss the current state of the BGP table, the changes in the last several years, where things might go, and what all of this means. This is part 1 of a two part episode.
Today's IPv6 Buzz discusses how to sell IPv6 as a project. That is, doing the advocacy work in your organization to drive IPv6 adoption. We examine the business and technical arguments you can make, including tying IPv6 to initiatives around cloud, containers, and zero trust.
The post IPv6 Buzz 097: Selling An IPv6 Project To Your Organization appeared first on Packet Pushers.
An AS, or Autonomous System, is a group of routable IP prefixes belonging to a single entity, and is one of the key building blocks of the Internet. Internet providers, public clouds, governments, and other organizations have one or more ASes that they use to connect their users or systems to the rest of the Internet by advertising how to reach them.
Per AS traffic statistics and trends help when we need insight into unusual events, like Internet outages, infrastructure anomalies, targeted attacks, or any other changes from service providers.
Today, we are opening more of our data and launching the Cloudflare Radar pages for Autonomous Systems. When navigating to a country or region page on Cloudflare Radar you will see a list of five selected ASes for that country or region. But you shouldn’t feel limited to those, as you can deep dive into any AS by plugging its ASN (Autonomous System Number) into the Radar URL (https://radar.cloudflare.com/asn/<number>). We have excluded some statistical trends from ASes with small amounts of traffic as that data would be difficult to interpret.
The AS page is similar to the country page on Cloudflare Radar. You can find traffic levels, protocol Continue reading
In the fourth installment of this 9-video series, Russ White describes methods for scaling data center fabrics. He reviews how to calculate port density in a leaf-spine design, discusses physical restraints on the scale of a fabric based on the spines, fabric types in chassis switches, and the pros and cons of chassis vs. single […]
The post Understanding Data Center Fabrics 04: Clos Scaling – Video appeared first on Packet Pushers.
Once your Mac computer gets connected to a source of wifi and the password has been saved, its unique features enable it to automatically reconnects once in range with the wifi network.. At first, this might be okay not until for some reason, you don’t want it to be connected anymore.
Sometimes, when there are various networks in range that had been previously connected and saved to your Mac, it becomes difficult for your system to choose which one to connect to as they are all saved and could easily be connected. In situations like this, you may want to connect to one particular network but it probably connects to the wrong one. In this scenario, you would want to disconnect with the unwanted wifi network, and to do that means you would need to forget the wifi.
There are other various reasons why you may need to forget your wifi network. Probably you’ve got lots of already connected networks and you would like to reduce them or you no longer really use the network anymore and don’t want it always connected or you probably have more than one wifi and would no longer want to use one but the Continue reading
TL&DR: Ansible might decide to reorder list values in a loop parameter, resulting in unexpected order of execution and (in my case) totally borked device configuration.
A bit of a background first: I’m using an Ansible playbook within netsim-tools to deploy initial device configurations. Among other things, that playbook deploys configuration snippets for numerous configuration modules, and the order of deployment is absolutely crucial. For example, you cannot activate BGP neighbors in Labeled Unicast (BGP-LU) address family (mpls module) before configuring BGP neighbors (bgp module).
TL&DR: Ansible might decide to reorder list values in a loop parameter, resulting in unexpected order of execution and (in my case) totally borked device configuration.
A bit of a background first: I’m using an Ansible playbook within netlab to deploy initial device configurations. Among other things, that playbook deploys configuration snippets for numerous configuration modules, and the order of deployment is absolutely crucial. For example, you cannot activate BGP neighbors in Labeled Unicast (BGP-LU) address family (mpls module) before configuring BGP neighbors (bgp module).
In this post I will show you how to setup Terraform to connect to your Google Cloud Platform (GCP) tenancy to manage your GCP infrastructure as code. Software The following software was used in this post. Terraform - 1.1.7 Ubuntu - 2004 gcloud - 378.0.0 Pre-Flight Check Google...continue reading
On today's Tech Bytes with sponsor Singtel, we look at SD-WAN as a critical network feature for cloud access, including the use of overlays to simplify operations. We also discuss why organizations might consider a service provider for SD-WAN and dig into Singtel's SD-WAN offering.
The post Tech Bytes: The Advantages Of Singtel SD-WAN For Cloud Access (Sponsored) appeared first on Packet Pushers.