Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add Hardware support: Unifi AC Mesh #1021
referenced this issue
Feb 12, 2017
That looks good.
I tried to write the whole thing down:
Its targeted for Atheros devices, and just from my amateurish viewpoint .
Next question then would be, check what works with the ac-lite board: wifi,lan,macadresses,LEDS
Gluon 2016.2.4, every 2-3 minutes in logread:
@Brother-Lal has build within his own repo a dedicated branch and changed all needed files (hopefully)...
If I just clone the LEDE Master tree and choose the AC-LITE device then LEDE is running on the AC-mesh, LOG:
What do I wrong during build, menuconfig etc.?
We confirmed that the Mesh Pro (codename "dragonfly") is actually using:
Hardware seems to be identical to what's been used with the UAP-AC PRO! Due to all the interesting talks and some debricking, we haven't tried to flash the existing image yet.
The case is a bit trickier but can be opened by first cutting the silicate seal all around the case (it's just two parts, later). The cover is hold in place by maybe 20 plastic hooks.
One can start to disconnect these hooks most easily by carefully levering the knobs up that hold the cable door in place (lever against the fixed part of the cable outlet). Once the first hook is loose, it's easier to continue with four hands and two screwdrivers.
Here are some pictures of the opened device:
We also found out that one of our AC Meshs was using a bootloader from 2016-06-12 which was not compatible with the latest gluon build. The device was bricked until we recovered with the special recovery process offered by UBNT, effectively upgrading the bootloader. One should update to latest stock firmware before trying to flash anything!
Note: it seems that you cannot be sure whether your device will actually boot from kernel0 or kernel1 partition (haven't searched for an output yet, that hints which one to flash to). This seems to be a safety feature where every upgrade would use the partition that’s not in use.
Testing mesh on 5 GHz has not yielded positive results yet. However, we couldn't confirm that the builds we were using can actually mesh on 5 GHz. Once we disabled 2.4 GHz mesh, no connection was possible to a second "mesh only" UAP-AC-M.
I'm gonna install my UAP-AC-M in a test setup for now and see if it's stable. One thing you can note is that these devices get a little bit hot when used indoors. It uses around 6.9 Watts when idling with gluon-v2016.2.3-8 - more than e.g. NanoStations would draw.
If somebody has access to an ubiquity ac lite, ac pro and also for the ac mesh pro, i would like to have a look at the flash. So, if you could do a Flash memory dump (cat /dev/mtd0 > /tmp/mtd0) for those three, i would appreciate it if you could drop me a link :)
DMESG log original FW:
First binwalk info:
Scan Time: 2017-05-11 07:09:40
DECIMAL HEXADECIMAL DESCRIPTION
150944 0x24DA0 Certificate in DER format (x509 v3), header length: 4, sequence length: 64
After FW upgrade (UniFi firmware 3.7.55 for UAP-AC-Lite/LR/Pro/EDU/M/M-PRO/IW):
Flash memory dump Unify AC mesh pro (FW 3755):
I have a UAP-AC-M-Pro (Mesh Pro); I have tried, but have been unsuccessful at getting non-stock firmware to run, presumably because of UBoot. I tried downgrading firmware to 3.4.7, but anything lower than 3.4.16 doesn't appear to boot on the device (TFTP upgrades succeed, but the device does not boot. fwupdate.real returns an error, stating it doesn't like the 3.4.7 firmware file.)
Arwed: I'm preplexed by your statement that one should update to the latest stock firmware before flashing custom firmware - were you able to get your unit to flash custom firmware, even with the UBoot installed by recent versions of firmware?
@janhanekom I have only flashed normal mesh APs yet. Therefore my comment was primarily meant for that device. My mesh AP came with "latest stock" back in March/April and we had no issues to flash it. Another mesh ap had a fairly outdated u-boot and bricked (details in my previous comment). I assumed that early mesh ap and ap pro's shipped together and would suffer both from ancient u-boot version (first orders).
Which Gluon version have you tried to flash on the device? If you have trouble with latest u-boot/stock I can add a warning to my comment that there might have been changes that cause compatibility issues.
Nevermind, I’ve figured it out! The unit has two Ethernet ports, and it turns out LAN and WAN are the other way around than I expected. When installing UAP-AC-PRO LEDE images onto a UAP-AC-M-PRO, LAN is on the “Secondary” port, and WAN is on the “Main” port (where PoE is connected to.)
(Haven't tried a Gluon image yet - right now I've just been trying to keep it basic and just testing "plain" LEDE. Prior to this I’ve tried both 17.01.1 and an image compiled from trunk.)
So as to my reason for asking about UAP 3.4.7 firmware: There is lots of talk on the LEDE pages and elsewhere about U-Boot in versions subsequent to 3.4.7 (3.4.16+) checking for digital signatures in firmware to block 3rd party firmware. Based on what I just did, I suspect that might no longer be the case, at least with recent firmware? (I had 3.7.55 on my device.)
For what it’s worth: Unifi 3.4.7 indeed does not boot properly on the UAP-AC-M-PRO. It gets partway through, as the AP responds to pings and you can SSH to it, but if you log in using ubnt/ubnt, the session closes immediately. (Logging in with a different password results in “access denied”, so pretty sure the credentials are correct.)
After I’d flashed my UAP-AC-M-PRO with LEDE and it didn’t come up (I flashed both firmware partitions – kernel0 and kernel1 – with the same image just to be sure), I assumed that the U-Boot problem was the cause. However, I eventually spotted odd behaviour which caused to me question that:
Status right now is that I’m up & running on the “Secondary” port. Similar to tuennes’ initial results, 802.11an/802.11ac does not seem to work yet even though I’ve added the qca988x-ct driver and firmware to my image. Subsequent posts infer he got it working, will try to reproduce.
That’s a challenge for another day… right now, I’m just chuffed I got the basics working without having to crack it open for access to a serial console.
Just an update: LAN and WAN being inverted (at least in my opinion) should be correctable in the device profile in LEDE; if I have time in the next few days' I'll try to catch up on how to do (and contribute) that, but it will probably be quicker and less error prone if someone else does it.
5Ghz wireless; not sure if this is related to the AC-M-PRO specifically, but: (tried both ath10k and ath10k-ct)
I find the above behaviour to be rather "weird." Will keep looking.
regarding unifi ac mesh (NOT mesh pro)
the mesh pro is not yet supported upstream.