When Your Tools Don’t Agree: The Ubiquiti Wave Pro Headache

There’s nothing quite as frustrating as trusting your monitoring tools—only to find out they’re telling two completely different stories. That’s exactly what happened during a recent Ubiquiti Wave Pro deployment. I was working the install remotely, checking the unit through the web interface, when it suddenly showed the 60 GHz link as down. Naturally, that set off alarms. A down link means troubleshooting, delays, and a big headache. But then I got a message from my onsite tech saying, “Everything looks fine here—the link is up.” That contradiction alone was enough to make me question my sanity.

At first, I assumed it had to be a syncing issue or maybe a firmware glitch. But the odd part was that the Bluetooth app on-site was showing completely different information from the web interface. Two official ways to access the exact same device—and somehow they couldn’t agree on something as fundamental as link status. When you're depending on accurate remote visibility to keep things moving, this kind of mismatch isn’t just inconvenient—it’s a recipe for wasted time, unnecessary troubleshooting, and serious deployment delays.

So, I tried to open a ticket with Ubiquiti support, expecting at least a “try this” or “here’s a workaround.” Instead, their response was almost surreal: they openly admitted it’s a known issue with no ETA for a fix. Not a minor bug, not a cosmetic glitch—an outright discrepancy between their own interfaces on critical link status. Even the support chatbot echoed the problem, saying, *“Based on your description, there may be a discrepancy between what UISP and the radio’s web interface report versus the Bluetooth app.”* It then pointed me to a general WiFi optimization guide that had nothing to do with the issue at hand.

In the end, the whole experience left me shaking my head but at least i knew it was a bug. When you're deploying gear like the Wave Pro, accurate diagnostics aren’t optional—they’re essential. Having to second-guess the device’s own interfaces shouldn’t even be on the table. Until Ubiquiti sorts this out, anyone managing Wave Pro deployments will need to rely heavily on onsite checks, because the remote view just can’t be trusted. It’s disappointing, avoidable, and honestly, not what I expect from equipment at this level. 

---

The next outage is coming – is your organization prepared?

Click the image for the article

from the web: Everything you wanted to know about Access Lists

 

What Access List? What is standard ACL, extended ACL, named ACL, and what is routing protocol ACL? What is a time-based ACL? How to configure ACL?

What is Access-List?

Access-List or ACL is a set of rules which will allow or deny the specific traffic moving through the router. ACL is defined as controlling network traffic and reducing network attacks. ACLs are used to filter traffic based on the set of rules defined for the IN to the router or OUT to the router of the network. An ACL would be your tool of choice for decision-making for example you can se....

Click on the image for the full article

Blast from the past - The Unidisc

 

The disc is metal and the whole thing weighs 2.9 kg (6 lbs, 6 oz) and stored 2 MB in 1996.

If you were a computer enthusiast in the late 1970s or early 1980s, you may remember **The Unidisc**, a quirky but clever attempt at solving one of the era’s biggest headaches: incompatible disk formats. Back when every computer manufacturer believed their floppy disk system was the one true path to digital enlightenment, The Unidisc showed up like a universal translator for storage media. Designed to read and write multiple floppy formats, it became a surprisingly essential gadget for anyone juggling CP/M machines, early PC clones, or that one weird computer your uncle bought from a mail-order catalog. One lesser-known bit of trivia is that The Unidisc often found itself used in small businesses that were transitioning from older dedicated word processors to microcomputers. Rather than retyping mountains of documents—a fate worse than dial-up speeds—they used The Unidisc to transfer data from one platform to another. In an era before USB flash drives, cloud sync, or even reliable networking, this thing was basically the Swiss Army knife of floppy drives. And like any Swiss Army knife, half the time you didn’t know what all the tools did, but you were glad they existed anyway. Another fun fact: enthusiasts still mention The Unidisc in retro-computing forums today, usually followed by a story that starts with “You won’t believe what I found in a box in my parents’ basement…” Many collectors swear by its durability—remarkable considering that modern gadgets beg for a protective case just to survive a gentle breeze. The Unidisc, on the other hand, seems to have been built out of the same material used for 1980s school desks and indestructible lunchboxes. You could drop it, stack things on it, or ignore it for 25 years, and it would probably still spin up. Of course, the true charm of The Unidisc lies in its accidental comedy. It promised “universal compatibility,” which was ambitious for a world where every company wanted proprietary everything, down to the screws. Using it sometimes felt like convincing rival kingdoms to sign a peace treaty—magnificent when it worked, mildly tragic when it didn’t. But when that clunky, glorious machine actually transferred your files without arguing, it felt like magic. Today, it’s a delightful reminder of a time when “plug and play” was more like “plug and pray,” and every working data transfer felt like a small personal victory.

---

Since the testing with the blog site is going so well, there is a good chance networkdatapedia.com name will be pointing here in the new year.

If you want to get weekly email updates - no spam..  

make sure you subscribe by filling out the contact form on the right with the word subscribe and i will add you to the list.

from the net: Aisuru botnet behind new record-breaking 29.7 Tbps DDoS attack

 

In just three months, the massive Aisuru botnet launched more than 1,300 distributed denial-of-service attacks, one of them setting a new record with a peak at 29.7 terabits per second.

Aisuru is a huge botnet-for-hire service that provides an army of routers and IoT devices compromised via known vulnerabilities or through brute-forcing weak credentials.

Internet management and infrastructure company Clou...

click the image for the full article

Linux cp command reference sheet

 

Technical cheat sheets are one of those things you don’t truly appreciate until you’re knee-deep in a problem and need the right command right now. When you’re working with Linux—especially with command-line utilities like cp—even seasoned pros can blank on syntax or flags. A good reference sheet acts like a mental shortcut, giving you instant access to the commands you use often, the ones you occasionally need, and the obscure options you’ve inevitably forgotten. Instead of digging through man pages or searching the web, you have the essentials neatly distilled into something you can scan in seconds.

Beyond convenience, cheat sheets dramatically cut down the cognitive load of technical work. Linux commands tend to pack a lot of functionality into short syntax, and remembering every flag (-r, -v, --parents, --no-clobber, etc.) isn’t a realistic expectation—especially when you're switching between tasks all day. A good cheat sheet reduces that mental juggling. It lets you focus on solving the actual problem instead of second-guessing whether you’re about to overwrite the wrong directory or miss a crucial flag that changes behavior. That reduction in friction adds up to faster, more accurate work.

There’s also an incredible amount of invisible effort that goes into creating a solid technical reference sheet. Anyone who has made one knows it’s more than “just jotting down commands.” You have to test each use case, verify edge behaviors, compare different versions of the command across distributions, and decide what’s essential enough to include. It’s a balance between completeness and usability. Too little info, and it’s pointless. Too much, and it becomes another overwhelming document no one wants to use. Curating clean, reliable, concise technical guidance takes real time, technical depth, and often several iterations.

Finally, cheat sheets become valuable assets not just for the person who creates them, but for entire teams. They help standardize how tasks are performed, reduce onboarding time for new staff, and minimize errors caused by inconsistent knowledge. When dealing with something as powerful—and potentially destructive—as Linux file operations, having a tested and trusted reference isn’t just handy; it’s a safeguard. The payoff is huge: smoother workflows, better accuracy, and a more confident technical environment. In short, technical cheat sheets are small tools with big impact.

Just click on the image to get the full screen view

From Dan Nanni www.study-notes.org

---

Yup, we're on Facebook, 

https://www.facebook.com/groups/24900262876244964