BUG? WOL tool not working

RouterOS General
1

Can someone please check if /tool wol is working correctly on their devices?
Especially when using interface= parameter

In my case, sometime after upgrading to 7.x Wake on LAN packets are no longer being sent from hAP ac3.

I'm currently using latest RouterOS version 7.20.2 on hAP ac3 (main router) and ac2 (AP)

On ac3 I cannot see that it is sending WOL packet on UDP port 9 at all, regardless if I call "/tool wol" with or without interface parameter on any available interface.

/tool wol mac=aa:bb:cc:dd:ee:ff                    #does not work
/tool wol mac=aa:bb:cc:dd:ee:ff interface=bridge1  #does not work
/tool wol mac=aa:bb:cc:dd:ee:ff interface=ether5   #does not work

On ac2 which has a much simpler configuration and only has one brigde interface, WOL packet is only being sent when interface is not specified

/tool wol mac=aa:bb:cc:dd:ee:ff                    #WORKS!
/tool wol mac=aa:bb:cc:dd:ee:ff interface=bridge1  #does not work
/tool wol mac=aa:bb:cc:dd:ee:ff interface=ether5   #does not work

When ac2 does sent WOL package (without interface=) it does it on all interfaces which are up (bridge, ether5 and wlan1 - for example)

I'm using

/tool sniffer set filter-dst-port=discard filter-ip-protocol=udp

to check if WOL packet is being sent (as well as monitoring on LAN using wireshark...)

Something is off here, I'm sure it was working on ROS v6.x

What I would expect to see when calling /tool wol is that it either sends WOL packet on all interfaces without interface= parameter or to send only on a single specified interface. But that is not what I see here.

2

Tested this again on a third ac2 router (v7.19.4)

Sending WOL packets is still not working as expected...

/tool wol mac=aa:bb:aa:bb:aa:bb   # sends packet on ether1 interface (Internet)
/tool wol mac=aa:bb:aa:bb:aa:bb interface=ether1  # no packet sent
/tool wol mac=aa:bb:aa:bb:aa:bb interface=ether5  # no packet sent
/tool wol mac=aa:bb:aa:bb:aa:bb interface=bridge  # no packet sent
/tool wol mac=aa:bb:aa:bb:aa:bb interface=wlan1  # no packet sent

This definitely looks like a bug to me...

3

As always with Mikrotik Routers do you first have the default config from the RouterOS version.
So if you want to file a bug, you have to reset the device to the default config and then test the thing that doesn't work.
Like if you have design vlans and so on that not get it correct.

4

Thanks @patrikg, I'll try this as well.
In the meantime can you please test it on your end and see if you get results that make sense (i.e wol tool respecting interface= parameter)?

5

Did you filed the bug report? i have the same problem here, wol is being sent on default interface(another subnet) and i cant wake up my pc on lan with mikrotik, when i use interface=bridge1 none package at sniffer is shown, when not using interface parameter, it is sent to a diferent subnet…

6

Yes, I reported this on MikroTik support portal, but didn't hear back from them yet.
Feel free to report it as well, maybe they'll acknowledge the problem sooner.

This is exactly the issue I'm seeing, it's not possible to send WOL to any LAN based host since WOL packet is going out only on default Internet facing interface.

1 Like