Sigfox often deploys antennas on billboards to speed deployment.
Its secret sauce has been its relationships with operators.
Buffering packets in a network is both good and bad. It is good because a buffer can hold packets from one stream while another stream’s packets are being processed, to take up and release short bursts of traffic, to hold and then release packets when there is a very short interruption on the wire (or during a route change), and in many other situations. However, queues are bad when there is a standing queue, which means a particular flow always has some number of packets in a particular queue along the path between the source and the destination. This normally occurs at the narrowest point along the path, or rather the link with the lowest bandwidth. In a previous post, I looked at BBR, a change to the way TCP computes its window sizes, that attempts to reduce the amount of traffic “in flight” between a sender and receiver to reduce the number of packets being held in a particular buffer along the way.
This post will consider another solution: CoDel. CoDel is essentially an improved tail drop mechanism that provides the correct signals to TCP to slow down its send rate, or rather to reduce the window size (and Continue reading
Radcom carves out a CTO spot; Arista vet steps down.
VMware is taking telecom seriously.
When it comes to multi domain or Inter datacenter communication, minimizing the broadcast traffic between the datacenters is an important scaling requirement. Especially if you are dealing with millions of end hosts, localizing the broadcast traffic is critical to save resources on the network and the end hosts. Resources are bandwidth , CPU , memory […]
The post Interdatacenter broadcast control – ARP Proxy in OTV and EVPN appeared first on Cisco Network Design and Architecture | CCDE Bootcamp | orhanergun.net.
The post Worth Reading: Redliner appeared first on 'net work.
In the first post of this series we talked about some of the CNI basics. We then followed that up with a second post showing a more real world example of how you could use CNI to network a container. We’ve covered IPAM lightly at this point since CNI relies on it for IP allocation but we haven’t talked about what it’s doing or how it works. In addition – DNS was discussed from a parameter perspective in the first post where we talked about the CNI spec but that’s about it. The reason for that is that CNI doesn’t actually configure container DNS. Confused? I was too. I mean why is it in the spec if I can’t configure it?
To answer these questions, and see how IPAM and DNS work with CNI, I think a deep dive into an actual CNI implementation would be helpful. That is – let’s look at a tool that actually implements CNI to see how it uses it. To do that we’re going to look at the container runtime from the folks at CoreOS – Rocket (rkt). Rkt can be installed fairly easily using this set of commands…
wget https://github.com/coreos/rkt/releases/download/v1.25.0/rkt_1. Continue reading
Just a few notes on the blog site in general. I’ve rebuilt the sixty books pages without tables. I don’t know if this is better, but it does load a bit faster. I’ve also added links to my GoodReads and Feedly profiles just in case you’re interested in what I’m currently reading/read on a regular basis. I didn’t include all the RSS feeds I read in the shared Feedly profile, just general, culture, and technology.
The post Administravia 030417 appeared first on 'net work.