OpenWrt support for Ubiquiti U6-Mesh

Anyone been hacking on the U6-Mesh model? This is about a perfect device for my needs, but ubiquiti's 'mesh' software is somewhat lacking. I'd love to drop in openwrt w/ batman-adv.

This isn't just a repackaged U6-Lite/LR. It's 4x4 5Ghz AX and 2x2 2.4Ghz AX and runs a qualcom chip.

Can't find any info on openwrt on these yet.

1 Like

Then it wouldn't just be repackaged, since the Lite and LR are Mediatek based.
See if you can find photos of the Mesh at

That was the implication.

That hardware list for 'ax is all mediatek chips... is mediatek the only chipset openwrt has support for?

Sorry, read it as a question...

For AX, there's currently only support for MT.

dang. same for the u6-Enterprise w/ 6E, qualcom. Any idea of this is on someone's radar or did they lock these qualcom units down to much to get openwrt on there?

Locked boot loader could be something they've implemented.

The SoC and radio support comes from mainline Linux kernel, whatever is in the making there, will end up in openwrt.

Flash layout is different between the mediatek and qualcom U6-* APs. Still looks like standard uboot though.

Mediatek U6-LR:

U6-LR-BZ.6.0.21# cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00001000 "Preloader"
mtd1: 00020000 00001000 "ATF"
mtd2: 00060000 00001000 "u-boot"
mtd3: 00010000 00001000 "u-boot-env"
mtd4: 00040000 00001000 "Factory"
mtd5: 00010000 00001000 "EEPROM"
mtd6: 00010000 00001000 "bs"
mtd7: 00100000 00001000 "cfg"
mtd8: 01ee0000 00001000 "kernel0"
mtd9: 01ee0000 00001000 "kernel1"

Qualcom U6-MESH:

U6-Mesh-BZ.6.2.27# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00030000 00001000 "SBL1"
mtd1: 00010000 00001000 "MIBIB"
mtd2: 00010000 00001000 "BOOTCONFIG"
mtd3: 000a0000 00001000 "QSEE"
mtd4: 00010000 00001000 "DEVCFG"
mtd5: 00010000 00001000 "CDT"
mtd6: 00010000 00001000 "u-boot-env"
mtd7: 000a0000 00001000 "u-boot"
mtd8: 00070000 00001000 "ART"
mtd9: 00010000 00001000 "EEPROM"

Also looks like it has additional flash:

U6-Mesh-BZ.6.2.27# fdisk -l /dev/mmcblk0
The backup GPT table is corrupt, but the primary appears OK, so that will be used.
Disk /dev/mmcblk0: 3.7 GiB, 3959422976 bytes, 7733248 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B51F2982-3EBE-46DE-8721-EE641E1F9997

Device          Start     End Sectors Size Type
/dev/mmcblk0p1     34  131105  131072  64M unknown
/dev/mmcblk0p2 131106  262177  131072  64M unknown
/dev/mmcblk0p3 262178  262179       2   1K unknown
/dev/mmcblk0p4 262180  264227    2048   1M unknown
/dev/mmcblk0p5 264228 4458532 4194305   2G unknown
1 Like

I'm looking for a long range 802.11ax AP with OpenWrt support that can be pole-mounted outdoors, but none of the 802.11ax APs in the ToH seem to fit this scenario (they are either for indoor use or they are better fit for wall or ceiling mounting). The U6-Mesh would be an ideal device. Given the existence of this forum post, as well as the presence of other U6 devices in the ToH, how reasonable is it to hope that support for the U6-Mesh will be added in the near future (say by next summer)?

Anyone working on this? If not, how hard and time consuming would it be for someone with programming, Linux and OpenWrt experience (advanced administration only, no development) to add support himself? Is it only a question of effort and time or are there hardware limitations that would make this too hard if not impossible? I'm considering buying the device and temporarily using it with the stock OS, but I want to make sure that OpenWrt support can be added in the future, by myself if not by others. Thanks

Sorry for the third post in a row, but I need to decide very soon whether to buy this product or not.

I see that a couple AX-capable Qualcomm devices (Edge-corE EAP102, Edimax CAX1800) have been added to the ToH. Is this promising for the U6 Mesh or could there be issues preventing OpenWrt to support it in the future (e.g. you spoke about the possibility of a locked bootloader)?

Well, in case anyone wants to work on this but doesn't own the device, I do now. Please message me if you want to collaborate

Now that you have one, what did you discover?

Just using with stock firmware for now. Wouldn't even know where to start and I don't have a lot of free time to find out at the moment