The CaNerdIan

Way back in the olden days before the world shut down (but only very shortly before), I had an inkling of an idea whilst returning to the USA aboard a cruise ship whose Wi-Fi refit I was commissioning.

(Apologies, this was stuck in the draft queue for a hot minute, I mean, year… ) OK, so it’s been a few months since my original post about the new generation of Ubiquiti gear, but in that time I started a new job that has me traveling every other week, and

Having spent most of the last 5 years steeped in the HPE/Aruba networking ecosystem, I didn’t pay much attention to what Ubiquiti has been doing, as their primarily Prosumer and small business market segment didn’t significantly overlap with the large glo…

A while back, I posted about how to set up an Aruba wireless bridge using the built-in mesh method.

Yep.

If you’ve been using Ekahau for a while, you probably already know how painful it can be to generate a list of APs from within a custom report template - and even then, it’s not the most useful thing in the world just for being in Word format.

If you’ve done a few post-install validation surveys with Ekahau, you’ve probably run into the dreaded “Measured AP-a1:b6”, even if your AP/ESSID were supposed to have AP name broadcast in the beacon (or you just forgot to turn it on before surveying).

One of the most underrated features of Aruba wireless hardware is its ability to be used as a wireless bridge.

In my previous posts about the ArubaOS API, I’ve given a general framework for pulling data from the AOS Mobility Conductor or a Mobility Controller.

Another quick bit today - this is the basic framework for using the REST API in ArubaOS.