WOL not working after upgrade

RouterOS Scripting
1

I hate upgrades, as always something goes wrong (ofcourse other things might have been wrong previously, hence the need for upgrade)

This time WOL stopped working in both 6.44.3 & current 6.45.3
It used to work perfectly fine in my old 6.34.x version

I can use Depicus WOL GUI tool (and with setting Send options: Internet my machines wakes up after packet is sent to 192.168.88.255 - but with Sent options: Local Subnet it also does not work, I assume /tool wol also uses local subnet, hence the issue)

So this does NOT work in current MikroTik RouterOS 6.45.3 (c) 1999-2019

/tool wol interface=ether2-master mac=A0:48:1E:B8:8D:58

Any ideas how to fix it?

sebus

2

It seems that the issue is that between OS versions behavior of master interface changed.

I have D-Link managed switch connected to ether3 (to which my devices are connected)

With current OS I can get WoL working again, but I had to change my scripts to use ether3 (previously it was working fine with master interface)

sebus

3

The concept of master interfaces does no longer exist in recent RouterOS releases. If the interface belongs to a bridge you should use that.

4

You need to find to which interface is A0:48:1E:B8:8D:58 attached. One good way is, while the device is awaken, and assuming good access to it, do:

:put [/ip arp get [f where mac-address=A0:48:1E:B8:8D:58] interface]

After ensuring that the device has been recently seen by the router (say after ping to its ip address).

5

This may not work. On hEX routers, it will just show name of the bridge where the interface is connected, not the physical interface.

6

The interface where it appears in arp table is the one that wake command needs

Sent from my Redmi Note 5 using Tapatalk

7

Interface is Bridge1 for all innside mac on hEX

/ip arp print
 0 DC 10.10.10.41     00:1A:EC:0C:1C:83 Bridge1
 1 DC 10.10.10.32     90:BA:1A:68:DA:D1 Bridge1
...
...
8

this means that bridge1 is the broadcast domain where the wake tool should be fired.

Sent from my Redmi Note 5 using Tapatalk

9

That I do understand, but if I know my PC is connected to ether2, its not easy to find out what mac is on ether2

10

if your machine is windows 10, you need to turn off quick boot in power option