Hi all,
can someone advise on how to check PoE support and usage on Meraki MX65?
This device does support PoE on switch ports lan11 and lan12, but not sure how to check the status from UI or terminal.
My device details are:
|Model|Cisco Meraki MX65|
|Architecture|ARMv7 Processor rev 0 (v7l)|
|Target Platform|bcm53xx/generic|
|Firmware Version|OpenWrt SNAPSHOT r28092-487ca61f91 / LuCI Master 24.321.37054~09e8d51|
|Kernel Version|6.6.61|
Thanks
Check the mx64/mx65 support thread.
PoE PSE support isn't in openwrt yet but the developer is working on it and has a public github which should work?
edit:
And here's the code?
Hi evs,
I have managed to power poe camera using lan11, so seems that poe is supported in the image from the snapshots.
But I wanted to check the status, voltage and etc parameters of it and not sure how to do that?
Can you suggest any commands or tools which can help with that?
Maybe it's exposed via hwmon subsystem by the PSE driver - but I haven't tried. Check lm-sensors package.
No idea. Haven't done anything with proper linux drivers and PoE support. I'd have to read the driver code.
Actually I was wrong, PoE is not working when using the Snapshot sysupgrade/firmware.
However PoE was supported on Leo's builds available:
https://drive.google.com/drive/folders/1sq2kuuHpL4ylq3zJKcKXXG2a0BRrdE4N
I was testing my camera, before upgrade to the official snapshots.
Seems that Leo's builds are special.
Yeah per above?
Yes, they do contain a patch including this driver - but it requires work before submitting upstream.
Where can be get special builds that Leo has made? Snapshots dont have POE support and I looked over that the google drive link and that too does not shoe POE support when flashed.
Perhaps I have some stale link.
These mx65, with available 300 mb and 2gb ram are great firewall that may be headed en mass to land fill or recycling. Your ingenuity with efforts from you and others is helping some of these to be saved.
I am not a tech but would love to write up on how to make it easy to use for layman (being one) and load up adguard or squid or some such thing. Its got so many ports that it may easily have opt or dmz zones etc.
Great work. I love Openwrt.
It is literally this post: How to check PoE support and usage on Meraki MX65 - #6 by nenni. Have you checked it?
Thanks for your response.
I did exactly try that earlier (Oct 21) and then I tried just now again. Both times, the box works fine. I even configured it to be a giant 12 port switch and shut down firewall and deleted wan before bridging wan1 and wan2 to the same bridge. Everything fine.
Then when I disconnect the barrel DC power supply and hook that up to a POE switch. Nothing happens. Its power LED is off and the machine is also not connected.
Everything is OK except the POE. The MX65 does not want to boot on any POE. I tried two different POE switches.
Where in specification exactly it is described, it can work as PoE powered device?
This. There's unofficial info from Cisco forums that MX65 can be powered from some PoE adapters. If yours doesn't work then it doesn't work. Mine didn't.
MX65 can provide power to other devices.
I'm wanting to do the same with my MX65; it's not fast enough to keep up with my fibre internet now. I have gotten as far as dropping the br-wan and adding the wan ports to the br-lan interface, and I can turn off serving DHCP but with a static IP address. My issue is that when I set the br-lan interface to receive a DHCP address from my network, the device disappears and never comes back online, leaving me to have to use recovery mode. Any thoughts on what I'm doing wrong when assigning it to be a DHCP client?
I have set up my MX65 as a DHCP client with 12 ports bridged and firewall disabled and stopped. In my box, it's lan is able to obtain IP address from the upstream DHCP server. See attached:
If I changed all the interfaces to IPv4 only, i ran into some hiccups. However, this will take more testing.
You may want to check whether netifd gets notified about link status of the child interfaces of the bridge and the bridge itself. It's possible, that "force link" option may be required to get DHCP client working.
As @kitor pointed out, I went stray with picture evidence based posting. And, now I have also read that Meraki claimed that is not a supported function, even if it happens.
In my case, I just wanted to have fewer cables. No issues.
On another note, I created two interfaces (no vlan, tag or untag settings -- using just ports bridged):
The Lan received the DHCP address but OPT did not. I can test again tomorrow, if there are any suggestions, that would be nice.
For me "Force link" did not work.
I am surprised as to a layman like me, there certainly appears to be plenty of horsepower under the hood. I wonder if that is because it is a router trying to be a layer 3 switch. I wonder what will make this a layer 2 switch.
There is 2 gig ram and nearly usable 300 mb of storage. I read somewhere, if we can delete (not for the faint of heart) a few irrelevant partitions, then this can be made into a 1 gb flash.
PS: I did some follow-up testing:
##############################################
I checked your build once with 12V dc supply and then again with TP-Link 54V DC supply.
When I used 12V, the MX65 booted and worked great but did not provide POE on port 11 and 12.
When I used 54V TP link power supply, it supplied and booted two downstream POE devices (Meraki MR-52) perfectly.
In both instance, I had to use a 2.1mm to 3.0mm converter (6.3 mm x 3.0mm barrel). [Similar to this] but I had it in my arsenal from before:
