WLAN Channel Management F1 Style: Part 1 of 3

We keep saying that overlapping channels are not good – they create unnecessary interference, contention, or both (depending on the distance between the APs). It is a general recommendation to stick to non-overlapping channels and actively hunt and eradicate anyone who overlaps. However, are overlapping channels always bad?

A typical example of a channel that overlaps with every other!

In this 3-part series I’ll be talking about some channel tuning techniques that may allow cramming more channels in the RF plan, have them overlap – and still get overall better network performance. A valuable LinkedIn member Eduard Garcia-Villegas (who is doing some interesting research in WLANs) had recently provided me with some interesting papers that offer theoretical foundations and practical proof behind this. What does it have to do with F1? Let’s find out!


ShellShock and Motorola WLAN Equipment

A tech support article has been published on Motorola’s support portal regarding ShellShock vulnerability. A brief note:

  • APxxxx, RFSxxxx, WSxxxx, CBxxxx (existing and legacy) – NOT vulnerable, as they don’t have bash at all.
  • NXxxxx and VXxxxx – KIND OF. They have unpatched bash, but it’s not exposed through any APIs/UIs unless you already somehow get the shell (which defeats the purpose of this vulnerability). Nevertheless, “Never say never” and a patch will be released in due time just to be sure, but there’s no rush.

Source: What Motorola products are affected by Bash/Shellshock vulnerability?

Harnessing Android Intents

This post is about Android Intents, and how to use them to start/stop/show/hide Android apps and services and perform some more advanced actions. Intents are the glue that binds numerous Android components together, and are very important for understanding and mastering various aspects of Android. Main goal of this guide is to understand enough about intents in order to be able to use them in ADB scripts and other tools that allow sending Intents.