Hi, i recently installed a new NAS (OpenMediaVault) on a HP MicroServer G7 and set it up for auto-shutdown and wake-on-lan.

I have a Mikrotik router (RB4011iGS+5HacQ2HnD) , running 6.45.9.

When i tested the Wake On Lan on the NAS i used two tools:
Wake On Lan from my ASUS AP admin panel (on network tools)
Wake On Lan Android APP
When i tested i had the ASUS AP conneted to the Mikrotik directly (ethernet2), then a dumb switch on ethernet10, then another dumb switch and the NAS conneted to that last switch.
The Wake on LAN worked, using both wake on LAN tools, passing trough this Layer 2 path.

After testing, i moved the NAS to it's definitive place, connected directly to the Mikrotik on Ethernet7, used the same two tools, but WakeOnLan did not work! Also used the CLI Mikrotik WOL command (first directed to the MAC address of the NAS, and on second try directed to the MAC address of the NAS + Ethernet7).

Also tried getting the NAS back to where i first tested, WOL worked again.

I have the NAS back on the Mikrotik on Ethernet7 , time to troubleshoot, anyone has any ideas where to start?

Thanks in advance!

There is a tool within cli:
[adter] > tool wol mac=xx:xx:xx:xx:xx:xx interface=bridge-1
"interface" can be specific but it also can be whole bridge
Try this

But it is not really the answer to your question. This is wol sent from Microtic and not through Microtic interfaces. (not sent from one interface to unit on another interface within same bridge)

Hi,

I got it working just now, i already tried that tool, although not pointed at the bridge but the ethernet interface.

When troubleshooting, in the NAS NIC, when it was connected to a dumb switch, i always saw activity on the LED's, wheter the system was running or was OFF.

In the Mikrotik the Ethernet port the NAS NIC had activity when the system was running, and was completly dead when the system was OFF.

I tried switching ethernet ports on the Mikrotik with the system off and i had activity on other ports, so i wen't to compare what was diferent with the configuration of the ports that had activity with the system off to the port that had no activity, turns out it was "Loop Protect" that was set to "off", i switched it to "default" like the other ports and now it had activity even with the system off, and Wake On Lan works!!

Thanks for the suggestion anyways!