Author Archives: wirednot

About wirednot

WLAN Professional, Writer. thinker of big thoughts. Proud of my kids, love my wife, thankful for my primary employment and good fortune in being able to do other things on the side. I'm a well-travelled homebody, and frequently find that adventure has sought me out to tangle a a bit. Buy me a beer, I'll tell you some war stories.

Contemplations on Large-Scale Cloud Wi-Fi in Higher Education

For so many years, the Wi-Fi story at most campuses has been pretty similar: hundreds or thousands of access points connect to some number of controllers, and it’s all managed by a network management system. Sounds simple enough, but this basic formula of WLAN building blocks has a number of implications that many of us who keep these networks up frequently get weary of. I recently took part in a panel discussion webinar where some notable wireless network managers and architects from the higher ed space discussed these implications. Let me share what we talked about, and we’ll see if any of it resonates with you- and I’m sure that you’d agree that the topics covered here certainly apply well beyond higher ed.

Mist Systems Hosts the Panel Discussion
Mist Systems isn’t the first company to bring cloud-managed wireless to market, but they do offer some fairly comprehensive strategies for those interested in different options. During the panel session, we talked with Bryan Ward from Dartmouth College and Brian Stephens from MIT. Both of these gents are now using Mist for their respective campus WLAN environments, albeit in different topologies. Rounding out the panel was Rowell Dionicio of Packet6.com, Wes Purvis and Jussi Kiviniemi (Mist Product Management team), and myself. Though Rowell and I both have deep backgrounds in higher ed wireless, we joined this session as independent consultants.

The Layer 2 Elephant in the Room
Back in the day when controllers first hit the market, they gave the WLAN world a major gift at Layer 2. With “fat APs”, any VLAN in use by the access point needs to be part of a trunk on the Ethernet uplink. But when the AP is controller based, a single management VLAN can be used to encapsulate a number of VLANs using CAPWAP tunnels. Using controllers allows for a much simpler L2 paradigm from the perspective of AP-uplink switch and switchport configurations- by an order of magnitude in large environments. To me, this is perhaps one of the most significant single benefits of using controller-based WLAN, and is one potential obstacle when going to a cloud-managed model. Old L2 concerns come back to haunt us when the controller gives way to a cloud-managed management plane, and not all vendors have an answer to the dilemma.

During our discussion, we learned that Dartmouth re-engineered their LAN network and embraced configuration automation to reduce the L2 admin burden when they migrated away from their old Cisco controllers to Mist’s cloud-managed WLAN. By contrast, MIT’s timeline for WLAN upgrades required that they NOT re-engineer their L2 environment, meaning they needed a solution to the L2 dilemma.

How do you take advantage of CAPWAP/similiar tunnel terminations afforded by controllers, when you are abandoning controllers? Mist provides an appliance called the Mist Edge which allows for termination of AP-management tunnels and VLAN aggregation, while still keeping the rest of Management Plane functions out in the cloud. This option allowed MIT to quickly get their Wi-Fi moved to the cloud paradigm while preserving their legacy LAN topology.

There was a lot of good discussion about what exactly a controller is versus solutions like Mist Edge and similar building blocks from other vendors. Wes presented this graphic to guide discussion:

Why Else is the Controller Construct so Important When Considering Cloud W-Fi?
Aside from Layer 2 concerns, we heard from both MIT and Dartmouth the various ways their admin time has gotten more productive since they jettisoned controllers. We all spoke of reliability and such, and there is no doubt that a move to the cloud simplifies major administrative tasks. I’ve used cloud-managed networking in almost twenty branch locations of varying sizes for at least a decade, and I can say that not having to upkeep both controller code and quirky, feature-bloated management servers is nothing short of liberating.

The panel as a group seemed to agree that many WLAN professionals get hung up on the loss of nerd-knobs and command-line deep debug capabilities when they consider a move away from controllers to cloud. I wasn’t the only one to vocalize that often the deeper debugs we do on controllers are when we are troubleshooting controller code for TAC rather than actually trying to figure out Wi-Fi or client issues (this gets extremely old). Dartmouth’s Bryan Ward spoke highly of the ease of use and effectiveness of Mist’s API capabilities from first-hand experience when deeper-than-GUI information is needed, while MIT’s Brian Stephens reflected on the Mist interface being comprehensive enough for daily use. Both perspectives are good news for the controller-weary. Competing cloud systems have similar API functionality, and one point of analysis at evaluation time is always “is there the right balance between GUI and API?” from the usability perspective.

A Lot to Consider, Digest
For me, this discussion does scrape off a significant portion of apprehension about potentially moving a large WLAN of many thousands of access points to the cloud-managed paradigm. (In my perfect world, I’d be able to keep my existing very expensive controller-based APs and use them with another vendor’s cloud solution- but the world doesn’t work that way, and likely never really will at enterprise scale.) We covered a lot of ground, with these among some of the other details to ponder:

• Rowell asked a great question- can we make a Mist Edge in VM? Wes replied that it could be done, but most customers don’t.
• Bryan Ward pointed out that SNMP completely goes away with the Mist deployment.
• Brian Stephens made the case that so many other enterprise systems are moving to a cloud-managed model that taking Wi-Fi there really isn’t that much of a leap.
• We all talked about the “what if your Internet connection goes down?” I’ll say that your Mist Wi-Fi will be fine during the downtime, but let you hear the rest of the conversation for yourself when you watch the session.
• We also hit on how funding changes from Capex to Opex with cloud management, and the value of scripting skills for network admins

There’s a lot more to hear, and it’s better firsthand so I hope you spend an hour or so and watch it. I will close by saying this: regardless of what system you are contemplating, you really have to do an honest eval with it the way you would actually use it daily, and you also have to talk to real-world customers that have been empowered to speak freely about the good and less-than-great of the solution you’re interested in.

This panel discussion was especially useful to me because Bryan and Brian have already gone down a road I think about often, and Rowell’s insights are always right on. I’m now better equipped to think about the WLAN future of environments that I manage.

If you missed one of the embedded links above, find the webinar here.

Mighty mioty and a Bit of IoT Knowledge

Like many of you, I get a lot of emails announcing some new thing going on under the general heading of technology. Most get a quick glance, register as either ho-hum or not of particular interest, and then get quietly flushed out my email box’s septic system. But a recent announcement regarding mioty gnawed at me. I wasn’t sure why, and then it hit me…

Why do they not capitalize the M?

Somehow I didn’t know that mioty is a competitor to LoRaWAN when I scanned the email, but I do know that the announcement covered the first “mioty Blueooth Low Energy Dual Stack“. EVERY WORD WAS CAPITALIZED EXCEPT MIOTY AND IT FREAKIN DROVE ME NUTS.

Yeah, I know- that’s probably a weird reason to be paying attention to a new-to-me technology… but truth be told, it was enough to hook me. I started digging in.

So Much to Learn

One of my several during-COVID areas of self-study is IoT. I got into LoRaWAN and a few others, I’m starting down the road of CWNP’s IoT-related certifications, and I give my RF Explorer and other spectrum analyzers/SDRs frequent workouts trying to capture fleeting little low-power pulses from all sorts of gadgets. I do know that “IoT” is one of those oft-abused words that some vendors try to own in their marketing of Wi-Fi systems, but the concept of IoT is far-ranging, very Un-Wi-Fi at times, and maybe even endless, when you think about it.

So.. I’m not completely IoT-ignorant, yet little-m mioty had never registered in my brainpan to date. If you too are in the dark, let me get you started. Think massive IoT. There’s an Alliance. Stolen from the mioty Alliance’s web pages, the following describes what differentiates this technology from others in the space:

The core invention behind the mioty technology is the Telegram Splitting Multiple Access (TSMA) method. As defined by the European Telecommunications Standards Institute (ETSI TS 103 357), Telegram Splitting splits the data packets to be transported in the data stream into small sub-packets at the sensor level.

These sub-packets are then transmitted over different frequencies and time. An algorithm in the base station permanently scans the spectrum for mioty sub-packets and reassembles them into a complete message. Due to sophisticated Forward Error Correction (FEC), the receiver only needs 50% of the radio bursts in order to completely reconstruct the information. This reduces the impact of corrupted or lost bursts due to collisions and increases the resistance to interference.

That should tickle the fancy of anyone who claims to do wireless…

Combine mioty and Bluetooth for Fascinating Scenarios

So now you have a starting point to go learn more about mioty, if you needed one. Let me bring you back to the announcement that started this whole thing for me- a company called BehrTech combining forces with Texas Instraments to put mioty and the latest Bluetooth (BLE 5.2) on a single chip. Remember, Bluetooth operates in 2.4 GHz, and mioty is “sub-Gigahertz” meaning 868 MHz in Europe and 915 MHz here in the states. Hopefully for some of you, just knowing the frequencies involved have your mind going… Bluetooth is a pretty short-range PAN technology, while mioty can go much, much, much farther riding those 915 MHz radio characteristics of distance and penetration. Meaning that mioty can backhaul Bluetooth traffic to other parts of the same network over large distances. All from the same chip.

This is the kind of announcement I like, as it leads to me learning something.

But why the little m?

Damn You, CAPWAP Tunnels… Damn You All to Hell

There comes a time in every person’s life when they have to face the truth: maybe their CAPWAP tunnels that have been so good for so long actually have a dark side… Maybe them tunnels make you feel empowered, nay- maybe they make you feel invincible when it comes to creatively using VLANs in your overall Wireless LAN construct… and maybe someday that good thing leaves you in a bad place. Maybe.

Let’s pause for some lyrics from the immortal Waylon Jennings’ song “Wrong”:

I should have known it all along
When the future looks too bright can’t be anything but right
Wrong

Everything was going strong
The sky was always blue I thought my dreams had all come true
Wrong
Wrong

Let’s get right to it: CAPWAP TUNNELS SPOIL YOU.

You’ve been using a WLAN solution for a lot of years. It’s been buggy at times, the vendor has left you frustrated on countless levels. You’re thinking “shit I would freakin love to finally ditch controllers and that bloated, semi-functional NMS and move to a cloud WLAN solution for my thousands of wireless access points” – WAPs for some of you (shut it- you know who you are)… But then you run into the CAPWAP tunnel thing and a big honkin Layer 2 quandary down in your switches.

If I have a controller-based WLAN, I can get away with this at the AP uplink port, which clearly gets the Polly Pony Seal of Approval:

But alas, take away the CAPWAP tunnel construct and you are left with something less savory, and Cactus Mike isn’t digging it:

I gotta agree with Cactus Mike- in very large WLAN environments, the thought of no CAPWAP tunnels sucks ass. Sure, maybe a radical redesign of the LAN that underpins the WLAN would help, by pushing L3 out closer to the edge and reducing the need for VLANs. But such undertakings aren’t always a possibility, and if they are a possibility, the timing of redesign opportunities may not line up. Back to topic.

Am I suggesting that by going to a cloud-managed WLAN solution that CAPWAP tunnels aren’t possible? Yes and no… Some cloud vendors recognize Cactus Mike’s conclusion, others not so much. I have not actually used any of the following solutions, but I do appreciate that they recognize that “switching to cloud” and “ditching the controller” isn’t all that easy for those of us with CTA (CAPWAP Tunnel Addiction):

Arista:

Aruba: (link is here)

Extreme definitely has an answer but I’m not finding the right link. Will edit

Mist: (link is here)

Ruckus: (link is here)

By no means is this summary meant to be comprehensive. And, if you were to drill in to any of these, I’m not sure they would each stand up as an answer to “how do we ditch our current controllers, terminate VLANs somewhere, yet move the rest of the show out to the cloud while retaining our CAPWAP tunnels and not doing a massive L2 reconfiguration?” as I have not tested any of them.

But- I do appreciate that the situation is being recognized and addressed by major vendors. AND- I am surprised that at least one long-running pure cloud innovating powerhouse vendor has yet to provide an answer to the situation. As long as the only answer is to configure the uplink to a cloud-managed AP as if it was an old fat legacy access point, they won’t be getting an invite to Cactus Mike’s summer bash…

Your thoughts on the topic?

Interfering Personal Hotspots- Beyond Simply a Technical Issue

After 20-some odd years in the Wi-Fi business, I can safely say that I both love and hate personal wireless hotspots. Before I get into all that, let’s go back in time. If you want some zesty background, here are a few easy, compelling reads written by me from the way back machine:

If you don’t want to review the above links, here’s the poor man’s executive summary:

