Cisco Meraki MX64/MX65 image support

Thanks a lot for the info. Just build an image and PoE works while official 24.10.2 packages can be used.

openwrt-bcm53xx-generic-meraki_mx65-squashfs.sysupgrade.bin

owut check -v
owut - OpenWrt Upgrade Tool 2025.05.12~8353c4e9-r1 (/usr/bin/owut)
ASU-Server     https://sysupgrade.openwrt.org
Upstream       https://downloads.openwrt.org
Target         bcm53xx/generic
Profile        meraki_mx65
Package-arch   arm_cortex-a9
Root-FS-type   squashfs
Sys-type       sysupgrade
Version-from   24.10.2 r28739-d9340319c6 (kernel 6.6.93)
Version-to     24.10.2 r28739-d9340319c6 (kernel 6.6.93)
Build-FS-type  squashfs
Build-at       2025-06-23T20:40:36Z (~277 hours ago)
Image-prefix   openwrt-24.10.2-bcm53xx-generic-meraki_mx65
Image-URL      https://downloads.openwrt.org/releases/24.10.2/targets/bcm53xx/generic
Image-file     openwrt-24.10.2-bcm53xx-generic-meraki_mx65-squashfs.sysupgrade.bin
Installed      125 packages
Top-level       69 packages
Default         34 packages
User-installed  41 packages (top-level only)

Package version changes:
  kmod-hwmon-bcm59111          6.6.93-r1                                  missing to-version
  luci                         25.168.50434~d6b13f6                       25.179.72978~e977ed6
  luci-app-firewall            25.168.50434~d6b13f6                       25.179.72978~e977ed6
  luci-app-package-manager     25.168.50434~d6b13f6                       25.179.72978~e977ed6
  luci-base                    25.168.50434~d6b13f6                       25.179.72978~e977ed6
  luci-light                   25.168.50434~d6b13f6                       25.179.72978~e977ed6
  luci-mod-admin-full          25.168.50434~d6b13f6                       25.179.72978~e977ed6
  luci-mod-network             25.168.50434~d6b13f6                       25.179.72978~e977ed6
  luci-mod-status              25.168.50434~d6b13f6                       25.179.72978~e977ed6
  luci-mod-system              25.168.50434~d6b13f6                       25.179.72978~e977ed6
  luci-proto-ipv6              25.168.50434~d6b13f6                       25.179.72978~e977ed6
  luci-proto-ppp               25.168.50434~d6b13f6                       25.179.72978~e977ed6
  luci-theme-bootstrap         25.168.50434~d6b13f6                       25.179.72978~e977ed6
1 packages missing in target version, cannot upgrade
13 packages are out-of-date

Default package analysis:
  Default                      Provided-by
  nftables                     nftables-json

Can a MX65 power supply power a MX64?

I think you will fry the MX64. The MX65 PSU supplies 54V while the MX64 PSU supplies 12V. The size of the pins are different as well so it would not fit properly.

It might. I believe they used the same 90W supply (MX65 just had more ports)

1 Like

MX65 works just fine with 12V DC. The POE supports would not be enabled even with the image from LEO (@Leo-PL -- Thank you so much each time I think of MX65).

The extra power of 90w is mostly needed to service the WIFI radio and the POE. An average 1.5a / 12v DC with 2.5mm DC barrel power supply works fine for MX65.

I have tried this with a 12V DC supply (works fine). Also tried with 19v DC and it works fine too. Then I have tried with 48v DC supply it works fine and also starts to operate the POE ports.

Cheers!

Did you build using Firmware selector?
And the POE worked automagically? When I tried a couple of months ago, I had to use Leo version of firmware and the one from the Openwrt did not have POE support.

LMK.

No POE does not work with the standard images / firmware selector. You will have to build your own firmware using the steps described here:

Thanks. I am not that good on linux and so this is a bit intimidating. I will study this later and then perhaps build.

Any idea why the std openwrt do not have the POE enabled and it has to be cherry picked?

Because the original POE driver from the Meraki GPL sources is used which is not part of mainline linux. The driver code works but would need to be submitted upstream and get accepted in mainline linux before it can become a part of OpenWrt. I don't know how to code but others have said that the current driver code would need to be improved / updated to current standards before it would be accepted in mainline linux.

2 Likes

I tried based on @konus point to this post. When I enter "make", it takes a long time and starts making arth79 onward.
Is there a pointer to make just MX65 and how to give it packages to include?

Much appreciate. I am not a developer.

you need to choose the chipset and router model.
You can use the image I've provided above if you want?