Supported devices

 

(May be synced with firmware targets: http://dev.qmp.cat/projects/qmpfw/repository/revisions/master/changes/targets.mk)

qMp is based on LEDE/OpenWrt, so devices supported by LEDE/OpenWrt are very likely to be supported by qMp (at least to some extent). The requirements for a device to run a minimalistic qMp node are:

  • Compatibility with LEDE/OpenWrt
  • 4 MB flash memory
  • 32 MB RAM memory

however, devices with more resources will be able to include more qMp features and will provide better performance.

qMp is Free Software so, if it doesn't perfectly suit your needs, you can modify it and send us your patches so that we can apply them.

You can find more information in this article on how to add a new device (wiki).

There are many devices known to work with qMp, but only some of them have been thoroughly tested. Ubiquiti M2, M5, RouterStation and RouterStation Pro products, Alix boards and several TP-Link devices have provided good results, but we encourage you to try qMp on other hardwares and send us feedback.

Devices tested with qMp 3.1 Clearance
  • Ubiquiti NanoStation M2 / M5 (XM devices only, newer XW aren't supported yet)
    • LAN/LAN+Mesh/WAN/WAN+Mesh/Mesh modes on wired ports eth0 and eth1
    • AP/AP+Mesh/Mesh modes on wireless interface wlan0
  • Ubiquiti NanoStation Loco M2 / M5
    • LAN/LAN+Mesh/WAN/WAN+Mesh/Mesh modes on wired port eth0
    • AP/AP+Mesh/Mesh modes on wireless interface wlan0
  • Ubiquiti Rocket M2 / M5
    • LAN/LAN+Mesh/WAN/WAN+Mesh/Mesh modes on wired port eth0
    • AP/AP+Mesh/Mesh modes on wireless interface wlan0
  • Ubiquiti NanoBridge M2 / M5
    • LAN/LAN+Mesh/WAN/WAN+Mesh/Mesh modes on wired port eth0
    • AP/AP+Mesh/Mesh modes on wireless interface wlan0
  • TP-Link TL-WDR4300, TL-WDR4900
    • LAN/WAN modes on wired blue/yellow ports, Mesh mode only available on last yellow port
    • AP/AP+Mesh/Mesh modes on wireless interfaces wlan0 and wlan1
  • TP-Link TL-WR841N (v8 and v9)
    • LAN/LAN+Mesh/WAN/WAN+Mesh/Mesh modes on wired ports eth0 (blue) and eth1 (yellow)
  • PCEngines Alix 2
    • LAN/LAN+Mesh/WAN/WAN+Mesh/Mesh modes on wired ports eth0 and eth1
    • AP/AP+Mesh/Mesh modes on wireless interfaces
Other devices known to work with qMp
ARCFlex
  • FreeStation
Compex
  • WPE72
TP-Link

ar7xxx/ar9xxx OpenWRT target (almost all models should work)

  • TL-MR3020
  • TL-MR3040  (and plus aircam)
  • TL-WDR3600
  • TL-WR703N
  • TL-WR842ND
  • TL-WR2543ND
Ubiquiti
  • UniFi AP
  • Bullet M2 & M5
  • PicoStation 2
  • PicoStation M2
  • RouterStation  (discontinued)
  • RouterStation Pro  (discontinued)
  • XW-series products (partial support for some of them)
Ramips architecture devices
  • WRTNode
  • D-Link DIR-810L
Others
  • In general, every device supported by OpenWrt with 4 MB+ flash and 32 MB+ RAM can work with qMp.
Known issues
  • The upgrade tool (qmpcontrol upgrade) bundled with qMp is not able to upgrade x86/Alix machines with qMp 3.0.x or older, since the configuration is not kept after flashing.
  • Ubiquiti newer XW- devices are partially supported in the experimental version of qMp (Kalimotxo)
  • 802.11ac radio on D-Link DIR-810L devices is not supported.
  • When the cable of an Ethernet port is unplugged, the network addressing and routes of the device are not deleted or updated. If the interface is acting, for instance, as the default gateway, the route 0.0.0.0/0 stays present until the network is rebooted or the DHCP lease time (if in use) expires. This is a limitation imposed by OpenWrt 12.09 Attitude Adjustment, which has been fixed in the development version trunk Barrier Breaker.
  • Wired devices with an integrated switch (like the ones found in TL-WDR4300) always have the CPU port up. For this reason, OpenWrt does not detect if a cable has been plugged or unplugged in the Ethernet ports. This leads to situations like the one described in the previous issue, and is not resolved yet in OpenWrt.