In today’s episode we’re talking about IPv6. More specifically, we discuss what it takes to run an IPv6 only network. Why now? And why not dual stack? Well, in the middle of November (2019), the US government put out a memo outlining their updated guidelines and expectations for IPv6. In it, they mandate a future vision of 80% of devices connected to IPv6 only networks by 2025. That’s not that far away. So, as many of our peers who work in US federal organizations are preparing for a world that is IPv6 only, we figured it might be time for us to do the same.
Long story short: ipSpace.net is going on an extended coffee break on June 24th 2021. You can stop reading; the rest of the blog post is full of details you probably don’t care about.
What exactly does that mean? Honestly, we don’t know yet… but we felt that it’s only fair to let engineers considering our subscriptions know months in advance what might happen.
Also, after investing two lifetimes into this project, and a few planned changes coming just before our regular summer hiatus (see below) it’s time for a longer break. ipSpace.net might be back to business-as-usual after a few months (unlikely), or it could be Ivan working on some interesting stuff (most likely) or ipSpace.net slowly disappearing into the sunset (not impossible).
The OSI model is perhaps the best-known—and perhaps the most-loved—model in the networking world. It’s taught in every basic networking course, and just about every blog (other than this one) has some article explaining the model someplace or another (for instance, here is one of the better examples).
The reality is, however, that I’ve been in the networking business for 30’ish years and I’ve never once used the OSI model for anything practical. I’ve used the model when writing books because just about every book on networking has to have a section on the OSI model. I’ve used the model when writing a paper comparing two different protocols, back in the multiprotocol days (VIP versus IPX versus IP), but we don’t have those kinds of arguments very often any longer.
So, we all learn the OSI model, and yet I don’t know of anyone who actually uses the OSI model in understanding how protocols work, or how to troubleshoot a network. There’s the “it’s a layer two problem” statement, and that’s about the end its useful life, it seems.
Let me make a suggestion—learn, use, and teach the RINA model instead. Okay, so what is the RINA model? It is Continue reading
Broadband to the people: A new COVID-19 stimulus bill passed by the U.S. Congress includes $7 billion to help residents connect to broadband and pay their monthly bills, the Washington Post reports. The legislation is one of the largest one-time investments in broadband ever in U.S. history. “Nearly half the money is slated to fund a new monthly benefit for low-income families, aiming to ensure that those who have lost their jobs can stay online at a time when the pandemic has forced millions of people to work, learn and communicate on their devices from home.”
RIP Flash: Adobe has finally killed off the controversial Flash video and animation tool that was a formative technology for the Internet, the Independent says. While Flash was widely used on websites for many years, critics complained about security problems and a poor user experience. In 2009, 99 percent of all PCs with an Internet connection had Flash installed, Adobe has said.
Alexa, what taxes do I owe? The Indian government is working on Alexa-like chatbots to deliver public services, India Today reports. The government has invited bids for a voice assistant similar to Amazon’s Alexa and Google Assistant. Using artificial Continue reading
We had the usual gloomy December weather during the end-of-year holidays, and together with the partial lockdown (with confusing ever-changing rules only someone in Balkans could dream up) it managed to put me in OCD mood… and so I decided to remove broken links from the old blog posts.
While doing that I figured out how fragile our industry is – I encountered a graveyard of ideas and products that would make Google proud. Some of those blog posts were removed, I left others intact because they still have some technical merits, and I made sure to write sarcastic update notices on product-focused ones. Consider those comments Easter eggs… now go and find them ;))
Anyway, I also salvaged some of the old content I was stupid enough to publish somewhere else from archive.org. Here it is:
For years now I've had a light switch that can be programmed to turn itself on/off on a schedule. The switch is programmed with the date, time, time zone, and lat/long and then you can create a schedule such as, "turn the lights on at sun set". It works pretty well except when 1/ daylight savings time starts or stops (the schedule doesn't adjust itself) or 2/ the power goes out (bye, bye all programming).
This slight annoyance coupled with my desire for a project I could geek out on lead me to look into software-controllable light switches.
In this post I'll explain how I flashed the open source Tasmota firmware onto the Treatlife 3-way wall switch which in the end allowed me to control the lights via a home automation controller.