Sat down With JJ Mcgrath and Eric Sooter at the Mikrotik User meeting in Autin for a little “
Sat down With JJ Mcgrath and Eric Sooter at the Mikrotik User meeting in Autin for a little “
Sat down With JJ Mcgrath and Eric Sooter at the Mikrotik User meeting in Autin for a little “
We recently did a job for a grad student at Purdue University. His project involves using iOT sensors to collect data from things such as soil, air, and other sources. This helps with farming.
A while back I did some posts on the Ubiquiti networks Aircube.
While cleaning my office I figured it was time to plug this guy back in and do a check of the new firmware. As soon as it was online, I logged in and was greeted with a firmware update message. I like it when this happens.
After just a few short minutes of verifying and then upgrading I was able to see what was new. I have to say the firmware has come a long way. I am not surprised, as I reviewed this product early in its life. I was expecting things to get better and better and they did.
We now have PPPoE on the wan, a more unified dashboard, VLANs, UNMS, and VLANs. For those of you with UBNT networks, this fits as a managed router nicely now.
Our buddy Willie Howe has a new video about Edge Router best practices. Check out his blog post here.
Your flash briefing for Thursday, February 7, 2019
Potential Misuse of ARIN unmet requests list
At their business meeting in January 2019, the ARIN Board of Trustees,
in light of the potential misuse of number resources under NRPM section
4.1.8 (Unmet Requests), suspended issuance of number resources per NRPM
section 220.127.116.11. (Fulfilling unmet needs), and referred NRPM section
4.1.8 to the ARIN Advisory Council for their recommendation. ARIN will
complete open transactions to waiting list organizations where IPv4
addresses have already been approved pending fee payment.
5G isn’t the answer for rural broadband
Verizon halting 5G home deployments
UBNT – https://blog.ui.com/2019/02/04/airos-v1-1-2-for-af-5xhd-now-available/
Disclaimers. I have been in the ISP world since 1991. I cut my teeth on BBS systems and moved onto dial-up. I am also an independent Cambium certified consultant. Read about the consultant program here... I also have clients who run a wide variety of UBNT products, and the last ISP we sold was 90 percent UBNT. We run some UBNT routers in MidWest-IX as well. My father was an attorney for over 40 years. I grew up around attorneys, have regular conversations with friends who are attorneys, and was learning about the law from the time I was 10. Having said that, I am not an attorney. Nothing in here should be construed as an official legal opinion.
So let’s get some background on what has transpired with Cambium and their elevate software. Cambium came up with a way to load their software onto select UBNT wireless units and, after a reboot, had the cambium EPMP software active on them.
Why did this work?
UBNT Airmax radios use U-Boot loader. If you want to read all about it you can read the references at the bottom of this article under References. The thing to know is it is released under the GNU General Public License.
UBNT and Cambium EPMP both use “commodity” wifi chipsets. This keeps the cost down and the software becomes the majority of the “special sauce” that makes them different. This is in contrast to the UBNT Airfiber and Cambium 450 lines. These use custom made chipsets. This is is one reason those lines are more expensive.
By using an open source bootloader and commodity hardware Cambium was able to figure out how to load their own software onto the UBNT devices. UBNT countered with modifying the bootloader to accept only signed software images. The only images that were recognized were ones signed by UBNT. If you are interested in learning more about signed software go here: https://www.quora.com/What-does-signed-firmware-means
Cambium came up with instructions on how to downgrade and by-pass the ability to only load signed firmware onto the device. The method I am aware of is downgrading the installed UBNT firmware to a certain version.
All in all the Elevate process turned the UBNT hardware into a device running Cambium’s software.
The gray areas aka this is why we have attorneys
There are several arguable points in this lawsuit. If you want to read articles on the Lawsuit
Debate #1 – The Hardware
The term Software Defined Radio (SDR) has been around for quite some time now. Basically, this is a radio with very little RF elements to it. Ham radio has been using SDRs for quite some time now. The idea is the manufacturer uses off the shelf components to build a single radio which can do various functions depending on what software is loaded. It also allows features in the chipset to be activated and licensed should the programmer want to support them. It’s interesting to note Wireless is not the only place this is happening. Software Defined Networking (SDN) is a growing thing, as well as a plethora of devices. A PC could be considered a software-defined device. More on that later.
So an argument could be made the UBNT devices are a software defined radio. they did not use custom chips. They most certainly have a proprietary board layout, but that is not a criterion in an SDR. So if a customer buys a piece of hardware, should they be able to load whatever software they want on it?
An argument saying yes they should can be pulled from many areas. This Verge Article (more in the reference at the bottom) says the Government ended the debate in 2015 giving consumers the ability to Jailbreak their phones and devices without legal penalties. Before that is was briefly illegal to “Jailbreak” your phone. This was mainly lead by Apple. The government said it was fair use to Jailbreak, but not carrier unlock your phone without permission.
Apple also went through this briefly when they switched to Intel processor chips. People were figuring out ways to load Apple OSX onto Dells, HP, and other “PCs”. The debate was whether this was legal or not. The following article sums up why these “hackintosh” computers were shut down. By clicking on the “Agree” of the End User License Agreement (EULA) before installing OSX you agree to a great number of things. The short of it was the user license of OSX says you can not install this on non-apple hardware. However, it says nothing about installing non-Apple Operating systems on the hardware. Apple knows it is commodity hardware. If you want to buy a 2000 mac and put windows 10 on it, go ahead. They even help you with an option called Bootcamp.
Our last example is the Linksys WRT54G and DD-WRT and its variants. A quick history of the DD-WRT Controversy doesn’t revolve much around the loading of the software onto Linksys hardware, it involves the use of the GPL license by DD-WRT. There were some FCC concerns, but we will talk about those later.
So the questions to be argued for this point:
Q1.Is the UBNT device a software-defined Radio?
2. Does the user have the legal ability to load whatever software they want to on hardware they own?
Debate #2 – Was the UBNT firmware “hacked” as they allege?
There are lots of unknowns here. Attorneys try to prove intent in arguments like this.
Did Cambium somehow reverse engineer the UBNT software, thus violating copyright laws? At what point is the line crossed? Since UBNT used a bootloader free to everyone, was the simple act of loading new software onto the units a hack? From what I know, and I am not a programmer, is Cambium used the bootloader to overwrite the UBNT software and install their own. How is this any different than installing Linux on a Dell PC? Computers have a bootloader called a BIOS. On a Wireless radio, where does the bootloader stop and the software start? To me, these are clearly defined. Bootloader and Image file.
If you boot up the UBNT unit out of the box without agreeing to the EULA have you violated the EULA? Can you be penalized for loading software onto a device you never had the opportunity to see and agree to anything? Did the simple act of taking it out of a box and booting it up via TFTP cause you to agree to something?
In a Brothers Wisp video on this topic, Justin Miller mentions some arguments on why this can be allowed.
Debate 3 – Did Cambium violate FCC rules?
If we believe the user has the ability to load software onto units they own it is the user, as well who developed the software to go on the device, to follow all laws then it is not up to UBNT to police this. This is the job of the FCC, provided it is agreed that once the user buys the hardware it is theirs. For this specific case, UBNT claims Cambium is violated allowed power limits by loading their software onto the UBNT device. Also, is the new device an FCC certified system? Most likely not unless it is resubmitted to the FCC for testing, and any labels removed and new ones added. However, this is not up to UBNT to enforce this. This is the job of the FCC.
Is UBNT being a steward of the community to bring this to the attention of the FCC, thus saving UBNT from possible issues with the FCC? Maybe, but why not bring suit against any of these others?
It’s interesting to note this page on HamNet
I am not a telecom attorney and I do not know the ins and outs. From what little I know of being in the industry you have to have an FCC certified system with proper identification stickers. I remember when UBNT had to send out stickers for units several years ago for DFS certification. You were supposed to put them on all your upgraded radios to be compliant. By changing the software did Cambium no longer make it a certified system? Or, because they use the same chipset is it still legal in the eyes of the FCC?
Debate 4 – Collusion and the end user
This is the biggest bombshell out of this whole ordeal and actually makes my blood boil. UBNT is suing Cambium of course. They are also suing a distributor and an end-user ISP. Cambium I can understand. UBNT is trying to protect their intellectual property and believe it was violated. They have every right to do so.
The distributor I can understand the argument. The distributor allegedly participated in distributing the “hacked” software. Not saying it’s right or wrong, but I can see why there would be the argument.
The most disturbing part of this an end-user ISP is named in the lawsuit. UBNT is suing a customer who was using the UBNT product and then decided to switch to a competitors product. In the case of elevate, the end-user ISP loaded the software onto their existing hardware. If we go along with the idea of you own the hardware, UBNT is suing a customer who bought their hardware and loaded the elevate software on it. This would be like Dell suing a school corporation for loading Linux onto new PCs they bought.
Many of the arguments you read are about you don’t own the software. If you buy the hardware, and it has a GPL licensed bootloader and load your own software onto the device, what laws have you violated?
Imagine this scenario. A user opens up a UBNT radio they bought. They see it uses an Atheros chipset, like many other radios. They write some code to talk to the hardware, all without ever looking at the software that came on the radio, boot up the unit via TFTP and load their own compiled image onto the hardware. All the while they never have seen the UBNT software. Did they violate any laws or user agreements?
This case and some others will help define who owns the hardware. We know the company, in this case, UBNT, owns the software. You have no legal standing to de-compile their intellectual property. That is cut and dry. What isn’t, is if they are using the same hardware everyone else, the same bootloader, is that considered proprietary? If not, and you overwrite their software were you allowed to because you own the hardware. Is the GPL bootloader considered proprietary? If we apply the analogy the bootloader is the same as the BIOS in the PC, no it is not proprietary. The BIOS debate has already been solved in court. Many of the PC debates have been loading a company’s software onto other hardware, such as Apple Hackintosh Computers and not the other way around, such as this case. As we talked in point 1, in the PC world, Apple even gives you the tools to install other Operating systems.
If UBNT sticks code in that says the bootloader only recognizes signed images is that “hacking” to put your own software on? Is this any different than Jailbreaking an Iphone?
So what does this all mean?
Going forward I believe we will see EULA and licensing agreements change. The hardware from a manufacturer will still be the property of the manufacturer, much like John Deere software.
The definition of what you own and have access to will change.
Proprietary bootloaders will take the place of Open Source bootloaders.
There will be a rise in manufacturers who make white box radios. Will there be a long-term solution? Only time will tell. We are seeing this trend in software-defined networking.
We will see more NDAs to end users about products. I believe we will see fewer case studies on newer products. End users will definitely be more tight-lipped about what they are doing.
So it will be interesting to see how this all plays out. Will there be enough precedent in the hardware world to squash some of this? Or does UBNT have a case? Obviously, UBNT has a responsibility to their shareholders to vigorously defend their Intellectual property. This case will help define where the commodity/open source items stop and where the intellectual property starts.
Where does this leave distributors? Do they want to continue carrying the Elevate product? Do they want to cut relationships with a manufacturer who has sued one of their own? The same goes for the end-user community. Do WISPs want to do business with a company that could potentially sue them for using and talking about a competitor’s product? Do the end users own the hardware they buy? If so, how much freedom do they have? If you don’t own the product, imagine the accounting ramifications.
Feds okay iPhone Jailbreaking
Is the Bios an Operating System?
Google Chromium OS
There has been much discussion on the performance of going from an N Series outdoor wireless system to AC. Not all AC is created equal. Right now there is AC Wave 1 and AC Wave 2. Just about all the AC stuff currently in the pipeline for outdoor wireless is wave 1. There is wave 2 indoor gear available, but for a WISP you are interested in the outdoor gear.
So what’s the difference?
For some reading about spatial streams, channel sizes, etc. look at this article https://info.hummingbirdnetworks.com/blog/80211ac-wave-2-vs-wave-1-difference
For the WISP folks who want the Cliff Notes version here are some key differences.
-Wave 1 uses 20,40,and 80 Mhz Channels. Wave 2 can support 80 and 160mhz channels. The 160mhz channel would be two 80mhz channels bonded together.
-Wave 1 can do 3 spatial streams. Wave 2 does 4. This requires an additional antenna to take advantage of wave2. This is a hardware upgrade from wave1 to wave 2.
-Wave 2 supports MU-MIMO. The AP can talk to 4 clients individually at once. The client must also support this, which is a hardware upgrade from wave 1 to wave 2 on both the client and the AP.
The question to ask your vendors is what is the upgrade path if you are using existing AC gear. If you are running AC currently you are most assuredly going to have to replace your AP radios and antennas. Will your existing clients work with the new AC wave 2 aps? An important thing to ask.
Offloading – Add CLI commands to disable flow-table flushing in offloading engine when routing table changes: set system offload ipv4 disable-flow-flushing-upon-fib-changes set system offload ipv6 disable-flow-flushing-upon-fib-changes
Prior to 1.10.3 firmware flow-table in offloading engine was always flushed when route was updated in linux routing table. Flow flushing ensured that offloading engine got routing updates instantly but it wasted a lot of CPU time and decreased performance if routing table was constantly updated for (instance in Full BGP, big OSPF or flapping PPPoE interface scenarios)
In 1.10.3 firmware by default disable-flow-flushing-upon-fib-changes is not set which means that flow table in offloading engine is always flushed upon routing table changes same way as it used to be in previous firmware.
If you have Full-BGP table or large OSPF network they you are advised to set disable-flow-flushing-upon-fib-changes this will ensure less CPU-load and increase max throughput.
Important note for multi-WAN environments – if nexthop interface of default-gateway changes and disable-flow-flushing-upon-fib-changes is set then it will take up to flow-lifetime seconds before all existing offloaded flows switch to new nexthop interface (up to 12 seconds by default).
Offloading – Add CLI command to modify flow-lifetime in offloading engine (expressed in seconds):
set system offload flow-lifetime 24Prior to 1.10.3 firmware flow-lifetime parameter was hardcoded and was not synchronized between different ER platforms: 12 seconds on ER-Lite/ER-Poe, 6 seconds on ER/ER-pro/ER-4/ER-6 and 3 seconds on ER-Infinity.
In 1.10.3 firmware default value of flow-lifetime is set to 12 seconds for all ER platforms and now it can be modified. By modifying flow-lifetime parameter you control how much traffic skips from offloading engine into linux network stack.
If you increase flow-lifetime then:
a) Offloaded IP flows will expire less frequently and less packets will be forwarded to linux
b) CPU load will decrease and max throughput will increase
c) if disable-flow-flushing-upon-fib-changes parameter is set then it will take more time for offloading engine to detect changes in routing table
If you decrease flow-lifetime then:
a) Offloaded IP flows will expire more frequently and more packets will be forwarded to linux
b) CPU load will increase and max throughput will decrease
c) if disable-flow-flushing-upon-fib-changes parameter is set then it will take less time for offloading engine to detect changes in routing table
Offloading – add CLI command to show flows in offloading engine: show ubnt offload flows Offloading – add CLI command to show offloading engine statistics: show ubnt offload statistics
Enhancements and bug fixes:
LDP – fixed regression in 1.10.0 when LDP configuration failed. Discussed here LoadBalancing – fixed regression in 1.10.1 when LoadBalancing failed to recover if WAN interface lost&restored link in 3 second interval. Discussed here DHCP – fixed bug when DHCP server configuration failed to commit with networks other than /8, /16, and /24. Discussed here TrafficControl – fixed regression in 1.10.0 when “command not found” output was printed when running “show traffic-control …” commands. Discussed here
One of the best features about the new aircube is the interface. On Facebook and other places the aircube has been criticized for it’s lack of features. I believe this is where the simple interface really makes the unit shine. One thing many people don’t realize is your typical home router really doesn’t have a true firewall. Most routers have features that are firewall like. Most “firewalls” are security by obscurity. The ability to close off ports is a by-product of a nat router.
Setup was very easy. I downloaded the ap, scanned the QR code, and then went into the phones wifi and connected to the AirCube wifi. Once I plugged it into my home router I was online.
One of the first things I always do when testing a new device is upgrade the firmware, unless I have a specific firmware version for whatever reason. Upgrading the firmware on the unit was very easy. I like the fact you can see the changelog notes with a single click.
Once upgraded the simplicity of the setup really shines through. By default, the AirCube is in an access point mode. This is probably the default mode which will be the most beneficial for the ISPs out there. I will explain why in a little bit.
The interface speaks for itself, I could go through screen by screen and spoon feed you the very simple setup screens, but you would get bored very quickly. It is truly a very minimalist product and interface.
One of the coolest features I like about this product is the scan feature. For some reason the way it is presented on screen resonates with me. It makes seeing the frequencies in use handy. While not a chart or graph, it still accomplishes the same function.
I know this little product has received some ripping from operators on various groups and forums. However, I think it fills a very basic need. That need is an easy to configure device which allows devices to access the Internet. Nat firewalls can be done by the provider, and the user never has to touch them. This is a trend many operators are headed toward anyway. Let the provider manage the endpoint for the customer. The customer ends up calling the ISP to do port forwarding or if they have a virus anyway. If the customer wants to add things in the house, it should be simple, and not add extra layers of NAT and firewall rules. This is a perfect fit for the Cube. So don’t dismiss it because it doesn’t have all the fancy features some router have. Save that for other product lines that you, as the ISP, can manage.
MTIN typically is not a reseller for many product lines, for several reasons. We like to be vendor agnostic and not chasing sales commissions on products, and we are not in the business of stocking product.
Having said this, we now have a reseller relationship with flexoptic.net. They have optics you can code for a huge variety of manufacturers. WISP clients will be intersted to know they support the following vendors:
and a whole bunch more. There are over 150 vendors supported.
The optics are coded with a product called Flexbox. The flexbox has several features to it such as coding, wavelength tuning of DWDM, distance analyzer, power measurement, and diagnostics.
We are working on some reviews, how-tos and other tutorials for these products. At the very least we are recommending everyone have a few optics of the form factors you use for compatibility troubleshooting. If you have a device that you wonder if it is recognizing your optics correctly you can pull out this kit, code an optic for your device, and go on with troubleshooting. Very handy for vendor optic issues.
If this is something you are interested in send us an e-mail for a quote on a starter kit and look for more information coming soon.