This past weekend, we observed the one-year anniversary of the first of many COVID-19 lockdowns. Since then, schools, small businesses, healthcare providers, and financial institutions around the world have relied on the Internet to maintain operations and deliver critical services – bringing the need for broadband access into sharp focus. The overflow of demand for digital communication amid the ongoing pandemic has put the Internet’s structural integrity and capacity to the test. Overwhelmingly, it has delivered.
The Internet’s network of networks has enabled massive segments of the global workforce to shift to remote operations, allowed schools to provide online educations to students around the world, and offered a space for countless businesses and individuals to continue to serve their communities amid a global crisis. The Internet’s role in not just sustaining crucial aspects of day-to-day life, but enabling communities to thrive throughout the COVID-19 pandemic is undoubtedly crucial. It is clear – now more than ever – that the Internet is indeed a force for good. The success of the Internet is the result of its universally accessible, decentralized, and open architecture; this Internet Way of Networking must be protected to allow us all to use this critical resource to its Continue reading
In the networking world, many equate simplicity with the fewest number of moving parts. According to this line of thinking, if there are 100 routers, 10 firewalls, 3 control planes, and 4 management systems in a network, then reducing the number of routers to 95, the number of firewalls to 8, the number of control planes to 1, and the number of management systems to 3 would make the system “much simpler.” Disregarding the reduction in the number of management systems, scientifically proven to always increase in number, it does seem that reducing the number of physical devices, protocols in use, etc., would tend to decrease the complexity of the network.
The wise engineers of the IETF, however, has a word of warning in this area that all network engineers should heed. According to RFC1925, rule 5: “It is always possible to agglutinate multiple separate problems into a single complex interdependent solution. In most cases this is a bad idea.” When “conventional wisdom” and the wisdom of engineers with the kind of experience and background as those who write IETF documents contradict one another, it is worth taking a deeper look.
A good place to begin is Continue reading
In the last weeks I described the challenges you might face when converting XML documents that contain lists with a single element into JSON, be it on device (Nexus OS) or in an Ansible module. Now let’s see how we can fix that.
In the last weeks I described the challenges you might face when converting XML documents that contain lists with a single element into JSON, be it on device (Nexus OS) or in an Ansible module. Now let’s see how we can fix that.
This is a running list of unusual data found in the Domain Name System.
Typically, DNS stores name-to-IP (for example, foo.example.net -> 192.0.2.123
) and IP-to-name mappings (i.e., the inverse). But, the
DNS is arguably the biggest, most distributed key/value store on the planet,
making it a great place to stash all kinds of simple data.
Google won’t pay for news: Google has threatened to end its search engine services in Australia over the government’s efforts there to require the company to pay news publishers for articles it links to, the BBC reports. The proposed Australian news code would require Google and Facebook to enter into mediated negotiations with publishers over the value of news content, if they don’t reach agreement first.
RIP, balloon-based Internet: Alphabet, Google’s parent company, is shutting down Loon, its attempt to deliver Internet service through balloons floating in the stratosphere, CNet reports. Alphabet says the business model doesn’t work, with the company unable to get costs low enough to offer services.
Judge rejects Parler: A U.S. judge has ruled that Amazon doesn’t have to reinstate Parler, the conservative Twitter competitor, after the company kicked it off its web hosing services this month, NPR reports. Amazon kicked out Parler after some members of the site threatened U.S. lawmakers and allegedly used the service to plan the 6 January attack on the U.S. Capitol. Parler has argued that Amazon’s decision threatens it with “extinction,” but the judge ruled that Amazon is under no obligation to “host the incendiary speech that Continue reading
On today's Tech Bytes podcast, sponsored by AppNeta, we talk about getting real-time monitoring in place so that you can clearly define your performance benchmarks, accurately measure them from the end-user perspective, and have a strategy to make sure those benchmarks are met. Our guests are John Tewfik, Director of Global Alliances; and Seth Differ, Senior Manager, Solutions Consulting.
The post Tech Bytes: Doing Better Than ‘Good’ Or ‘Bad’ For UX Metrics (Sponsored) appeared first on Packet Pushers.
The modern world craves our attention—but only in short bursts. To give your attention to any one thing for too long is failing, it seems, because you might miss out on something else of interest. We have entered the long tail of the attention economy, grounded in finding every smaller slices of time in which the user’s attention can be captured and used.
The problem is obvious for anyone with eyes to see. What is the solution? The good news is there are solutions. The bad news is these solutions are swimming upstream against the major commercial interests of our day, so it’s going to Continue reading
curl -O https://raw.githubusercontent.com/sflow-rt/fabric-view/master/demo/topology.jsonThen, download the topology file for the example.
curl -X PUT -H "Content-Type: application/json" -d @topology.json \Install the topology using the sFlow-RT REST API.
http://localhost:8008/topology/json
curl http://localhost:8008/topology/jsonRetrieve the topology.
{
"version": 0,
"links": {
"L1": {
"node2": "spine1",
"node1": "leaf1",
"port1": "swp1s0",
"port2": "swp49"
},
"L2": {
"node2": "spine1",
"node1": "leaf1",
"port1": "swp1s1",
"port2": "swp50"
},
"L3": {
"node2": "spine2",
"node1": "leaf1",
"port1": "swp1s2",
"port2": "swp51"
},
"L4": {
"node2": "spine2",
"node1": "leaf1",
"port1": "swp1s3",
"port2": "swp52"
},
"L5": {
"node2": "spine2",
"node1": "leaf2",
"port1": "swp1s0",
"port2": "swp49"
},
"L6": {
"node2": "spine2",
"node1": "leaf2",
"port1": "swp1s1",
"port2": "swp50"
},
"L7": {
"node2": "spine1",
"node1": "leaf2",
"port1": "swp1s2",
"port2": "swp51"
},
"L8": {
"node2": "spine1",
"node1": "leaf2",
"port1": "swp1s3",
"port2": Continue reading
Today's Network Break examines Citrix's multi-billion bet on a SaaS collaboration acquisition, a fight over the Elasticsearch project where everyone gets a black eye, Red Hat's sop to everyone angry about CentOS, a pair of dangerous Cisco SD-WAN bugs, and more IT news.
The post Network Break 317: Citrix Bets The House On SaaS Collaboration; AWS Forks Elasticsearch appeared first on Packet Pushers.