FCC: Don’t use de-auth frames- that equals jamming (depending on which one of our own definitions you stumble across). Selling jammers is illegal. We let Wi-Fi vendors sell illegal jammers because they provide tools that do de-auth. But that is illegal. You can’t sell jammers except when you can sell jammers. Confused? Shut up, or maybe we’ll fine your ass for our lack of clarity. Our annual fund-raiser is coming up- how’d you like to “donate” several thousand dollars?

Hotspot Makers: We use only the highest power and some really cocked up channel selection algorithms to ensure your device delivers the absolute finest in RF interference to the Wi-Fi environment you are sitting in the middle of.

Wi-Fi Alliance: BUY MORE WI-FI GEAR! FAT CHANNELS! GO TEAM! CRANK UP THAT POWER! WORK IT, YOU SWEET THANG! WE ARE AWESOME, JUST ASK US! IGNORE ALL THE STUFF WE SHOULD HAVE BEEN DOING FOR THE LAST 20 YEARS.

Network Customers, WLAN Admins: WTF?

It all makes perfect sense if you don’t think about it.

The Technical Frustrations

Anyone else in the biz knows that hotspots can be annoying, or they can be WLAN-killers. It all depends on the day, the device, the location, and the density of the WLAN where those hotspots are fired up. You can only play so many frequency-stomping games with spectrum, then physics shows through and Wi-Fi sucks for everyone until the contention is eliminated. This is the technical side of hotspot frustration.

And nobody of title has done a shittin’ thing to improve the situation- not the FCC, not the WI-Fi Alliance whose members make all of the devices that step on each other, not anybody. Everyone is in it for themselves… (Soapbox moment brought to you by the good folks at Shamwowsers & McKracken, LLC).

Ah well.

The Cultural Component to the Whole Mess

Cell phones and Mi-Fi devices have come soooo far since WLAN administrators first played whack-a-mole with hotspot-induced network issues. Data plans have also evolved, to the point where many of us are walking around with dual-band, unlimited data hotspots in our pockets ready to put into service at the slightest notion.

Let’s turn to rocker Ted Nugent for his take on the situation, as written about in his mega-hit “Free For All”:

Well looky here, you sweet young thing: the magic’s in my hands
When in doubt, I’ll whip it out. I got me a hotspot- dual-band
It’s a free for all

Or something like that… It ABSOLUTELY IS a free for all. That’s the culture right now. If I can’t get on the business network because I don’t know how to configure meself for 802.1X, I’m gonna WHIP IT OUT, Nugent-style, and get myself off to the Internet. The business Wi-Fi can suck it, and how dare you expect me to open a trouble ticket to get help with your 802.1X noise? THE MAGIC IS IN MY HANDS. Any collateral damage is NOT MY PROBLEM.

So what if your stupid police cars can’t transfer dashcam video because of interference? Why do I give two figs if your expensive Wi-Fi locks and clocks are acting up because of my RF pride and joy? Spare me the lecture on how your wireless VoIP handsets are getting walked on… Maybe YOU shouldn’t be using Wi-Fi-equipped medical devices. IT’S A FREE FOR ALL, DID YOU NOT GET THAT MEMO FROM TED NUGENT?

Hate ’em, Love ’em

Yeah, hotspots are a big fat PITA. They really do create problems. Some are dual-band, high power beasts that insist on obliterating your WLAN, while others seem to have a little more common sense and lower power built in, but in dense WLAN environments it still gets ugly.

But I’m here to confess that I too hear their siren song.

I get WHY people fire up their hotspots. At hotels, at camp, while troubleshooting systems that have potential ISP issues and so on. My phone’s hotspot gets it’s share of exercise, and I can’t imagine not having it available in a number of situations. But as a WLAN professional, I have the knowledge and (usually) the discipline to not hose up someone else’s WLAN with my hotspot when I’m at their place of business. Most people- not so much.

We’re way past the opportunity for THE INDUSTRY PLAYERS to responsibly to educate end users on why hotspots shouldn’t just be whipped out Ted Nugent-style. So we’re stuck with the problem.

Suck it up, Buttercup

What really sucks about all of this is that WLAN components are only getting ever more expensive. The tools that are used to design and support WLANs are only getting more expensive. Collectively, the security stakes in almost all WLAN environments are only getting higher. We can pump endless dollars and man-hours into delivering really good Wi-Fi, yet hotspots can lay waste to parts of our infrastructures, and there isn’t much anyone can do except to ask the offender to put them away, if we can pinpoint them and get them to listen to our appeal that they think of their fellow man…

Strange times, says I.

7signal’s Mobile Eye Demystifies the Client End of Wi-Fi

Given the widespread Work-From-Home reality that many of us are wrapped up in given COVID, network life has absolutely changed for both WLAN users and those who support them. Rather than everyone connecting to the workplace wireless network, we’re in a new age of VPN and a thousand different workers connecting through a thousand different home Wi-Fi connections. No big news here, right? But it needs to be pointed out in the context of support.

As a WLAN architect, engineer, and administrator, I have easy views into all network building blocks in the typical enterprise setting when it’s time to solve end-user problems. But think about how that paradigm changes when all the workers go home, still need to do their work, but now connect to “living room networks” built on who-knows-what network equipment and ISP connections of every range of speed and capacity.

Mobile Eye Bridges the Gap

Among those home-bound employees using Wi-Fi, problems are inevitable. And just like when we’re all at the office, connectivity issues mean lost productivity. While we in the support role aren’t going to drive from house to house doing mobile support (you might, but I’m not), we might want to consider the likes of Mobile Eye, a software-based monitoring tool from 7signal.

From a single cloud-hosted Mobile EyeQ dashboard, those of us doing support have pretty deep views into those far-flung home environments (it’s just as effective in central environments where we don’t have rigid control over client devices) and can “roll the tape” on WLAN factors that may be mucking with the experience of remote users.

How Might You Leverage Mobile Eye?

After running Mobile Eye in test for a few weeks on half a dozen devices on multiple Wi-Fi networks in a couple of different locations, I can say that I would love to have it on all mobile workers’ devices. But it doesn’t have to be all or nothing by any stretch… maybe only key people who simply cannot be down for very long get a Mobile Eye agent so when trouble hits, we can have the contributing factors already recorded. Or perhaps you deploy it to users short-term for diagnostics and troubleshooting as users need help- all data is good and you’ll get deep live and reportable trended insight regardless of how you employ it.

Learn More

After a long gap of not following 7signal’s evolution very closely (we all get busy), I caught one of their almost-zero-salesfluff Friday product intros, and it was time well spent. I had gotten to know the company fairly well back in 2013 when they presented at Wireless Field Day, but so much has changed since then that the Friday tour was an excellent catch up.

_______

Other: There are a lot of resources and WLAN knowledge aggregated at the 7signal web site. They have been in the WLAN performance game for quite a while. I have been fortunate to present for a few of their webinars over the past several months.

Linksys Leverages Tanaza for Cost-Conscious Cloud-Managed Wi-Fi

You’ve heard of Linksys, everybody has. But Tanaza? Is that an energy drink? No, but it is what fuels Linksys’ latest go at cloud-managed Wi-Fi. Let’s get the Tanaza thing out of the way first, then we’ll talk about what Linksys is up to (if you’ve had with expensive vendor license paradigms, you’ll want to read on).

Tanaza Explained

Tanaza – Logos Download

Tanaza is a cloud-managed networking platform based in Italy, I’ve been tire-kicking and following the evolution of the Tanaza system for a while now, Here’s a blog I wrote on Tanaza, to get you started. I like the company, their people, and the UI. As an enterprise WLAN guy myself, I sometime have to stretch my mind to get the appeal of a company that (so far) only manages Wi-Fi and not “the full network stack”, but once you get that it’s easy to appreciate Tanaza’s effectiveness. Recognizing a company’s Wi-Fi as the thing that many SMB customers interact with the most with, Tanaza makes providing well-managed and feature-rich WLAN environments easy for single sites or distributed locations likely served by MSP types or savvy in-house staff that need the most for their precious network budget dollars.

Linksys Cloud-Managed Wi-Fi 2.0

As a reminder, Linksys is part of Belkin, which is part of Foxconn. You of a certain age may be pre-disposed to think of Linksys as a home router vendor, but the company has long since evolved to having business-grade products in several spaces. With its latest strategy for cloud-managed WLAN, Linksys replaces it’s old in-house magic with Tenaza’s very polished dashboard and management framework and pairs it with a so-far modest handful of decent indoor 802.11ac wireless access points.

So what is the actual news here?

Tanaza has the cloud-management thing down pretty well. The case can be made that Foxconn/Belkin/Linksys using Tanaza’s framework validates Tanaza’s suitability for the SMB/MSP masses. The Linksys empire includes manufacturing, support, various channel relationships, and the ability to capitalize on Tanaza’s native cloud goodness to offer a decent SMB solution at compelling prices. And what makes those prices compelling? Probably the biggest selling point is that no licenses are required when you compare to other cloud-managed solutions. In my opinion, many of the bigger guys have gotten so license-happy they have priced themselves out of the SMB market.

Good Stuff, But Is It Enough?

Linksys Cloud Management 2.0 promises unlimited scaling (again, think MSP), easy pre-configurations and new access point adds (think Meraki-style), and has a good road map for options that will help customers to either directly or indirectly monetize their guest WLAN environments. All that sounds good when you can get it for cheap with no licenses, and I will say that the Tanaza access point I’ve been running works well. But I also can’t help but think that sooner or later “cloud managed Wi-Fi only” is going to be an issue for some potential customers. Even Open Mesh, before they were acquired by Datto, had a pretty effective cloud managed switch and edge router offering to go with their wireless APs, as does Ubiquiti- who is always the elephant in the room in this space. An outdoor AP option with external antenna capabilities would also be nice.

Linksys Cloud Manager 2.0 web page

Synology NAS Ramblings

A few years back, I got turned on to the world of Synology by networking pals who employ these impressive devices in their home setups (though Synology has it’s share of devices out there in business settings as well). I’m far from a “power user” in NASland, but I continue to learn more about Synology’s NAS capabilities as I go. Let me share a bit on my recent goings on.

One Big, One Small

I’m currently using two NAS devices. One is the low-end two-bay DS218j, and the other is the more beefy DS1618+. I’ve set mine up as 4 TB and 10 TB with decent disk resiliency, but you van go much bigger on either.

Why two? The little guy is primarily a repository for decades of family pictures, videos and such. I went this path after some frustration with online repositories. It’s easy to add to the drive whether on the LAN or out on the Internet, with multiple user accounts and home spaces. The larger unit is an important part of Wirednot, LLC, where endless drone footage, documents, proposals, white papers, software etc are stored and frequently accessed.

Each is a “private cloud”, if you buy into that notion.

Wake on LAN is a Must

Every now and then our local power company causes us some grief during a thunderstorm or some such. When power comes back, it’s nice to leverage Wake on LAN to not have to remember to go downstairs to the Command Center to power up these units. I highly recommend it

It’s Not Just Storage Here… Let’s Whip Up Some CCTV

Though “NAS” is network attached storage, there are so many cool features you *could* do with Synology. There are dozens upon dozens of “packages” that can be installed, making this NAS morph into a many different servers and appliances all at the same time. I haven’t leveraged much beyond storage and file services, until recently.

I bought a low-end IP camera for a specific purpose (weather station companion camera) that it failed miserably at. I can’t tell you all the ways that JideTech cameras are cheap Chinese junk with horribly built software sides, but I was able to turn disappointment into a productive experiment using my Synology NAS and it’s Surveillance Station application.

I have installed, used, and continue to support a handful of different CCTV systems. Synology’s free surveillance system kicks ass versus the likes of Hikevision, accommodates a decent variety of cameras (including generic configs like I used to get El Cheapo to work) so has that advantage over closed systems like Ubiquiti’s Protect (which I love), and has a powerful range of features on par with upper-end enterprise systems like Genetec. You get two camera licenses included out of the box, then need to pay as you grow. But it’s really a nice feature you can simply enable on your NAS, and it makes my Chinese shitcam look good. Retrieving past recordings is a snap, and the UI is just shweet.

Add Some RAM- If You Can

I read somewhere that added RAM can make your Synology more snappy, and have felt some lag on occasion when interacting with both of my drives… little things like slow-feeling logins and population of file menus kinda stuff. So, for the first time in years and years I found myself adding RAM cards to a computing device- but in the case only the 1618+ was eligible.

Synology models ending in “j”, like my little 218j, are out of luck when it comes to RAM expansion. Here’s where you have to be careful, as Synology has a 218+ and a 218j. Plus models can do RAM upgrades, J models cannot and so I will live with 512 MB of DDR3 on my small drive. I expanded the 4 GB that came on the 1618+ to 16 GB, and the result was impressive. EVERYTHING I do on bigger drive is peppier.

That’s it for now. Nothing remarkable going on here, but if you are contemplating buying a NAS, Synology has served me well so far and has a lot to offer. Definitely spend a bit more and get yourself a + model.

If you are doing anything cool with your Synology, I’d love to hear about it. These things are so versatile, it can be hard to know what to do with them beyond storage/file stuff.

A Very Robust, Funky Power Outlet Tower

The product is called the T1, the company is Eshldty (I’m not even going to attempt to pronounce). It’s a power outlet tower… big deal, right? Lots of those on the market. But this one has some unique features in a compact package that I can see being welcomed at home and in a number of business settings.

With 9 outlets, 3 USB ports, one USB-C, you get a lot of charging capability in a well laid-out form factor that takes up little table or shelf space. But… it’s still just a power strip, no?

Let’s get to what made me want to look at this thing.

No, the T1 didn’t work up a sweat here pushing volts- it’s made to be used in wet environments. It’s marketed as both splash-proof, and waterproof, and if you dig in to the companies videos you’ll see them heaving buckets of water at it and even sticking metal tweezers in the outlet to show it protects itself against short-circuits… I can’t promote those experiments as my history and training with electricity won’t let me participate in potentially enabling bad habits. But I did play around a bit with “how night this be beneficial in the real world?” scenarios.

Being a husband and a father, sometimes I’m astounded at how many electrical gadgets make their way into the bathroom. I’ve camped and done outdoor activities where rain and such is inevitable. And I’ve been in restaurants and airports where those cleaning tables and floors frequently push a fair amount of soapy water fairly close to outlet strips on tables, kiosks, and other public areas. All of these might be good fits for the T1’s weatherproofing, and it also is touted as flame-resistant.

Now for the fun stuff: The T1 has a cool embedded LED lighting array that will either react to sound with random multi-color patterns, or you can put it in any one of several night-light or idle patterns. I had more fun with this than I should have in testing.

The unit is built well, and I have come to generally prefer the tower approach to power outlets over strips in general. The USB ports on this seal the deal for me, and I can see it being perfect in hotel rooms as well.

Here’s the official specs from Eshldty :

– IPX6 waterproof
– Built-in RGB Music Rhythm Light, 9 special color effects
– 9 &12 fully protected outlets (model-dependent) can be used simultaneously without interfering with each other
– Support Fast Charging, Includes 3 USB outlets that support 2.4A fast charging and a Type-C port with 20W PD fast charging (Type-C port is designed to charge the new iPhone 12)
– ETL Listed and FCC Certificated

The T1 is brand-spanking new to the market. Here’s where you can find out more. I don’t tend to get all that excited about consumer-grade products like this, but the T1 really does have the potential to fill other niche scenarios as well.

Celona Tees Up Bigtime on CBRS

Private 5G networking has been discussed a lot over the last year. Engineers and installers are getting trained on design, installation, and support. Though it’s not exactly a new topic, it is still fairly exotic. It’s like we’re all kind of waiting for CBRS to take some big, meaningful step forward that signals “OK, it’s really finally here. Really, like for real.” With Celona’s latest news, that big step has arguably just been taken.

Back in February of this year, I pondered on the past and short future of CBRS in this blog. I’ve gotten to know Celona (the private mobile network company) up close and personal at Mobility Field Day events last year and in 2020 and through a number of private briefings. From where I sit, the entire CBRS and Celona thing has been kind of a slow simmer- waiting for things to break open and get real.

We’re there now.

Platform, Products

Celona is ready to rock and roll the CBRS-hungry enterprise crowd with all the makings of a build-it-yourself 5G networking solution. The details are here, but the short version goes like this- product components of Celona’s integrated solution architecture include:

Celona RAN: Indoor and outdoor CBRS LTE access points built for Enterprise environments. They provide up to 25K indoor sqft and 1M outdoor sqft of coverage. Radio functions are fully automated via Celona software with their power level and frequency channel assignments in the CBRS spectrum, no manual configurations required.

Celona Edge: Private LTE/5G core Enterprise appliance that’s designed to integrate with any existing network environment. Deployable on-premises for strict SLA enforcement for local applications, within private / public / edge clouds for service scalability, or both.

Celona Orchestrator: The AIOps platform that enables remote installation of Celona’s access points and Edge software, across multiple enterprise sites. Orchestrator provisions Celona SIM cards against required device level access control policies within the enterprise network. Providing more than monitoring of infrastructure components, Orchestrator also keeps track of application and device KPIs for Celona MicroSlicing™ (think QoS on steroids, but there’s more to it than just that).

Everything you need to build your own private 5G environment.

Aruba Networks Partnership

Celona has also formed a partnership with Aruba networks, who will sell Celona gear where a given customer is looking for not just Wi-Fi but also private mobile networking. Given Aruba’s lofty position in the WLAN space, this is a good thing for Celona as they set out to conquer this new market.

A Fat Wad of Series B Funding Never Hurts

Not that further validation that Celona is doing things right is needed, but one could argue that the cash the company has just secured is another indicator that industry is taking both Celona and their new tech solution seriously.

There are some decent folks at Celona that I’ve known in different roles at other companies, and it’s exciting to see them move their collective vision forward. I’m looking forward to seeing how this unfolds for Celona, the fledging CBRS industry, and for the customers about to go down this road.

See the new Celona Platform.

Wyebot Brings Wi-Fi 6, More to Its WLAN Monitoring Platform

I’ve been using and evaluating Wyebot in different wireless environments for the last 18 months or so. One of the things that I most like about the company behind the sensor product and their Wireless Intelligence Platform (WIP) is their willingness to listen to what tech-savvy customers want, versus just adopting the mindset of “we’ll tell YOU what you need in a dashboard” that comes with competing products. My own requests have helped to shape the product, and I’ve listened in on calls where other wireless processionals have described what they feel is important. Wyebot listens, and iterates where it makes sense while not necessarily duplicating what everyone else is doing, or diluting their core strengths by trying to be all things to all people. This strikes me as a small, smart, agile company with a good product (and some good competition). My past coverage:

Now, we have a new 802.11ax sensor and version 3.1 code to improve Wyebot’s already impressive capabilities of WLAN/LAN characterization, troubleshooting, and alerting.

Continuous Improvement

Here’s the latest incarnation of the main page in the Wyebot dashboard, to get the juices flowing:


Whether you install Wyebot sensors for long-term monitoring, or use them more in a tactical role for point-in-time troubleshooting, there is a lot to appreciate. I love that with three radios, you get the flexibility of using wireless backhaul from the sensor when no network wiring is available. But what about the new magic in 3.1?


Unfortunately, you have to be logged in to see the details of each feature, but most of these are probably fairly intuitive to those in the business of Wi-Fi. Let’s talk about a couple.

Access Point Classification Feature

The Wyebot sensor does a fantastic job of characterizing a given WLAN environment. You may see a list of SSIDs on your phone or PC, but Wyebot will distill it all down to how many APs are in each SSID (within it’s receive range, of course) along with all of the 802.11-related particulars you’d ever need to know. From there, you can add your own classification- is it a friendly? A threat? an unknown? Sounds simple, perhaps, but this on-the-fly graphical note-taking with security overtones helps keep busy environments straight as you pick them apart.

Available Test Profiles

At the bottom of the list of test profiles, we see a new option- Link Doctor. With this, you exercise core network services and device-to-destination connectivity to get a sense of network health. Run it on demand, or at regular intervals for trending.

Hopefully you get a taste for Wyebot’s look, feel, and general aspirations as a test and monitoring platform. For a more analytical look at the entire platform, check out this presentation from Bryan Daugherty.

What Do I Like Best?

From the first time I experienced Wyebot, I fell in love with a few aspects of the sensor and it’s cloud framework, That affinity continues, and here’s what keeps me smitten:

  • As a permanently-mounted sensor, Wyebot would be welcome in any WLAN environment. But to me it has as much value as a pop-it-in short-term analysis tool, almost like a NetAlly hand-held product. Even if you don’t buy into sensor overlays, a Wyebot sensor two on hand could bring unique troubleshooting value.
  • You just don’t get as many false alarms with Wyebot as you do with certain competitors.
  • It’s awesome to take wireless packet captures gathered elsewhere and to load them into Wyebot, and have them displayed as if Wyebot did the capture. Pretty slick.