AT&T activated the first US dynamic spectrum sharing deployment; Ericsson burned cash on China...
May means more content! There was a very exciting announcement from us this month, and if you missed it don’t worry, you can read all about it below. In addition, we were keeping very busy with fresh podcast episodes, informative blog posts and much more. Ready to dive into all things open networking? Get comfortable and let’s dive in.
UCMP: Augmenting L3 only designs: So what makes a purely L3 design so aspirational? Can a UCMP increase efficiency? Read this blog post by Rama Dharba as he addresses these questions and more. He delves into the challenges surrounding this type of design, possible solutions and a recent augmentation in Cumulus Linux 4.1 that increases the design’s ability for flexibility.
Kernel of Truth season 3 episode 6: Building modern campus networks: Let’s talk about all things modern campus networks. In this new Kernel of Truth episode, Brain O’Sullivan, Roopa Prabhu, Eric Pulvino and David Marshall dive into trends, technologies, architecture and much more. Grab your headphones and get ready to hear first-hand experiences from building these networks as well as tips and tricks learned along the way.
Build an OpenStack/ Ceph cluster with Cumulus Networks in Continue reading
Companies can kiss their dream of a future dominated by smart machines goodbye unless they start...
QUIC is a relatively new data transport protocol developed by Google, and currently in line to become the default transport for the upcoming HTTP standard. Because of this, it behooves every network engineer to understand a little about this protocol, how it operates, and what impact it will have on the network. We did record a History of Networking episode on QUIC, if you want some background.
In a recent Communications of the ACM article, a group of researchers (Kakhi et al.) used a modified implementation of QUIC to measure its performance under different network conditions, directly comparing it to TCPs performance under the same conditions. Since the current implementations of QUIC use the same congestion control as TCP—Cubic—the only differences in performance should be code tuning in estimating the round-trip timer (RTT) for congestion control, QUIC’s ability to form a session in a single RTT, and QUIC’s ability to carry multiple streams in a single connection. The researchers asked two questions in this paper: how does QUIC interact with TCP flows on the same network, and does UIC perform better than TCP in all situations, or only some?
To answer the first question, the authors tried running QUIC Continue reading
The vendor's business in China has grown as of late, having inked contracts with the country’s...
The updates follow a move by Chef last year to revamp its development, platforms, and go-to-market...
Today’s Tech Bytes episode, sponsored by Fortinet, explores an SD-WAN deployment with PAYOMATIC, a lending company in NYC. We talk about how PAYOMATIC cut costs by migrating off MPLS, and how Fortinet Secure SD-WAN positioned the company to take advantage of new infrastructure options. Our guest is Michael Saraceno, CISO and VP of IT at PAYOMATIC.
The post Tech Bytes: Payomatic Cuts Costs, Revamps WAN With Fortinet Secure SD-WAN (Sponsored) appeared first on Packet Pushers.
Read this blog in Portuguese
Improving the state of routing security is no small task. It requires network operators, IXPs, and CDN and cloud providers of all sizes across the globe to work together, improve their own networks, and open lines of communications with both their friends and competitors to make a real difference.
One of the ways we’ve been able to spread the MANRS message so far and wide is through partnerships. We’re lucky to have dedicated, strong partners in several regions of the world. In this post, we’ll talk about one partnership in particular – NIC.br – and how their efforts have changed the landscape for routing security in Brazil and beyond.
A Little History
NIC.br is responsible for the administrative and operational functions related to the .br (Brazil) domain. In addition, NIC.br goes beyond similar entities in other countries, investing in actions and projects that bring a series of benefits to the improvement of activities related to the available Internet infrastructure in Brazil.
In 2017, NIC.br hosted a Safer Internet Program, which the Internet Society supported. NIC.br invited Andrei Robachevsky to speak on a fairly new initiative called MANRS addressing routing security as Continue reading
Today's Network Break podcast discusses the growth of the infrastructure market based on Open Compute specs, the decline in switch and routing revenues, Cisco postponing its 2020 Cisco Live virtual event, VMware's latest acquisition, and more tech news.
The post Network Break 287: Open Compute Infrastructure Makes Its Mark; Cisco Live Postponed appeared first on Packet Pushers.
No free encryption: Popular videoconferencing service Zoom has promised to roll out end-to-end encryption, but it won’t provide encrypted service to free users, The Verge reports. The decision allows Zoom to share information about free conference with law enforcement agencies. Zoom doesn’t want to give free users end-to-end encryption “because we also want to work together with the FBI, with local law enforcement, in case some people use Zoom for a bad purpose,” Zoom CEO Eric Yuan said.
A big spike: Internet use has gone up dramatically in rural India in recent weeks, with people flocking to YouTube, Netflix, and other services during the COVID-19 pandemic, Inc42.com reports. Data consumption on the BharatNet fiber backbone nearly tripled, to 150 Terabytes in May from 55 TB in January. During the same timeframe, Netflix use in rural India grew by 422 percent, with YouTube and Facebook growing by 219 percent and 374 percent, respectively.
Broadband challenges: The government of Nigeria has a new broadband plan with a goal of increasing download speeds to 25 Mbps in urban areas and 10 Mbps in rural areas, Quartz Africa says. The country now has a mean download speed of less than 1.6 Mbps. But Continue reading
“DSS is an important stepping stone on our path to nationwide 5G," AT&T's Igal Elbaz said.
I often hear people expressing their of helplessness in the face of pervasive corporate surveillance. "They've already got all my data, what can I do anyway ?" When I was twenty five, my career was centred on maintaining Novell and Windows networks, my life aspirations were to own my car and a house. My social […]
The post Not Giving Up on Data Surveillance appeared first on EtherealMind.
A long while ago I decided to write an article explaining how you could run VMware NSX on ESXi servers with redundant connections to two top-of-rack switches on top of a layer-3-only fabric (a fabric with IP subnets and VLANs limited to a single top-of-rack switch). Turns out that’s Mission Impossible, so I put the article on the back burner and slowly forgot about it.
Well, not exactly. Every now and then my subconsciousness would kick it up and I’d figure out yet-another reason why it’s REALLY hard to do it right. After a while, I decided to try again, and completely rewrote the article. The first part is already online, more details coming (hopefully) soon.
XML, or Extensible Markup Language, rounds out the usual suspects of YAML, JSON, and XML. It’s probably my least favorite of the three, but knowledge of XML is needed when working with code.
XML is, of course, related to HTML. So why didn’t we just settle for HTML? Turns out machines don’t understand HTML very well. They can parse it perfectly fine, yes, but in HTML you put information in, such an address, and you understand it’s an address because you are a human. A machine doesn’t know that Baker Street is an address, unless you tell it.
XML consists of tags, elements, and attributes. Let’s take a basic example and then go through these in more detail:
<?xml version="1.0" encoding="UTF-8"?> <address> <name> <title>Mr</title> <first-name>Sherlock</first-name> <last-name>Holmes</last-name> </name> <street>221B Baker Street</street> <city state="NA">London</city> </address>
First, we declare that this is an XML document and the encoding used. This is called a prolog. It’s optional, but if included, should always be the first line.
The tag <address>
is the root of the document. We must always have a root. The tag <address>
has three children:
<name>
<street>
<city>
The tag <name>
has three children as well: